メニュー
Full planning workflow — create (with integrated validation), review, and consolidate. Orchestrates plan-creation, plan-review, and plan-consolidation. Triggers on "/plan", "create plan", "plan for".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Research codebase, validate external claims, and emit a work-ready spec.json for a new planning session. Single-pass creation with integrated validation via Context7 and locator/analyzer agents. Triggers on "create plan", "plan for", "write a plan". For exploratory requests where the user is unsure what to build, prefer brainstorm first. Once spec.json exists, use plan-review for evaluation or go straight to work. For a reviewed spec, use plan-consolidation to merge findings.
Execute spec.json (plan mode) or review.findings.json (fix-findings mode) by dispatching subagents per chunk. Triggers on "work on", "implement", "execute plan", "carry on", "continue".
Shared conventions for Flywheel subagents. Tool discipline, output format, research patterns.
Perform exhaustive code reviews using multi-agent analysis. Reviews PRs, branches, or current changes. Writes review.findings.json to the active session. Triggers on "review", "code review", "check PR".
Refine the active session's spec.json by merging reviewer findings.json into it. Backs up the pre-refinement spec to a .pre-consolidation sidecar. Triggers on "consolidate plan", "finalize plan".
Run ALL reviewer agents in parallel against a plan. Deduplicates findings semantically and writes findings.json to the active session. Triggers on "review plan", "check plan".
SOC 職業分類に基づく
| name | plan |
| description | Full planning workflow — create (with integrated validation), review, and consolidate. Orchestrates plan-creation, plan-review, and plan-consolidation. Triggers on "/plan", "create plan", "plan for". |
| argument-hint | [feature description OR path to *-design.md OR slug of existing session] |
| allowed-tools | ["Read","Bash","Skill","AskUserQuestion"] |
MANDATORY FIRST ACTION — You MUST use the Skill tool to invoke the correct skill below BEFORE doing anything else. Do NOT read files, search code, or respond to the user first.
Determine which skill to invoke first based on the input:
feat-user-auth) that matches an existing session under .flywheel/plugin/sessions/<slug>-* whose spec.json exists: invoke plan-review (skip creation)-design.md): invoke plan-creationInvoke the first skill NOW using the Skill tool:
skill: plan-creation
OR if the input resolves to an existing session with spec.json:
skill: plan-review
#$ARGUMENTS
Note: The current year is 2026.
DO NOT WRITE OR EDIT ANY CODE DURING PLANNING!
This workflow is for research and planning only. Implementation happens in /work.
This orchestrator runs three skills in sequence. After each skill completes, immediately invoke the next one using the Skill tool. Do NOT stop between phases — select "continue" options when presented and invoke the next skill.
[Input] → plan-creation → plan-review → plan-consolidation → [Present]
After plan-creation, the session dir at .flywheel/plugin/sessions/<session-id>/ contains the spec.json and session.json that subsequent skills read. The active pointer .flywheel/plugin/active.json is the connecting glue — no explicit path-passing between phases.
spec.json, session.json into the session dir; updates active.jsonreview.findings.jsonreview.findings.json into spec.json; backs up pre-consolidation spec to spec.json.pre-consolidationIf the input was a slug that resolved to an existing session (review mode), start at step 2.
After plan-creation completes, invoke:
skill: plan-review
After plan-review completes, invoke:
skill: plan-consolidation
Both skills read the active session via .flywheel/plugin/active.json — no path arg needed.
Display summary: session id, session dir path, phases completed, findings count, and any critical items.
/plan Add user authentication with OAuth2 — Full mode (all 3 phases, creates a new session)/plan .flywheel/plugin/designs/oauth2-design.md — Design mode (creation uses design doc as input, creates a new session)/plan feat-user-auth — Review mode if a session slug feat-user-auth-* already exists (skips creation, starts at review)After consolidation, the session dir contains: spec.json (refined with findings integrated), spec.json.pre-consolidation (backup of the pre-refinement spec), and session.json. The review.findings.json is consumed and removed. Ready for /work.