Dev Plan

Dev Plan

Convert a spec / scoped requirement into a Critic-approved implementation plan before coding. Single-agent in-context consensus loop:Planner → Architect → Critic, with iteration cap.

This skill only plans. It does not gather requirements (dev-grill-docs does that; dev-spec is a compatibility alias) and does not review or write code (dev-code-review / your editor / a coding skill do that).

Trigger routing

Use this skill when a spec or scoped requirement exists and the user wants a concrete implementation plan with cross-perspective validation before writing code. If the user is still asking to clarify what the requirement should be, route to dev-grill-docs.

Trigger phrases include:

• 基于这个 spec 出 plan
• 需求已经清楚了给实施方案
• 技术实施方案
• 出个 plan
• 做个实施方案
• plan this
• make a plan
• consensus plan
• ralplan

Ambiguous phrases such as 写个方案, 给我个方案, 怎么做这件事, or 帮我设计 belong to dev-grill-docs unless the user says the requirement/spec is already clear and wants implementation steps.

Output goes to .claude/artifacts/plans/<feature>.md.

Optional arguments:

• --quick: single-pass plan for small changes
• --deliberate: high-risk plan with pre-mortem and expanded test plan
• default: full Planner → Architect → Critic loop

Step 0 — Load baseline

执行前先加载 references/dev-baseline.md。不假设、最小代码、外科手术式改动、可验证成功标准 全程生效。

baseline 与本 skill 的关联点:

• 不假设 —— 最强落地是 RALPLAN-DR 强制 ≥ 2 个 viable options + 显式 invalidation rationale。绝不只给 1 个方案。