菜单
Use when a feature needs to be planned/designed in the Exploration step, or when the user says "EXP plan", "feature plan", "exploration plan", "design the feature". Produces an EXP plan/spec per chevp-ai-framework templates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | create-exp-plan |
| description | Use when a feature needs to be planned/designed in the Exploration step, or when the user says "EXP plan", "feature plan", "exploration plan", "design the feature". Produces an EXP plan/spec per chevp-ai-framework templates. |
Step 2 artifact: captures HOW the feature will be built, the chosen approach, risks, and acceptance criteria.
G1 must be passed. Before creating, verify via the gate-validator subagent (gate=G1). If G1 is not passed, block and redirect to /context.
guidelines/plan-granularity.md (project-level override takes precedence) for size limits and plan type.An EXP plan file. Status is Draft until human approves (required for G2).
Use when an approved EXP plan is ready to be implemented and a Production-Plan (PRD) is needed, or when the user says "PRD plan", "production plan", "produce", "implement EXP-NNN", "draft PRD". Produces a PRD per the chevp-ai-framework template.
Use when an out-of-scope item, Challenger-identified failure mode, or NOT-in-Scope row warrants its own future plan (Rule 12). Trigger phrases: "create proposal", "PROP for this", "open a proposal", "log this for later", "this is out of scope but worth tracking". Produces a `PROP-NNN` file per the plan-proposal template.
Use before requesting G2 approval for an EXP plan, or when scope changes are proposed mid-Production (Rule 11 / Challenger role). Trigger phrases: "run challenger", "challenge this plan", "stress-test the approach", "draft the challenger block", "what could go wrong with this plan". Produces the four mandatory Challenger sections per [02-exploration/challenger.md].
Use when an Exploration cycle is wrapping up and the `insights.md` learning artifact is needed (mandatory before G2), or when Production has revealed implementation surprises that must be appended (Rule 9 / Learning Loop). Trigger phrases: "write insights", "insights file", "what did we learn", "log insights", "update insights with implementation surprises".
Use when the user wants to mirror chevp-ai-framework plan files (context/plans/**/*.md) to GitHub Issues, or says "sync plans", "issue für §X.Y", "plans als issues anlegen", "create issues from plans", "spiegle backlog nach github". Wraps integration/github-issues/sync-plans-to-issues.py.
Use when the user wants to record an architecture decision, says "write an ADR", "new ADR", "document this decision", or when a non-trivial architectural choice is made during Context or Exploration that future contributors need to understand.