From kickoff chaosto a project charter
The first week of a project scatters its own foundations: goals in a deck, scope in a meeting, milestones on a whiteboard, risks in someone's head. Khint collects what you pull and capture into a Memory session, drafts the charter from that context with one saved action, and publishes it to Confluence with a preview before anything is written.
The charter is due
while everything is still in pieces
A charter is easy to write a month into a project and needed on day three. That is the trap: the moment sponsors want goals, scope, and milestones on one page is exactly the moment those things exist only as fragments: a kickoff deck, a discovery page someone drafted, an epic in Jira, notes from two meetings that half-contradict each other. A blank template does not fix that; the headings were never the hard part. What you need is a way to collect the fragments as you encounter them and then draft from them. That is what a Memory session plus one saved charter Action does.
Kickoff week, from fragments to a signed-off page
Collect as you go, draft from context, publish with a preview.
Start a Memory session for the kickoff
On the Memory page, start a session named after the project. From now on, everything you pull or capture while working on the kickoff is logged as an entry, and Khint keeps a compacted running summary of it. The charter will be drafted from this context, not from a blank page.
Gather the scattered inputs into one place
Kickoff material never lives in one document. Pull the existing epic with Pull issue and the discovery page with Pull page straight from the palette once Atlassian is connected. Run Extract text over the kickoff deck or a whiteboard photo to capture what was never typed. Each pull and capture lands in the active session.
Draft the charter with one action
Select your rough kickoff notes, hit Cmd+Shift+K, and run a saved “Draft project charter” Action: background, objectives, scope in and out, stakeholders, milestones, risks. Because the session is active, the action also sees the compacted context of what you gathered in step two, so the draft cites the epic and the discovery decisions you actually pulled.
Publish it as a Confluence page, with a preview first
Run Create page from the palette: pick the space, pick the parent page (or the space root), and Khint drafts the page with the action you chose, then shows a preview behind a confirm button before anything is written to Confluence. The charter goes from notes to a linkable page without you opening a browser tab.
Turn the routine into one keystroke for next time
Chain the charter action and the Confluence write into a single Workflow: draft the charter, create the page, and hand back the link. The next project you kick off, the whole routine is one launch from the palette instead of an afternoon of assembling.
A BA's kickoff, played out
Monday: the payments-migration kickoff. You start a session named after the project, pull the umbrella epic from Jira and the discovery page from Confluence, and run Extract text over the sponsor's three scope slides. Wednesday, after the second stakeholder meeting, your notes file is a mess of decisions, open questions, and two dates that matter. You select the lot, hit Cmd+Shift+K, and run your charter action. The draft that pastes back already frames objectives against the epic and lists the scope exclusions the sponsor insisted on, because the session context carried them. You fix two lines, run Create page, choose the project space, confirm the preview, and send the link. The risks section is thin? Feed it to the RAID log flow next.
Why not just fill in a charter template?
A template hands you the headings and leaves the actual work untouched: chasing content across a deck, a tracker, and three sets of notes, then summarizing it consistently. A chatbot can summarize, but only what you paste into it, one fragment at a time. Khint's difference is that collection and drafting are the same motion: the pulls and captures you make while preparing the kickoff are already in the session, so the charter action drafts from the real material, in place, and the result pastes back where you are working. The charter is also just the first page of a project's paper trail: the same habits produce status reports while it runs and a handover document when it ends.
Common questions
What does the AI actually see when it drafts my charter?
Only what you give it: the text you selected when you ran the action, plus, if you opted in, the compacted summary of your active Memory session. That session summary is how the charter draft can reflect the Jira epic you pulled and the pages you captured during kickoff week without you re-pasting them. Nothing else on your screen or disk is read, and Memory sessions live in a local database on your machine.
Can Khint publish the charter straight to Confluence?
Yes. Connect Atlassian with an API token on the MCP page, then run Create page from the palette: you pick the space, pick a parent page (or the space root), Khint drafts the page with the action you chose, and shows you a preview behind a confirm button before anything is written. Later revisions can go through Append to page, which adds to the existing charter without rewriting what is already there.
Do I have to write the charter prompt myself?
You save it once as an Action, but you do not have to write it from scratch: type a one-line description like 'turn kickoff notes into a project charter with background, objectives, scope in and out, stakeholders, milestones, and risks' and press Generate. Khint drafts the prompt, and Improve refines it in place. After that, the charter format is one shortcut away for every project you start.
What if half my kickoff inputs are slides and whiteboards?
Capture them. Extract text runs a region capture over any slide, PDF, or shared screen and puts the text on your clipboard, and you can point it at a whiteboard photo too. With a Memory session active, each capture is also logged into the session, so the material feeds the charter draft even when it never existed as selectable text.
Start the next project on one page
Free with 10 AI actions and 5 captures per day. No credit card. Collect the kickoff as you go, and draft the charter from it.