skills.rest
SPURSGO
SPURSGOCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Translate multi-step project requirements into structured implementation plans with task sequences, tests, and commits.

Updated Aug 23, 2026
Search Tags:#workflow#planning#documentation#task breakdown#test-driven development#software-development
One-click install
npx skills add https://github.com/SPURSGO/awesome-skills-cn --skill writing-plans-spursgo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/SPURSGO/awesome-skills-cn/tree/main/writing-plans
Command: npx skills add https://github.com/SPURSGO/awesome-skills-cn --skill writing-plans-spursgo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

当你需要把一个多步骤任务的规范转化为可执行的实现计划时，此技能提供结构化、逐步的任务清单，确保团队对目标、涉及的文件、测试和提交有清晰共识。

Core Features & Use Cases

  • 生成逐步任务粒度的计划，包含需要创建、修改的文件、测试与提交清单
  • 将计划保存为 docs/plans/YYYY-MM-DD-<feature-name>.md 的规范化文档，方便版本控制与审查
  • 适用于软件开发及需要明确执行步骤的工作流场景（需求分解、计划实施、代码审查前的准备）

Quick Start

Start by announcing: "I am using writing-plans to create an implementation plan." Then ensure the plan is prepared in a dedicated worktree and saved to docs/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down software development requirements into an actionable implementation plan?▼

Implementation planning translates multi-step software requirements into structured task sequences specifying files to modify, required tests, and commit checklists, ensuring clear team consensus on executable project steps.

What is the best way to enforce DRY, YAGNI, and TDD principles during task breakdown?▼

Task breakdown enforces DRY, YAGNI, and TDD principles by structuring executable implementation plans with explicit test sequences and commit checklists, guiding development workflows toward clean, test-driven code generation.

How should I store implementation plans for version control and code review?▼

Store implementation plans as normalized Markdown documents under docs/plans using the YYYY-MM-DD-<feature-name>.md filename format, facilitating version control tracking and pre-implementation code review preparation.

Can I use this planning workflow for non-software multi-step projects?▼

Planning workflows apply to any scenario requiring clear task sequences, including requirement decomposition and workflow planning, though the generated plans specifically enforce software development principles like TDD and commit checklists.

Do I need a dedicated Git worktree to create an executable implementation plan?▼

A dedicated Git worktree is recommended for preparing executable implementation plans, isolating structural planning documents and task breakdown processes from your main development branch before initiating code changes.

Related Skills

Explore More Software Engineering Skills→
okbest2024okbest2024

writing-plans

Convert vague specifications into step-by-step implementation plans.

Community
Intermediate
jlawsjlaws
2

cmd-workflow-write-plan

Create structured implementation plans with exact file paths, tests, and commits.

Community
Advanced
sylvandingsylvanding
9

file-todos

Create standardized markdown todo files with YAML frontmatter from code review feedback.

Community
Intermediate
hetsheth-droidhetsheth-droid

writing-plans

Draft task-oriented implementation plans from a project spec.

Community
Advanced