plan-feature
Guide a feature from requirements interview through architecture analysis, security check, and task decomposition.
Mr-DooSun · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Mr-DooSun/fastapi-agent-blueprint --skill plan-feature技能说明
name: plan-feature description: Guide a feature from requirements interview through architecture analysis, security check, and task decomposition. metadata: short-description: Feature implementation planning
Plan Feature
Default Flow Position
- Steps:
framing(Phase 0) +approach options(Phase 1) +plan(Phases 2~4) - Routes after: STOP at the approved Execution Packet. Execution is a separate, explicit step — invoke
$execute-plan, which advances the ledger toexecutingand routes to the implement skills internally. To run a single implement skill directly, use a[trivial]/[hotfix]token. Never auto-continue from planning into implementation in the same turn (ADR 054; Codex surfaces the drift as a Stop-time advisory, Claude hard-blocks) - Recursion guard: do not invoke
/plan-featurerecursively. Implement skills must not call/plan-feature(planning happens before implement)
Procedure Overview
-
Requirements Interview — 3-5 questions from 5 categories (Phase 0)
-
Approach Options — propose 2-3 candidates with trade-offs, recommend one (Phase 1)
-
Architecture Impact Analysis — layer, domain, DTO, cross-domain (Phase 2)
-
Security Checkpoint — 6-item assessment matrix (Phase 3)
-
Task Breakdown — skill mapping, supervision levels, execution order (Phase 4)
-
Execution Packet — include Goal, Scope, Success Criteria, Selected Approach, Architecture Impact, Task List, Verification Gates, and Review Gates.
-
Work-ledger update — after task breakdown is confirmed, record goal/scope/plan and workflow state via
from work_ledger import update_goal_scope_plan, update_workflow_state; update_goal_scope_plan(goal=..., scope=..., plan=..., updated_by="skill:plan-feature"); update_workflow_state(stage="planned", plan_ref=..., tasks=..., updated_by="skill:plan-feature") -
Read
AGENTS.mdanddocs/ai/shared/skills/plan-feature.mdfor the full procedure. -
Read
docs/ai/shared/planning-checklists.mdfor question bank and templates. -
Interview the user on requirements (data model, business rules, integrations).
-
Propose 2-3 approach options with trade-offs and recommend one.
-
Analyze architecture impact, run security checkpoint, break into tasks.
-
Present the implementation plan in the standard output format, including the Execution Packet.
-
After approval, write the ledger (
stage="planned") and stop — hand complex, architecture-changing, governor-changing, or multi-task work to$execute-planas a separate step. Do not implement within$plan-feature(ADR 054; on Codex the plan→execute drift surfaces as a Stop-time advisory).