framework-plan
Explicit framework workflow: plan
SKILL.md.claude/skills/framework-plan/SKILL.md
GitHub/plan — Implementation plan
Use after a spec exists (or for small tasks, a verbal agreement). Prefer plan mode or explicit user approval before large edits.
Inputs
- Approved spec or tight task description.
- Relevant files the user pointed at.
Output
- Goal — What “done” means.
- Files / areas to touch — Paths or components.
- Approach — Steps in order; call out risky changes.
- Failing test stubs to write BEFORE touching implementation — Name the specific tests/assertions (mapped from spec acceptance criteria) that should be authored and confirmed failing first; map them to AGENTS.md commands.
- Rollback / flags — If feature-flagged or migratory.
Done when
- Another developer could execute the plan without guessing.
- Failing test stubs identified and ready to write before implementation begins.
- Test plan matches project conventions.
Note
If the user has not approved implementation, do not apply code changes until they confirm.