skills.rest
yuquanliu1-dot
yuquanliu1-dotCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert multi-step specifications into executable implementation plans with TDD tasks.

Updated Aug 23, 2026
Search Tags:#tdd#documentation#implementation planning#test-first#git commits#spec decomposition
One-click install
npx skills add https://github.com/yuquanliu1-dot/Test --skill writing-plans-yuquanliu1-dot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/yuquanliu1-dot/Test/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/yuquanliu1-dot/Test --skill writing-plans-yuquanliu1-dot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns ambiguous multi-step requirements into a clear, testable engineering plan that a developer can execute with minimal knowledge of the codebase.

Core Features & Use Cases

  • Multi-step implementation planning: Breaks work into bite-sized tasks with explicit tests, commands, and commits.
  • Zero-context friendly guidance: Documents what files to touch, what to check in docs, and how to test changes effectively.
  • Plan structure enforcement: Requires a standardized plan header and consistent task format to reduce ambiguity.
  • Use Case: You have a new feature spec and need an engineer to implement it safely and quickly without getting lost in unfamiliar tooling or architecture.

Quick Start

Use the writing-plans skill when you have a spec or requirements for a multi-step task, and then save the generated plan to docs/superpowers/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 a feature spec into test-first implementation steps?▼

Implementation planning decomposes multi-step specifications into bite-sized tasks with explicit tests, file-by-file guidance, commands, and git commits to reduce ambiguity.

What is the best way to create an implementation plan for engineers with no codebase context?▼

Generate standardized plans with file-by-file guidance, explicit tests, commands, and commits, enabling engineers to execute multi-step specifications safely with minimal codebase knowledge.

How do I enforce a standardized structure for TDD implementation plans?▼

Apply strict formatting with a standardized plan header, step-by-step checklists with code blocks for implementations and tests, and deterministic save locations to enforce consistent plan structure.

Where should generated implementation plans be saved in the repository?▼

Save generated plans to the deterministic path docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md to maintain consistent file retrieval and version control.

Can I use this approach for multi-step feature development with uncertain tooling?▼

Yes, it applies to feature development with uncertain tooling by providing a structured workflow for testing and committing, requiring only a multi-step specification as input.

Related Skills

Explore More Software Engineering Skills→
Matt-Aurora-VenturesMatt-Aurora-Ventures
58

writing-plans

Generate detailed implementation plans from specs for multi-step software tasks.

Community
Advanced
beratcelik1beratcelik1
1

work

Execute development plans into tasks, code changes, tests, and commits.

Community
Intermediate
chuangkevinchuangkevin

subagent-driven-development

Dispatch fresh subagents to implement, test, and commit each task.

Community
Advanced
AlexiosBluffMaraAlexiosBluffMara
2

writing-plans

Generates implementation plans with tasks, file paths, and example code from a project spec.

Community
Advanced