Test-First Implementation Plan
gittower/git-flow-next
Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.
Produce a structured implementation plan (no code) from an existing specification or deep analysis.
Install Implementation Plan
$ npx skills add POW-Software/ByteSync --skill implementation-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install POW-Software/ByteSync implementation-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/POW-Software/ByteSync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementation-plan .claude/skills/implementation-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 "implementation-plan" agent skill from https://github.com/POW-Software/ByteSync/tree/master/skills/implementation-plan into .claude/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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/POW-Software/ByteSync/tree/master/skills/implementation-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 POW-Software/ByteSync --skill implementation-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install POW-Software/ByteSync implementation-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/POW-Software/ByteSync.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/implementation-plan .agents/skills/implementation-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 "implementation-plan" agent skill from https://github.com/POW-Software/ByteSync/tree/master/skills/implementation-plan into .agents/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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 POW-Software/ByteSync --skill implementation-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install POW-Software/ByteSync implementation-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/POW-Software/ByteSync.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/implementation-plan .cursor/skills/implementation-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 "implementation-plan" agent skill from https://github.com/POW-Software/ByteSync/tree/master/skills/implementation-plan into .cursor/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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/POW-Software/ByteSync.git --path skills/implementation-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 POW-Software/ByteSync --skill implementation-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install POW-Software/ByteSync implementation-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/POW-Software/ByteSync.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/implementation-plan .gemini/skills/implementation-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 "implementation-plan" agent skill from https://github.com/POW-Software/ByteSync/tree/master/skills/implementation-plan into .gemini/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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 POW-Software/ByteSync implementation-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 POW-Software/ByteSync --skill implementation-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/POW-Software/ByteSync.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/implementation-plan .github/skills/implementation-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 "implementation-plan" agent skill from https://github.com/POW-Software/ByteSync/tree/master/skills/implementation-plan into .github/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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 POW-Software/ByteSync --skill implementation-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 POW-Software/ByteSync implementation-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/POW-Software/ByteSync.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/implementation-plan .opencode/skills/implementation-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 "implementation-plan" agent skill from https://github.com/POW-Software/ByteSync/tree/master/skills/implementation-plan into .opencode/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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.
Facts
- Skill name
implementation-plan- GitHub stars
- 172
- Token cost
- ~391 tokens
- SKILL.md length
- 173 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produce a structured implementation plan (no code) from an existing specification or deep analysis.
- Tasks that involve Planning
- SKILL.md covers Overview, Workflow, Output Format and Constraints
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Test strategy
What it does
Implementation Plan is an agent skill from POW-Software/ByteSync. Produce a structured implementation plan (no code) from an existing specification or deep analysis. Use after a spec is written to outline steps, file touch points, sequencing, and test strategy without writing code.
Its SKILL.md is about 390 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Planning and Test strategy. The repository describes itself as: ByteSync is a free and open-source tool for file synchronization, backup, and deduplication. It works locally or remotely, with no VPNs or firewall configuration required… The licence is MIT.
When your agent uses it
- Tasks that involve Planning
- Tasks that involve Test strategy
Example prompts
- “/implementation-plan”
What it can do on your machine
Read from SKILL.md and the folder at commit 397a1d1. 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 Plan loads about 391 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 173 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 POW-Software/ByteSync at commit 397a1d1, republished under its MIT licence (© POW-Software). 173 words, ~391 tokens.
Download SKILL.mdSave it as
.claude/skills/implementation-plan/SKILL.md (or your agent's skills folder).- name
- implementation-plan
- description
- Produce a structured implementation plan (no code) from an existing specification or deep analysis. Use after a spec is written to outline steps, file touch points, sequencing, and test strategy without writing code.
Implementation Plan
Overview
Transform an existing specification into a clear, ordered implementation plan with concrete steps, affected areas, and test execution sequence. Do not write code.
Workflow
- Confirm inputs
- Ensure a specification already exists in the current context.
- If missing, ask for the spec or a link to it.
- Identify workstreams
- Break the spec into discrete steps: core logic, validation, UI, persistence, integration, tests, tooling.
- Map each step to files/areas referenced in the spec.
- Order the steps
- Prefer foundational utilities first, then integrations, then UI, then tests.
- Highlight prerequisites and dependencies between steps.
- Define test strategy
- List the test layers to update (unit/integration/e2e).
- Specify the target projects and key scenarios.
- Include build/test command order when relevant.
- Call out risks and checkpoints
- Note migration or compatibility concerns.
- Identify risky changes that warrant extra verification.
Output Format
- Title
- Assumptions
- Step-by-step plan (numbered)
- Files/Areas to touch (bulleted)
- Test plan (bulleted)
- Risks/Checkpoints
Constraints
- Do not generate code.
- Ask questions only if the specification is missing or ambiguous.
- Keep plan concise but actionable.
© POW-Software, 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 skills/implementation-plan of POW-Software/ByteSync.
Open the folder on GitHubat commit 397a1d1
Compare with similar skills
Implementation Plan 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 this skillPOW-Software/ByteSync | 172 | — | ~391 | Automated safety check: Pass | MIT | |
| Test-First Implementation Plangittower/git-flow-next | 458 | — | ~1.3k | Automated safety check: Notes | Custom licence | |
| Fable Disciplineassafkip/kipi-system | 112 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Feature Development WorkflowQwenLM/qwen-code | 28k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Foreman PlanVisionForge-OU/foreman | 444 | — | ~1k | Automated safety check: Pass | Custom licence | |
| Engineering Plan Reviewgarrytan/gstack | 136k | — | ~13k | Automated safety check: Notes | MIT |
Similar skills
Fable Discipline
assafkip/kipi-system
Teaches staged, verifiable coding habits for multi-file tasks and ships a hook that blocks tests from touching live data.
Feature Development Workflow
QwenLM/qwen-code
Phased workflow for non-trivial qwen-code features: investigate, design doc, E2E test plan, baseline dry-run, implement, verify, self-audit, review and iterate.
Foreman Plan
VisionForge-OU/foreman
Headless implementation-plan authoring for the Foreman planning stage.
Engineering Plan Review
garrytan/gstack
Reviews an execution plan or design doc before coding, covering architecture, data flow, edge cases, test coverage and performance, one issue at a time.
Improve
fossasia/eventyay-interpretation
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.
More from POW-Software/ByteSync
Gh Issue Specifier
POW-Software/ByteSync
Analyze a GitHub issue in depth and produce a detailed specification based on codebase analysis.
Create PR
POW-Software/ByteSync
Push the current branch and create a Pull Request for ByteSync.
Perform Implement Plan
POW-Software/ByteSync
Execute an implementation plan end-to-end in the ByteSync repo.
Related
Categories
Questions about Implementation Plan
What does Implementation Plan do?
Produce a structured implementation plan (no code) from an existing specification or deep analysis. Implementation Plan is an agent skill from POW-Software/ByteSync. Produce a structured implementation plan (no code) from an existing specification or deep analysis.
When should I use Implementation Plan?
Implementation Plan fits situations like: tasks that involve Planning; tasks that involve Test strategy.
How do I install Implementation Plan in Claude Code?
Run `npx skills add POW-Software/ByteSync --skill implementation-plan -a claude-code`. Or copy the skill folder (skills/implementation-plan in POW-Software/ByteSync) into .claude/skills/implementation-plan in your project. Claude Code loads it when a task matches its description.
How do I install Implementation Plan in Codex?
Run `npx skills add POW-Software/ByteSync --skill implementation-plan -a codex`. Or copy the skill folder (skills/implementation-plan in POW-Software/ByteSync) into .agents/skills/implementation-plan in your project. Codex loads it when a task matches its description.
Can I use Implementation Plan 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 POW-Software/ByteSync --skill implementation-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/implementation-plan, .gemini/skills/implementation-plan, .github/skills/implementation-plan and .opencode/skills/implementation-plan in your project.
What does Implementation Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Implementation Plan is instructions for the agent only.
Does Implementation Plan 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 Plan 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 Plan use?
Implementation Plan 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 Plan use?
About 391 tokens (SKILL.md is roughly 1.6k 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 Plan?
Skills that share tags, products or a category with Implementation Plan: Test-First Implementation Plan (gittower/git-flow-next, 458 stars), Fable Discipline (assafkip/kipi-system, 112 stars), Feature Development Workflow (QwenLM/qwen-code, 28k stars) and Foreman Plan (VisionForge-OU/foreman, 444 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementation Plan?
POW-Software (a GitHub organization) maintains it in POW-Software/ByteSync, which has 172 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on May 7, 2026.
Source: POW-Software/ByteSync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.