Create A Plan

Create A Plan

Use this skill when the user wants a substantive plan before a repository change.

Prime Agent Setup

Read ../../../../references/prime-planning-workflow.md and state-and-config.md — both normative — and follow their setup, state, language, and reviewer/criticizer rules. State lives in .git/prime_plans/ via ../../../../scripts/prime_plans_state.py init --workdir <target-workdir>; spawn reviewer/criticizer roles with await rlm(...).

Depth Contract

• Inspect the target Git repo read-only before the first product question.
• Ask 5 to 10 planning questions, one at a time; standard choice format (recommended first, Other second-last, Auto-complete last).
• Use web research whenever outside library behavior, ecosystem precedent, UX convention, protocol semantics, or compatibility affects the recommendation.
• Ask the final scope confirmation, then write PLAN_v1.md per ../../../../references/plan-artifact-template.md.
• After each plan version, ask the refinement mode question from the shared workflow — never spawn a reviewer or criticizer unless the user or Auto-complete selected it at that question. Default sequence: one Reviewer round, then one Criticizer round; afterwards the recommended option is Accept plan for native Prime Agent execution. Up to five rounds total, continuing only for high-priority findings or unresolved criticizer questions; surface at most five per round. Then the goal-based execution handoff from the shared workflow.

Fit

Multi-file changes, architecture boundaries, user-facing workflows, external APIs, dependency upgrades, compatibility risk, or web-evidence-shaped plans. Escalate to create-a-big-plan when open-ended, cross-system, strategically ambiguous, or likely beyond ten planning decisions.