sp-writing-plans
Create actionable, multi-step implementation plans before coding, following TDD principles and atomic commits.
Install
mkdir -p .claude/skills/sp-writing-plans && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15990" && unzip -o skill.zip -d .claude/skills/sp-writing-plans && rm skill.zipInstalls to .claude/skills/sp-writing-plans
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
當你有明確需求或設計方案時，在動手改代碼前，用來撰寫多步驟的詳細實作計畫。Key capabilities
- →Break down design solutions into small, executable tasks
- →Ensure each task can be completed within 2-5 minutes
- →Require an atomic git commit after each task completion
- →Prohibit vague placeholders like TBD or TODO in plans
- →Outline the file structure before listing tasks
- →Integrate Red-Green-Refactor workflow into task planning
How it works
The skill translates design solutions into a series of small, test-validated tasks, enforcing a TDD workflow and strict planning requirements.
Inputs & outputs
When to use sp-writing-plans
- →Planning a complex feature implementation
- →Drafting a TDD-based development roadmap
- →Defining file structures for new features
- →Breaking down architectural designs into tasks
About this skill
超級能力：撰寫實作計畫 (Writing Plans)
你現在是資深軟體架構師。你的任務是將設計方案轉化為一系列極細、可執行且具備測試驗證的任務清單。
核心規則 (Core Rules)
- 微型化任務 (Bite-sized)：每個步驟必須夠小，預計在 2-5 分鐘內即可完成。
- 原子化提交 (Atomic Commits)：每個任務完成後都必須有一個 git commit。
- 嚴禁佔位符：計畫中不可出現 "TBD"、"TODO" 等模糊字眼，所有邏輯必須在計畫階段想清楚。
- 地圖先行：在開始列任務前，先列出將會建立或修改的文件結構圖。
TDD 工作流 (Test-Driven Development)
每個功能的實作計畫必須包含：
- 紅燈 (Red)：編寫一個會失敗的測試代碼並執行驗證。
- 綠燈 (Green)：編寫最少量的程式碼使測試通過並執行驗證。
- 重構 (Refactor)：優化代碼結構，確保其符合
CLAUDE.md的規範。
計畫格式要求
計畫必須寫入 IMPLEMENTATION_PLAN.md，結構如下：
- 目標摘要
- 文件架構圖
- 任務列表（包含檢查框
[ ]） - 每個任務需註明：預期行為、驗證指令、相關檔案。
輸出要求
- 全程使用「繁體中文」。
- 完成計畫後詢問：『這個計畫看起來沒問題嗎？準備好執行
/run指令了嗎？』
When not to use it
- →When the requirements or design solutions are not clear
- →When a detailed, step-by-step implementation plan is not needed
- →When the user prefers not to follow a TDD workflow
Limitations
- →Requires clear requirements or design solutions as input
- →Strictly enforces a TDD workflow
- →Prohibits vague language in the plan
How it compares
This workflow enforces a highly granular, test-driven approach to implementation planning, ensuring each step is atomic and validated, unlike less structured planning methods.
Compared to similar skills
sp-writing-plans side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sp-writing-plans (this skill) | 0 | 4mo | No flags | Intermediate |
| spec-workflow | 10 | 8mo | No flags | Intermediate |
| feature-design-assistant | 6 | 7mo | No flags | Intermediate |
| spec | 0 | 1mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.
feature-design-assistant
davila7
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
spec
AndrewDryga
Design an opinionated, boring-by-default implementation plan before writing code. Use when a change spans more than one file or context, when the approach isn't obvious, or when asked to plan/design/think through a feature. Produces a small-step, verifiable plan to approve before /work.
brainstorming
obra
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.