writing-plans

Generates structured, TDD-aligned implementation plans with exact file paths, code snippets, test commands, and commit steps for multi-step software tasks.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/qiushibang/skill-creator-pro --skill writing-plans-qiushibang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/qiushibang/skill-creator-pro/tree/main/references/superpowers/writing-plans
Command: npx skills add https://github.com/qiushibang/skill-creator-pro --skill writing-plans-qiushibang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of incomplete, inconsistent implementation plans that lead to engineer rework, missed requirements, or incorrect code when building multi-step software features. It ensures all necessary context, file changes, test steps, and requirements are documented clearly upfront for any engineer, regardless of their familiarity with the codebase.

Core Features & Use Cases

  • Structured Task Decomposition: Breaks down specs into bite-sized, 2-5 minute actionable steps with exact file paths, code snippets, and test commands for each task.
  • TDD Alignment: Enforces test-first development steps, including writing failing tests, verifying failure, implementing minimal code, and confirming tests pass for every feature.
  • Use Case: For example, when implementing a new user notification system, this Skill generates a full plan with all required test cases, implementation code, and commit steps, so any engineer can complete the work correctly without prior context of the codebase.

Quick Start

Use the writing-plans skill to generate a complete implementation plan for the new user notification feature described in the product spec.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan for multi-step software development tasks?

To create an implementation plan, decompose software development tasks into structured, 2-5 minute actionable steps with exact file paths, code snippets, and test commands. This ensures engineers have full codebase context and requirements documented upfront for error-free implementation.

What is TDD-aligned task decomposition in engineering workflows?

TDD-aligned task decomposition breaks specs into bite-sized steps enforcing test-first development: writing failing tests, verifying failure, implementing minimal code, and confirming tests pass. This workflow aligns implementation planning with test-driven development practices for each feature.

How do I write an implementation plan for engineers lacking codebase context?

Write an implementation plan providing exact file paths, code snippets, test commands, and commit steps. This placeholder-free documentation gives any engineer complete tooling and requirements context, enabling them to correctly implement features or refactors without prior codebase knowledge.

Can I use this implementation planning method for bug fixes and refactoring?

Yes, you can use this implementation planning method for bug fixes and refactoring. It applies to engineering teams implementing new features or refactoring by enforcing structured documentation with exact file paths and test commands for any multi-step software task.

What's the best way to structure actionable documentation for multi-step dev tasks?

The best way to structure actionable documentation is decomposing tasks into 2-5 minute steps with exact file paths, code snippets, and test commands. This placeholder-free approach ensures all necessary context, file changes, and requirements are documented clearly upfront.