Create A Small Plan
Use this skill when the user wants a compact 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 1 to 3 planning questions, one at a time; standard choice format (recommended first,
Othersecond-last,Auto-completelast). - Ask the final scope confirmation, then write
PLAN_v1.mdunder the artifact root (normallydocs/prime-plans/YYYY-MM-DD-topic/) 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-completeselected it at that question. Default: exactly one round, recommended modeCriticizer; afterwards the recommended option isAccept plan for native Prime Agent execution, then the goal-based execution handoff from the shared workflow.
Fit
A few local files, clear ownership, low risk, focused verification. Escalate to create-a-plan for external API semantics, dependency behavior, compatibility research, cross-module design, or more than three meaningful decisions.