prepare-ticket

Use when asked to create a Notion page — drafts the requested content and creates the page through the session's Notion tools, private by default unless the…

Use when an approved design doc (ADR, accepted RFC, epic-scale ask) should become several tickets and task folders — proposes the decomposition into ordered…

Use when asked to explore, explain, walk through, describe, teach, or analyze a topic — code, a library or API, a protocol, a system, a concept, or a domain…

Use when asked to fix code or documentation findings from a session review, PR comments, or a pasted or saved list.

Use when asked to implement, execute, run, or carry out a task's plan from a task folder (canonically under `.agents/tasks/`) — by task folder path, or the…

Use when asked to prepare, draft, or write up an epic or its description — drafts it to a file in the kit's default epic shape from a raw description, a PRD…

Use when asked to publish review-code's findings to the PR on GitHub — offers its Critical/Major findings, its Minor findings, and its improvements as counted…

Use when asked to format dictated text or a transcript, applying spoken punctuation, layout, emoji, and editing commands while preserving the speaker's wording.

Use when asked to implement, build, fix, or change something directly — described in the session or pointing at a file, issue, or diff — with no task folder…

Use when asked to create, update, or repair this machine's agents-kit config — discovers task roots or configures a requested runbook directory, compares…

Use when asked to plan, design, architect, scope, or break down a feature or change before implementation.

Use when asked to proofread, check, review, or polish a message, email, or piece of writing.