skills.rest
chuangkevin
chuangkevinCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate step-by-step implementation plans with TDD tasks, file paths, code snippets, and commands.

Updated Mar 16, 2026
Search Tags:#tdd#spec-driven#execution-plan#task-decomposition#implementation-plans#developer-handoff
One-click install
npx skills add https://github.com/chuangkevin/project-bridge --skill writing-plans-chuangkevin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/chuangkevin/project-bridge/tree/main/skill/superpowers/writing-plans
Command: npx skills add https://github.com/chuangkevin/project-bridge --skill writing-plans-chuangkevin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers and teams often receive high-level specs without the actionable, step‑by‑step work breakdown needed to implement features reliably; this Skill converts vague requirements into precise, test-first implementation plans that a developer with no prior context can follow end-to-end.

Core Features & Use Cases

  • Complete task decomposition: Breaks a feature or subsystem into bite-sized, 2–5 minute actionable steps including explicit test-first steps and commit points.
  • File-level mapping: Lists exact files to create or modify, with clear responsibilities and minimal, focused file scopes.
  • Executable details: Provides full test and code snippets, exact commands to run, expected outputs, and a commit recipe for each step.
  • Handoff & review: Produces a saved markdown plan ready for subagent-driven execution or inline execution, and includes a reviewer prompt template for plan verification.
  • Use case: Turn a product spec for a new checkout flow into a series of failing tests, minimal implementations, validation runs, and commits that produce working, testable software.

Quick Start

Create an implementation plan from the given spec titled Add multi-page checkout and save it to the default docs/superpowers/plans path.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a software feature spec into an actionable implementation plan?▼

You can convert specifications into actionable developer work by decomposing features into 2–5 minute test-first steps, specifying exact file paths, code snippets, run commands, and commit instructions for each task.

What is spec-driven task decomposition for developer handoffs?▼

Spec-driven task decomposition for developer handoffs is converting high-level requirements into precise, file-specific, test-first implementation plans that engineers with no prior context can execute end-to-end.

How do I create a TDD execution plan for a multi-step engineering task?▼

Create a TDD execution plan by structuring the work into sequential steps that start with failing tests, provide minimal implementations, include validation run commands with expected outputs, and define commit points.

Does a good implementation plan need to specify exact file paths and run commands?▼

Yes, a complete implementation plan must list exact file create or modify paths, include executable test and code snippets, and specify run commands with expected outputs to ensure reliable developer handoffs.

Can I use an implementation plan for subagent-driven software execution?▼

Yes, you can use the generated markdown implementation plan for subagent-driven execution or inline execution, as it provides the precise file-level mapping and executable details required for automated or handoff workflows.

What's the best way to structure commits when following an execution plan?▼

The best way to structure commits in an execution plan is to define clear commit recipes at the end of each 2–5 minute step, ensuring each commit represents a test-first, minimal implementation that produces working software.

Related Skills

Explore More Software Engineering Skills→
GuidoBergmanGuidoBergman

create-epics-stories

Convert PRDs and architecture documents into epics and user stories with acceptance criteria.

Community
Advanced
TumeloRamaphosaTumeloRamaphosa

writing-plans

Convert implementation specifications into decomposed, testable task plans.

Community
Advanced
yashs33244yashs33244
1

writing-plans

Generate a detailed engineering implementation plan from a requirements spec.

Community
Advanced
zhentingWu-wztzhentingWu-wzt
6

superpowers:writing-plans

Generate test-driven implementation plans with task decomposition and file path mapping.

Community
Advanced