Implementation Plan Writer
imbue-ai/bouncer
Turns a feature's goals, requirements and architecture documents into a set of self-contained task files that a developer with no project context can follow.
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
$ npx skills add tailcallhq/forgecode --skill create-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tailcallhq/forgecode create-plan --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/tailcallhq/forgecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.forge/skills/create-plan .claude/skills/create-plan && 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 "create-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-plan into .claude/skills/create-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plan", 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/tailcallhq/forgecode/tree/main/.forge/skills/create-planType 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 tailcallhq/forgecode --skill create-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tailcallhq/forgecode create-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.forge/skills/create-plan .agents/skills/create-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-plan into .agents/skills/create-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plan", 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 tailcallhq/forgecode --skill create-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tailcallhq/forgecode create-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.forge/skills/create-plan .cursor/skills/create-plan && 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 "create-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-plan into .cursor/skills/create-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plan", 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/tailcallhq/forgecode.git --path .forge/skills/create-plan--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 tailcallhq/forgecode --skill create-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tailcallhq/forgecode create-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.forge/skills/create-plan .gemini/skills/create-plan && 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 "create-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-plan into .gemini/skills/create-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plan", 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 tailcallhq/forgecode create-planInstalls 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 tailcallhq/forgecode --skill create-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .github/skills && cp -r skills-src/.forge/skills/create-plan .github/skills/create-plan && 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 "create-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-plan into .github/skills/create-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plan", 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 tailcallhq/forgecode --skill create-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tailcallhq/forgecode create-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.forge/skills/create-plan .opencode/skills/create-plan && 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 "create-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-plan into .opencode/skills/create-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plan", 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.
create-planWrites a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
The agent first researches the codebase: its structure, the relevant files read in full, existing conventions, risks and data flows, citing sources as `filepath:line`. It then writes a plan into the `plans/` directory, named by date, task and version, for example `plans/2025-11-24-add-auth-v1.md`.
Every plan must pass `validate-plan.sh`, which the agent re-runs until errors and warnings are gone; a second script, `validate-all-plans.sh`, is also included. Implementation tasks have to use checkbox format rather than numbered lists or plain bullets, each with what, why, affected files and integration points, and the plan carries an objective, verification criteria, risks and alternative approaches. The skill is strictly about planning: no code, snippets or examples go into the plan, and nothing in the repository changes beyond the plan file. A plan template and an example plan sit in `references/`.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 92a5699. It shows what the files ask for, not the result of running them.
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.
Ships script files (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Implementation Plan Creator loads about 1.1k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 149 tokens; SKILL.md has 359 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.
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.
The full file from tailcallhq/forgecode at commit 92a5699, republished under its Apache-2.0 licence (© tailcallhq). 359 words, ~1,095 tokens.
.claude/skills/create-plan/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.Generate comprehensive implementation plans that provide strategic guidance without making actual code changes.
Research the codebase to understand:
Use search, sem_search, and read tools to examine the codebase. Use sage if deeper research is required for the use-case. Explicitly cite sources using filepath:line format in your plan.
Generate a Markdown plan file in plans/ directory with naming: plans/{YYYY-MM-DD}-{task-name}-v{N}.md
Example: plans/2025-11-24-add-auth-v1.md
MANDATORY: Run the validation script to ensure the plan meets all requirements:
./.forge/skills/create-plan/validate-plan.sh plans/{YYYY-MM-DD}-{task-name}-v{N}.mdFix any errors or warnings and re-validate until the plan passes all checks.
# [Task Name]
## Objective
[Clear statement of goal and expected outcomes]
## Implementation Plan
- [ ] 1. [First task with detailed description and rationale]
- [ ] 2. [Second task with detailed description and rationale]
- [ ] 3. [Third task with detailed description and rationale]
## Verification Criteria
- [Criterion 1: Specific, measurable outcome]
- [Criterion 2: Specific, measurable outcome]
## Potential Risks and Mitigations
1. **[Risk Description]**
Mitigation: [Specific mitigation strategy]
2. **[Risk Description]**
Mitigation: [Specific mitigation strategy]
## Alternative Approaches
1. [Alternative 1]: [Brief description and trade-offs]
2. [Alternative 2]: [Brief description and trade-offs]./.forge/skills/create-plan/validate-plan.sh after creation- [ ]) for ALL implementation tasksfilepath:line format for file references (e.g., crates/forge_repo/src/provider.rs:45)This is a planning-only skill:
If user requests implementation work, suggest switching to an implementation agent.
© tailcallhq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files (references) in .forge/skills/create-plan of tailcallhq/forgecode.
Open the folder on GitHubat commit 92a5699
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in tailcallhq/forgecode, which our catalogue first saw on October 7, 2026.
Implementation Plan Creator 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 Plan Creator this skilltailcallhq/forgecode | 7.6k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Implementation Plan Writerimbue-ai/bouncer | 400 | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Auditable Playbook Designercursor/plugins | 10k | 8 repos | ~1k | Automated safety check: Pass | None | |
| Vibe Workflow RouterKhazP/vibe-coding-prompt-template | 3.1k | — | ~544 | Automated safety check: Notes | MIT | |
| Launch Delivery PipelineYeachan-Heo/oh-my-claudecode | 40k | — | ~7.3k | Automated safety check: Pass | MIT | |
| Planning And Task Breakdownabashev/vfs-s3 | 106 | 8 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 |
imbue-ai/bouncer
Turns a feature's goals, requirements and architecture documents into a set of self-contained task files that a developer with no project context can follow.
cursor/plugins
Designs a step-by-step playbook for large or unfamiliar work, runs it as a loop of hypotheses and measurements, and logs decisions so a human can review them later.
KhazP/vibe-coding-prompt-template
Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed.
Yeachan-Heo/oh-my-claudecode
Delivery pipeline from mission brief to verified change: writes a spec, splits it into tickets, runs them in parallel, verifies and reports a decision log after a repo audit gate.
abashev/vfs-s3
Breaks work into ordered tasks. An agent skill from abashev/vfs-s3.
code-yeongyu/oh-my-openagent
Explore-first planning that turns a vague or large request into one decision-complete work plan, written only after your approval and executed by a separate worker.
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
tailcallhq/forgecode
Gives a systematic process for debugging the forge CLI: build in debug mode, check the latest help output, test with the non-interactive -p flag, and clone conversations before reproducing bugs.
tailcallhq/forgecode
Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.
tailcallhq/forgecode
Checks that ReasoningConfig fields are serialized into the right provider-specific JSON for OpenRouter, Anthropic, GitHub Copilot and Codex requests.
tailcallhq/forgecode
Pulls a GitHub release and every linked pull request, then writes polished, factual release notes from the combined set of changes.
tailcallhq/forgecode
Guidance for creating and updating agent skills: what skills provide, keeping context lean, choosing how specific to be, and how SKILL.md and bundled resources are laid out.
Categories
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes. The agent first researches the codebase: its structure, the relevant files read in full, existing conventions, risks and data flows, citing sources as `filepath:line`.md`.
Implementation Plan Creator fits situations like: being asked for a plan, roadmap or implementation strategy before coding starts; breaking a complex feature into trackable checkbox tasks; assessing risks and alternative approaches before an architectural change.
Run `npx skills add tailcallhq/forgecode --skill create-plan -a claude-code`. Or copy the skill folder (.forge/skills/create-plan in tailcallhq/forgecode) into .claude/skills/create-plan in your project. Claude Code loads it when a task matches its description.
Run `npx skills add tailcallhq/forgecode --skill create-plan -a codex`. Or copy the skill folder (.forge/skills/create-plan in tailcallhq/forgecode) into .agents/skills/create-plan in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tailcallhq/forgecode --skill create-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-plan, .gemini/skills/create-plan, .github/skills/create-plan and .opencode/skills/create-plan in your project.
Going by SKILL.md and its folder, Implementation Plan Creator needs a shell for the scripts in its folder. Our summary lists: Bash to run the bundled validation script.
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.
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.
Implementation Plan Creator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Implementation Plan Creator: Implementation Plan Writer (imbue-ai/bouncer, 400 stars), Auditable Playbook Designer (cursor/plugins, 10k stars), Vibe Workflow Router (KhazP/vibe-coding-prompt-template, 3.1k stars) and Launch Delivery Pipeline (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
tailcallhq (a GitHub organization) maintains it in tailcallhq/forgecode, which has 7,642 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.
Source: tailcallhq/forgecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.