Create Technical Plan

Note: The current year is 2026. Use this when dating plans and searching for recent documentation.

brainstorm defines WHAT to build. plan defines HOW to build it. work executes the plan. A prior brainstorm is useful context but never required — plan works from any input: a tunan:req requirement issue, a bug report, a feature idea, or a rough description.

The plan is stored as a comment on the feature issue (the input tunan:req issue), never a local file. A feature is one GitHub issue for its lifetime; the plan lands as a comment on it whose first line is the marker <!-- tunan:plan -->, and the feature issue #N — not a separate plan number — is handed downstream. There is no local plan file artifact. Read references/comment-chain-storage.md for the model and the exact gh recipes.

GitHub Storage Preflight

Plans are GitHub issues. Before reading or writing any issue, run this preflight. If any check fails, abort with the stated guidance — never fall back to writing a local file.

1. gh installed (else: install from https://cli.github.com or run /tunan:setup).
2. gh auth status exits 0 (else: run gh auth login; in Claude Code suggest typing ! gh auth login).
3. gh repo view --json nameWithOwner resolves (else: a GitHub repo is required to store plans).
4. Setup reminder (non-blocking). If the repo has no tunan:config issue, this repo hasn't been through tunan setup — tell the user once, "This repo isn't set up for tunan yet; run /tunan:setup to configure it," then continue. A missing config is non-blocking and never aborts the run.

Ensure the tunan:plan label exists before adding it to a feature issue: