Writing Implementation Plans

VerifiedCaution

Converts design specifications into detailed, executable task lists with TDD workflow. Ensures each step is micro-sized, atomic commits, and no placeholders.

Sby Skills Guide Bot
DevelopmentIntermediate
7/26/2026
Claude Code
#tdd#implementation-planning#task-breakdown#atomic-commits#claude-code

Recommended for

Automated summary

Turns a settled requirement or design into a detailed implementation plan broken into TDD micro-tasks with atomic commits, written to IMPLEMENTATION_PLAN.md.

Strengths

  • Forces 2-5 minute tasks with one git commit each, making progress checkable
  • Applies an explicit red/green/refactor loop for every feature
  • Bans placeholders like TBD/TODO, so all logic must be decided while planning
  • Requires a file map of what will be created or changed, plus verification commands per task

Limitations

  • Output is mandated in Traditional Chinese, which won't suit French or English teams
  • Assumes a Claude Code setup with CLAUDE.md and a /run command available
  • Produces the plan only — no code is written or executed
When to use it

Use it once the design is approved, to get a reviewable, executable plan before any code changes.

When not to use it

Skip it for one-line fixes or exploratory spikes whose scope isn't settled yet.

Security analysis

Caution
Quality score82/100

The skill is a planning aid and contains no destructive, exfiltrating, or obfuscated instructions. However, it declares Terminal access and directs test execution plus atomic git commits, so it carries moderate operational risk through powerful tools used for legitimate development purposes.

Findings
  • •Declares the Terminal tool and instructs running validation commands and creating git commits, which is legitimate but can modify repository state/history if followed broadly.
  • •References `CLAUDE.md` and a `/run` command without defining their safeguards or scope.
How this analysis is made

Examples

Plan for a new feature
I've finalized the design for JWT-based authentication. Before touching any code, write a detailed TDD implementation plan to IMPLEMENTATION_PLAN.md with bite-sized tasks, atomic commits and verification commands for each step.
Turn a design doc into tasks
Here is our design doc for the invoice export module. Break it into a step-by-step implementation plan with a file structure map and red/green/refactor steps per feature.

name: sp-writing-plans description: 當你有明確需求或設計方案時,在動手改代碼前,用來撰寫多步驟的詳細實作計畫。 allowed-tools: Terminal, Read, Write, Edit, Glob, Grep

超級能力:撰寫實作計畫 (Writing Plans)

你現在是資深軟體架構師。你的任務是將設計方案轉化為一系列極細、可執行且具備測試驗證的任務清單。

核心規則 (Core Rules)

  1. 微型化任務 (Bite-sized):每個步驟必須夠小,預計在 2-5 分鐘內即可完成。
  2. 原子化提交 (Atomic Commits):每個任務完成後都必須有一個 git commit。
  3. 嚴禁佔位符:計畫中不可出現 "TBD"、"TODO" 等模糊字眼,所有邏輯必須在計畫階段想清楚。
  4. 地圖先行:在開始列任務前,先列出將會建立或修改的文件結構圖。

TDD 工作流 (Test-Driven Development)

每個功能的實作計畫必須包含:

  • 紅燈 (Red):編寫一個會失敗的測試代碼並執行驗證。
  • 綠燈 (Green):編寫最少量的程式碼使測試通過並執行驗證。
  • 重構 (Refactor):優化代碼結構,確保其符合 CLAUDE.md 的規範。

計畫格式要求

計畫必須寫入 IMPLEMENTATION_PLAN.md,結構如下:

  • 目標摘要
  • 文件架構圖
  • 任務列表(包含檢查框 [ ])
  • 每個任務需註明:預期行為、驗證指令、相關檔案。

輸出要求

  • 全程使用「繁體中文」。
  • 完成計畫後詢問:『這個計畫看起來沒問題嗎?準備好執行 /run 指令了嗎?』

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/writing-implementation-plans-ms1aw4iz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/writing-implementation-plans-ms1aw4iz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/writing-implementation-plans-ms1aw4iz/download' --output '.skill-downloads/writing-implementation-plans-ms1aw4iz/SKILL.md.part' && mv '.skill-downloads/writing-implementation-plans-ms1aw4iz/SKILL.md.part' '.skill-downloads/writing-implementation-plans-ms1aw4iz/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Terminal, Read, Write, Edit, Glob, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/writing-implementation-plans-ms1aw4iz/SKILL.md' && test -s '.skill-downloads/writing-implementation-plans-ms1aw4iz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/sp-writing-plans' && cp -R '.skill-downloads/writing-implementation-plans-ms1aw4iz' '.claude/skills/sp-writing-plans'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/writing-implementation-plans-ms1aw4iz'

openskills read 'writing-implementation-plans-ms1aw4iz'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/writing-implementation-plans-ms1aw4iz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills