planlisted

# /abc:plan — Draft a PLAN-*.md fast Produce a structured plan document within a few tool calls — no extended clarifying-question loop. The output is shaped so that: - `/abc:scaffold-sub-issues` can turn the sub-tasks into a Linear parent + sub-issues. - `/abc:ship-epic` (later) can read the sub-issue dependency graph and ship them in parallel. ## Hard rules - **Write first, refine in place.** Within the first 3-5 tool calls, produce a draft `PLAN-<slug>.md` on disk. Then iterate via the file, not via Q&A. The user has explicitly said extended clarifying questions before any deliverable are an anti-pattern. - **Always include the obvious adjacent sections** on the first pass: context, approach, sub-tasks (with repo + dependencies), open questions, validation. Even if a section is one line, write it — easier to delete than to retroactively add. - **Never commit the PLAN file or push it.** It lives locally until the user decides where to keep it. - **Use `repo:<name>` notation per sub-task** so `/abc:scaffold-sub-issues` can map it to a Linear `repo:` label and `/abc:ship-epic` can resolve it to a workdir. ## Where to put the file Default: `~/.claude/plans/PLAN-<kebab-slug>.md` (keeps drafts out of project repos by default). Override: if the user passes an explicit path or is inside a project repo and says "in this repo", write to `./PLAN-<kebab-slug>.md` in the cwd. Slug: derive from the task description. Keep it short, kebab-case (e.g. `cuj-platform-poc`, `auth-migrat