skills.rest
jayhjenkins
jayhjenkinsCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans from software specifications with task decomposition.

Updated Jan 3, 2026
Search Tags:#planning#documentation#TDD#task-breakdown#implementation-plan#engineering-workflow
One-click install
npx skills add https://github.com/jayhjenkins/Dev-Team-Full-SDLC --skill writing-plans-jayhjenkins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/jayhjenkins/Dev-Team-Full-SDLC/tree/main/vendor/superpowers/skills/writing-plans
Command: npx skills add https://github.com/jayhjenkins/Dev-Team-Full-SDLC --skill writing-plans-jayhjenkins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Core Features & Use Cases

  • Announce at start: "I'm using the writing-plans skill to create the implementation plan."
  • Context: This should be run in a dedicated worktree (created by brainstorming skill).
  • Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md
  • Bite-Sized Task Granularity: Each step is one action (2-5 minutes):
  • "Write the failing test" - step
  • "Run it to make sure it fails" - step
  • "Implement the minimal code to make the test pass" - step
  • "Run the tests and make sure they pass" - step
  • "Commit" - step

Plan Document Header

Every plan MUST start with this header:

# [Feature Name] Implementation Plan

> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

**Goal:** [One sentence describing what this builds]

**Architecture:** [2-3 sentences about approach]

**Tech Stack:** [Key technologies/libraries]

---

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan from unclear software specifications?▼

Task decomposition breaks complex features into 2-5 minute steps like writing failing tests, implementing minimal code, and committing frequently. This TDD-compatible approach ensures each step is one action, enabling frequent commits and continuous delivery.

What is included in a TDD implementation plan document?▼

An implementation plan document includes a header with goal, architecture, and tech stack, followed by bite-sized steps for writing failing tests, implementing code, running tests, and committing. It also identifies required files, tests, docs, and reviews.

How do I break down complex engineering tasks for developers with no codebase context?▼

Break down complex engineering tasks by creating bite-sized steps that document every file to touch, test, and check. This approach assumes zero codebase context and enforces DRY, YAGNI, and TDD principles for clear execution.

Can I use this planning workflow with version control and continuous delivery practices?▼

Yes, the planning workflow is compatible with version control and continuous delivery practices. It structures tasks to enforce frequent commits after each passing test, integrating seamlessly with standard engineering workflows.

Where should generated implementation plans be saved in the project directory?▼

Generated implementation plans should be saved to the `docs/plans/` directory using a date-prefixed naming convention like `YYYY-MM-DD-<feature-name>.md`. This organizes plan documents chronologically within the project structure.

What are the limitations of using automated task breakdown for software project planning?▼

Automated task breakdown relies on the clarity of the initial specification and assumes strict adherence to TDD. It may not suit projects requiring exploratory coding or those lacking a dedicated worktree environment for isolated planning.

Related Skills

Explore More Software Engineering Skills→
takemo101takemo101

create-worktree

Create isolated Git worktrees for parallel feature branches and copy environment files.

Community
Intermediate
qodex-aiqodex-ai
39

planning-documentation

Generate step-by-step implementation plans with file modifications, code examples, and testing procedures.

Official
Intermediate
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
bbohhu-progbbohhu-prog

writing-plans

Create implementation plans from specs, outlining files, tests, and documentation.

Community
Advanced