implementation-planning
From the author
Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.
Install
npx skills add cbrock84/headcount --skill implementation-planning -a claude-code
Installs to .claude/skills/implementation-planning/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 89
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- make-planthedotmack/claude-memCreate a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.Planning★ 102.1K
- writing-plansjnMetaCode/superpowers-zh当你有规格说明或需求用于多步骤任务时使用,在动手写代码之前Writing★ 8.4K
- task-planningpaperclipai/paperclipWrite or revise a useful Paperclip plan with a clear outcome and verification. Use when a plan is requested or uncertainty needs resolving before execution.Planning★ 105.4K
- speckit-tasksforyourhealth111-pixel/Vibe-SkillsBreak down implementation plans into actionable task lists. Use after planning to create a structured task breakdown. Generates tasks.md with ordered, dependency-aware tasks.Planning★ 3.7K
- dothedotmack/claude-memExecute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.Planning★ 102.1K
- spec-driven-developmentaddyosmani/agent-skillsCreates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.Planning★ 109.1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in