メニュー
Route feature planning to the correct workflow. Recommends RFC-first design when no RFC exists, sends reviewed RFCs to RFC-backed planning, and sends explicit opt-outs to direct planning.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use whenever executing, continuing, resuming, or finishing an implementation plan or plan directory. Orchestrates assigned worker dispatch, integrated test-first discipline, progress checkpointing, isolated workspaces, checkpoint integration, and blocker batching.
Create implementation plans directly from user requirements when no reviewed RFC is available or the user explicitly declines RFC-first planning. Decomposes work into self-contained sub-plans with full iterative multi-agent plan review.
Create implementation plans from a reviewed RFC. Uses the RFC as the approved design baseline, decomposes it into executable sub-plans, and runs RFC-specific plan review.
Use whenever implementing or fixing production code, writing or changing tests, reviewing test quality, applying TDD, or diagnosing tests that pass without proving behavior. Ensures tests are requirement-grounded and reach behavioral RED before implementation.
Use when turning a settled design direction, brainstorming outcome, context anchor, or architecture discussion into a codebase-grounded RFC. Produces self-contained RFC documents with verified current architecture, chosen design, tradeoffs, risks, stable references, and planning handoff context without creating implementation plans.
Create project-specific plan reviewer agents that integrate with the planning-project-features workflow. Use when a project needs domain-specialized reviewers for sub-plans (e.g., Go code reviewer, API layer reviewer, database reviewer) or when the planner warns that no suitable local reviewer exists for a sub-plan's domain.
| name | planning-project-features |
| description | Route feature planning to the correct workflow. Recommends RFC-first design when no RFC exists, sends reviewed RFCs to RFC-backed planning, and sends explicit opt-outs to direct planning. |
Route feature planning deterministically. This skill does not create plans itself; it chooses the correct planning workflow and then stops or delegates.
| Input State | Action | Planning Workflow | Reviewers |
|---|---|---|---|
| Reviewed RFC provided | Validate the RFC review record, then use the RFC as the design baseline | planning-project-features-from-rfc | plan-rfc-fidelity-reviewer, plan-executability-reviewer |
| RFC provided but not reviewed | Stop and offer two choices: review the RFC first, or proceed as direct planning | authoring-rfcs review or planning-project-features-direct | Depends on chosen path |
| No RFC provided | Recommend creating an RFC first, then ask whether to create one or continue directly | brainstorming + authoring-rfcs, or planning-project-features-direct | Depends on chosen path |
If the user provides or references an RFC, read it and inspect its Review Record.
A reviewed RFC has:
design-reviewer with status Passed or Passed with concerns.Blocking review status that affects decomposition, scope, contracts, migration, rollout, acceptance criteria, or implementation constraints.If these conditions hold, use planning-project-features-from-rfc. Do not re-gather requirements or re-litigate the RFC design.
If an RFC exists but does not meet these conditions, stop and present exactly two choices:
authoring-rfcs.planning-project-features-direct, treating the RFC as background context rather than an approved baseline.If no RFC exists, recommend creating one before planning. Explain the concrete benefits briefly:
Then ask the user to choose exactly one path:
brainstorming and authoring-rfcs.planning-project-features-direct.Do not continue silently. The user chooses the route.
After the route is chosen, load exactly one workflow skill:
planning-project-features-from-rfc for reviewed RFC-backed planning.planning-project-features-direct for direct planning.brainstorming and then authoring-rfcs when the user chooses RFC-first design work.Do not mix workflows in one planning run.