New product, zero context:ramp up in weeks, not months
Joining a product as its new owner or analyst means weeks of archaeology: a Confluence wiki you can't navigate yet, a Jira board full of conventions nobody wrote down, a running product with screens the docs forgot. Khint turns the archaeology into one growing work session: pull the docs and the board into it, ask AI about the screens, and start writing in the team's style from your first week.
The ramp-up problem is not reading,
it's retention across tools
In your first weeks you read plenty: onboarding docs, old tickets, retro notes, the product itself. The problem is that each piece lives in a different tool, and by the time you write your first user story, the context you gathered on Tuesday is three tools away. Khint's answer is a Memory session that everything flows into, fed by the Confluence and Jira integrations and by Capture, so the Actions you write with have your accumulated understanding in view, not just the paragraph you selected.
Your first weeks, in five moves
Every step runs from the same palette shortcut.
Start a ramp-up session before your first meeting
On day one, start a Memorysession called “Ramp-up”. It becomes the container for everything you are about to absorb: every document you pull, every board query, every screen you capture lands there as an entry, and Khint keeps a compacted summary of the whole thing. Instead of scattering your first weeks across browser tabs and a notes app, the learning accumulates in one place, on your machine.
Pull the pages everyone tells you to read
Every new PO gets the same welcome: a list of Confluence links. Open the palette with Cmd+Shift+K and run Pull page: Khint shows you the spaces you can see, then the most recently modified pages in the space you pick, or paste a page URL directly. Pull the product overview, the architecture page, the last quarter's decisions. Each one is read into your session, so the doc trail and your own notes stop being two separate piles.
Learn the board without knowing the JQL
Run Active sprint to load the current sprint's state into the session, and Pull issue on the tickets your new teammates keep mentioning. When you want a slice of the backlog and don't know the project's query syntax yet, the Search Jirarow lets you describe it in plain words: Khint drafts the JQL, shows it to you to confirm, then pulls the results. You learn what a “done” ticket looks like here by reading real ones, not by asking someone to export a list.
Ask about the product itself, screen by screen
Documentation lags; the running product doesn't. When you are clicking through the legacy admin console and hit a screen nobody warned you about, run Capture & ask from the palette: select the region and ask questions about what you are looking at, in a back-and-forth Capture chat. Extract text grabs the labels and error strings off any screen straight to your clipboard when you just need the words (say, to search Jira for the ticket that introduced them).
Write like the team from your first week
If a teammate shares the team's pack, you open an invite link, sign in, and their pack appears read-only in your Agentspage; a preview shows you every prompt before you clone it into your own packs. Now your first ticket runs through the same “draft a story” action as everyone else's; and because your actions can read your ramp-up session's context, the draft already uses the product's vocabulary you have been pulling in all week.
The ramp-up session becomes
your product brain
Weeks in, the session that started as onboarding notes is a compact record of how you learned the product. One click on Copy recap turns the whole session (summary and entries) into paste-ready markdown, handy when your manager asks how the ramp-up is going or when the next new joiner asks where to start. From there, the habits carry over: the same session mechanism powers day-to-day work context, the terms you kept tripping over can seed a living business glossary, and your first real deliverable is one palette row away: meeting notes into a Jira ticket that reads like the team wrote it. And when it's you handing a product over someday, the other side of this page is the handover document.
Common questions
My new team doesn't use Khint. Is it still useful for ramping up?
Yes. The pulls only need your own credentials: connect Atlassian with your email plus an API token on the Integrations page and the Confluence and Jira rows work with no one else involved. The team-pack step is a bonus for teams that do share prompts; if yours doesn't, clone a first-party starter pack (Meeting → Ticket, Backlog Refiner) from the Agents page instead and adapt it as you learn the house conventions.
Where does everything I learn about the product end up?
In the Memory session you started for the ramp-up, which lives in a local database on your machine and is never synced to Khint's cloud. A pull happens only at the moment you run its palette row, with your own credentials, straight from Confluence or Jira to your machine. Khint keeps a compacted running summary of the session; that summary is what your Actions read, and it stays on-device too.
How do AI drafts pick up the product's vocabulary?
Each saved Action has an opt-in to read your active session's context. Switch it on for your drafting actions, and every ticket or note you write is generated with the compacted summary of what you pulled and captured in view: the module names, the team's ticket shape, the domain terms. Your first drafts sound like week six instead of day two, without you pasting background into a chat window each time.
Isn't this what a handover document is for?
A handover document is the outgoing person's snapshot, frozen on their last day, and it answers the questions they thought to write down. Your ramp-up session is the incoming person's living context: it grows with every page you pull, every board query, every screen you capture, and it answers the questions you actually hit. The two work well together: pull the handover page into the session as one of its first entries.
Start the new role ahead, not behind
Free with 10 AI actions and 5 captures per day. No credit card. Confluence and Jira connect with your own credentials, kept in your keychain.