From chevp-ai-framework
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/chevp-ai-framework:create-exp-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Step 2 artifact: captures HOW the feature will be built, the chosen approach, risks, and acceptance criteria.
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).
Whole-repo audit for over-engineering: finds dead code, unnecessary abstractions, stdlib-replaceable dependencies. Outputs ranked findings and net line/dep savings.
npx claudepluginhub chevp/chevp-ai-framework