plankitlisted

# plankit Turn a rough idea — a feature, a project, a spec, a PRD — into a structured plan document you can act on. plankit is generative: it brainstorms the approach, settles the decisions needed for a coherent draft, and writes a `plan-<slug>-YYYY-MM-DD.md` grounded in the real codebase (not a guess). It is the front of a three-step flow — **plankit drafts → grillkit hardens → issuekit files** — so the plan it writes is the exact input those next steps expect. plankit **plans only**: it never writes application code and never creates issues. ## When this fires The user wants to think a piece of work through *before* building it — "plan this feature", "brainstorm a plan / PRD / spec", "write a plan doc", "help me think through X first", "/plankit". One distinction matters: - **It is not the adversarial interrogator** — that's grillkit. plankit asks enough to draft a coherent plan and records the thin spots as open questions; grillkit is what pressure-tests them one decision at a time. ## Procedure ### 1. Capture the idea Get the concept, the problem it solves, who it's for, and the outcome that means success. If the input is a one-liner, ask a few **scoping** questions (use `AskUserQuestion` when available) — generative "what are we building and why", not adversarial "what did you miss". Enough to draft, no more. ### 2. Ground it in reality Research before proposing, so the plan reuses what exists instead of reinventing it. - **In an existing repo:** read the relevan