writing-plans

Generates detailed implementation plans with bite-sized TDD tasks from feature specifications.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill writing-plans-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/superpowers/skills/writing-plans
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill writing-plans-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature spec into working code often fails because engineers lack context about the codebase, file structure, and testing approach. This Skill converts a spec or requirements document into a comprehensive implementation plan with exact file paths, complete code snippets, and step-by-step TDD tasks that any engineer can follow without prior context. ## Core Features & Use Cases - Bite-Sized Task Decomposition: Breaks work into 2-5 minute steps following a write-test, verify-fail, implement, verify-pass, commit cycle. - Structured Plan Documents: Produces plans with a required header, file structure mapping, exact file paths, and checkbox-tracked steps saved to docs/superpowers/plans/. - Review and Execution Handoff: Dispatches a plan-document-reviewer subagent to validate completeness against the spec, then offers subagent-driven or inline execution. - Use Case: After brainstorming a new API feature, use this Skill to produce a dated plan document where each task lists exact files to create or modify, failing tests to write, and commit commands, ready for task-by-task execution. ## Quick Start Use the writing-plans skill to turn my feature spec into a step-by-step implementation plan with TDD tasks.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write an implementation plan from a feature spec?

Provide the spec or requirements document and the Skill produces a plan with a goal, architecture summary, file structure map, and tasks broken into 2-5 minute steps. Each task includes exact file paths, failing tests, minimal implementations, and commit commands.

How detailed should tasks be in a software implementation plan?

Each step should be one action taking 2-5 minutes, such as writing a failing test, running it to confirm failure, implementing minimal code, verifying it passes, and committing. Plans must include exact file paths and complete code rather than vague instructions.

Where are the generated implementation plans saved?

Plans are saved to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md by default. User preferences for plan location override this default path.

When should a spec be split into multiple implementation plans?

Split when the spec covers multiple independent subsystems. Each plan should produce working, testable software on its own, so one plan per subsystem keeps scope manageable and reviewable.

What happens after the implementation plan is written?

A plan-document-reviewer subagent checks completeness and spec alignment, with fixes applied until approval. You then choose subagent-driven execution with fresh agents per task or inline execution with batched checkpoints.