writing-plans

Generates detailed multi-task implementation plans from specs with TDD steps and file mappings.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/kangjuhyup/study --skill writing-plans-kangjuhyup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/kangjuhyup/study/tree/main/scoped-superpowers-ab/workflow-code-benchmark/fixture/workflows/full/skills/writing-plans
Command: npx skills add https://github.com/kangjuhyup/study --skill writing-plans-kangjuhyup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: tasks end up too vague, placeholders slip in, and engineers without codebase context get stuck. This Skill produces a complete, bite-sized implementation plan that an engineer with zero project context can execute task by task. ## Core Features & Use Cases - Structured Plan Generation: Creates a plan document with a mandatory header (goal, architecture, tech stack, spec reference, global constraints) saved to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. - Bite-Sized TDD Tasks: Breaks work into tasks with exact file paths, interface contracts (consumes/produces), and 2-5 minute steps following the failing-test, implement, verify, commit cycle. - Placeholder Prevention & Self-Review: Enforces a no-placeholder policy (no TODOs or vague steps) and runs a self-review checklist covering spec coverage, placeholder scan, and type consistency. - Execution Handoff: Offers subagent-driven or inline execution after the plan is saved, with a reviewer prompt template for validating the finished plan. - Use Case: Given a feature spec for a new API endpoint, produce a plan where each task lists exact files to create or modify, real test code, run commands with expected output, and commit commands. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan from your spec document before writing any code.

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 spec before coding?

Provide the spec or requirements and invoke the writing-plans skill before touching code. It maps the file structure, decomposes work into right-sized tasks with exact file paths, and writes TDD steps with real test code, run commands, and commit instructions.

What makes a good task breakdown for an implementation plan?

Each task should be the smallest unit carrying its own test cycle, ending with an independently testable deliverable. Steps within a task are single 2-5 minute actions: write the failing test, verify it fails, implement minimally, verify it passes, then commit.

Where are 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.

Can a plan cover multiple independent subsystems?

No. If the spec spans multiple independent subsystems, the skill suggests breaking it into separate plans, one per subsystem. Each plan should produce working, testable software on its own.

Why does the plan forbid placeholders like TODO or TBD?

Placeholders are treated as plan failures because the executing engineer may have zero context and read tasks out of order. Every step must contain actual code, exact commands, and expected output so implementation never stalls on missing details.

What happens after the implementation plan is written?

The skill offers two execution options: subagent-driven development, which dispatches a fresh subagent per task with review between tasks, or inline execution with batch processing and checkpoints. A reviewer prompt template can also validate the plan against the spec.