Requirements
rizsotto/Bear
Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…
Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints.
MITAuto-check passed
Install Implementation Planning
$ npx skills add cbrock84/headcount --skill implementation-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount implementation-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/technology/skills/implementation-planning .claude/skills/implementation-planning && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "implementation-planning" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/implementation-planning into .claude/skills/implementation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/implementation-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill implementation-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount implementation-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/technology/skills/implementation-planning .agents/skills/implementation-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "implementation-planning" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/implementation-planning into .agents/skills/implementation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill implementation-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount implementation-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/technology/skills/implementation-planning .cursor/skills/implementation-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "implementation-planning" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/implementation-planning into .cursor/skills/implementation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/technology/skills/implementation-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill implementation-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount implementation-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/technology/skills/implementation-planning .gemini/skills/implementation-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "implementation-planning" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/implementation-planning into .gemini/skills/implementation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount implementation-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill implementation-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/technology/skills/implementation-planning .github/skills/implementation-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "implementation-planning" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/implementation-planning into .github/skills/implementation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill implementation-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount implementation-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/technology/skills/implementation-planning .opencode/skills/implementation-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "implementation-planning" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/implementation-planning into .opencode/skills/implementation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
implementation-planning- GitHub stars
- 2k
- Token cost
- ~485 tokens
- SKILL.md length
- 261 words
- Files
- 1
- Skills in repo
- 177
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints.
- SKILL.md covers When a plan is worth writing, Writing the plan, Executing and Never
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Implementation Planning is an agent skill from cbrock84/headcount. 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.
Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
Example prompts
- “Use the implementation-planning skill to turn a spec or requirement into a written plan a separate session or agent can execute, then drives that…”
- “/implementation-planning”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Implementation Planning loads about 485 tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 261 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 261 words, ~485 tokens.
Download SKILL.mdSave it as
.claude/skills/implementation-planning/SKILL.md (or your agent's skills folder).- name
- implementation-planning
- description
- 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.
Implementation planning
When a plan is worth writing
More than about three steps, more than one file of consequence, or any work that will be handed off. Below that, planning costs more than it saves.
Writing the plan
A plan is executable when someone who was not in the conversation can follow it without guessing. That means every step names:
- The change — the file or surface, and what it should do afterward.
- The proof — the command that shows it worked. "Run the tests" is not a step; the exact invocation is.
- The checkpoint — whether a human reviews before the next step starts.
Order steps so the system is working at the end of each one. A plan whose midpoint is a broken build cannot be paused, and every plan gets paused.
State up front what is out of scope. Plans fail by accretion far more often than by being wrong.
Executing
- One step at a time, in order. Finish and verify before starting the next.
- Stop at checkpoints. The point of a checkpoint is that continuing without it is a mistake.
- When reality contradicts the plan, stop and amend the plan. Do not improvise past it silently — the plan is the shared state, and a stale plan is worse than none.
- Track status in the plan as you go, so an interrupted run can resume.
Never
- Start writing code because the plan felt obvious. If it was obvious, writing it costs a minute.
- Mark a step done without running its proof.
- Expand scope mid-execution. Note it, finish the plan, then decide.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/technology/skills/implementation-planning of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Implementation Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Implementation Planning this skillcbrock84/headcount | 2k | — | ~485 | Automated safety check: Pass | MIT | |
| Requirementsrizsotto/Bear | 6.5k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Turn This Into A Threadsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Aria Required Attrthedaviddias/Front-End-Checklist | 74k | — | ~459 | Automated safety check: Pass | MIT | |
| Aria Required Parentthedaviddias/Front-End-Checklist | 74k | — | ~498 | Automated safety check: Pass | MIT | |
| Browser Requiredthedaviddias/Front-End-Checklist | 74k | — | ~448 | Automated safety check: Pass | MIT |
Similar skills
Turn This Into A Thread
sickn33/agentic-awesome-skills
Turn a long idea, transcript, article or draft into a Twitter/X thread where every tweet stands alone.
Aria Required Attr
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Include required ARIA attributes for roles.
Aria Required Parent
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure ARIA roles are contained by required parent roles.
Browser Required
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Perform browser-based performance audits.
Requirements Clarification
asgeirtj/system_prompts_leaks
Clarify a material user-owned product decision before substantive implementation commitments.
More from cbrock84/headcount
All 177 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
AI Search Optimization
cbrock84/headcount
Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf.
Questions about Implementation Planning
What does Implementation Planning do?
Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Implementation Planning is an agent skill from cbrock84/headcount. Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints.
How do I install Implementation Planning in Claude Code?
Run `npx skills add cbrock84/headcount --skill implementation-planning -a claude-code`. Or copy the skill folder (plugins/technology/skills/implementation-planning in cbrock84/headcount) into .claude/skills/implementation-planning in your project. Claude Code loads it when a task matches its description.
How do I install Implementation Planning in Codex?
Run `npx skills add cbrock84/headcount --skill implementation-planning -a codex`. Or copy the skill folder (plugins/technology/skills/implementation-planning in cbrock84/headcount) into .agents/skills/implementation-planning in your project. Codex loads it when a task matches its description.
Can I use Implementation Planning in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill implementation-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementation-planning, .gemini/skills/implementation-planning, .github/skills/implementation-planning and .opencode/skills/implementation-planning in your project.
What does Implementation Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Implementation Planning is instructions for the agent only.
Does Implementation Planning access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Implementation Planning safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Implementation Planning use?
Implementation Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Implementation Planning use?
About 485 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Implementation Planning?
Skills that share tags, products or a category with Implementation Planning: Requirements (rizsotto/Bear, 6.5k stars), Turn This Into A Thread (sickn33/agentic-awesome-skills, 47k stars), Aria Required Attr (thedaviddias/Front-End-Checklist, 74k stars) and Aria Required Parent (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementation Planning?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,001 GitHub stars. The repository holds 177 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.