Individual skill
create-implementation-plan
Turn a refined requirements document into a structured implementation PLAN.md a fresh session can execute. Planning only — decides the "how", not the "what". Invoke manually only.
skills/create-implementation-plan/SKILL.md
Source commit bc5e2cd450b25fa64e4ba3127f3e9b6ab33923c3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 84
- Repository last updated
- Nov 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- spec-driven-development Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Create Implementation Plan
**Planning only** — no code changes, no execution. You produce one document: an implementation plan
that is the contract for a later execution session.
This is the **"how", not the "what"**. The "what" was settled in an earlier refinement step and
lives in the requirements document you're given; do not redefine scope. But you **must flag** any
gap, ambiguity, or inconsistency you find in the requirements — surface it, never paper over it.
## Golden rule
**Never guess — ask.** With one limit: anything resolvable by reading the codebase, resolve by
reading the codebase; only questions the code cannot settle go to the user.