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
撰寫實作計畫
沿用使用者指定的計畫或專案現有位置；沒有慣例時使用 IMPLEMENTATION_PLAN.md。
計畫至少寫明目標、範圍、必要的檔案／模組、步驟依賴、預期行為與驗證方法。依可獨立驗收的成果分步，不固定每步分鐘數或每步提交。
- 先讀與本次決策直接相關的入口及規範；只有跨模組設計需要時才建立結構圖。
- 未確定的事項寫成有影響與解決方式的待確認項，不用沒有行動意義的佔位符，也不假稱所有細節已知。
- 使用者要求 test-first，或已批准 TDD 時，採每個行為一個 red → green → 必要的 refactor 切片。其他工作選用與風險相稱的現有檢查。
- 每項指明何時算完成及失敗後怎麼處理；在已授權範圍內修復並重跑受影響檢查。
- Commit／push 依原始授權及專案慣例安排，不用計畫自行擴張發布權限。
需要計畫審查時提交具體方案並等待；使用者已批准執行時接續完成工作。以繁體中文說明計畫與未決事項。
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 | 5mo | No flags | Intermediate |
| spec-workflow | 10 | 10mo | No flags | Intermediate |
| feature-design-assistant | 6 | 8mo | No flags | Intermediate |
| spec | 0 | 3mo | 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.