obra-superpowers-writing-plans

Name: obra-superpowers-writing-plans
Availability: InStock
Author: cpa03

Generate end-to-end implementation plans from specs into docs/plans markdown files.

Updated Jan 8, 2026

Search Tags:#planning #documentation #task-management #software-engineering #feature-development #plan-generation

Ready to run

npx skills add https://github.com/cpa03/blueprintify --skill obra-superpowers-writing-plans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: obra-superpowers-writing-plans
Source: https://github.com/cpa03/blueprintify/tree/main/.opencode/skill/obra-superpowers-writing-plans
Command: npx skills add https://github.com/cpa03/blueprintify --skill obra-superpowers-writing-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert scattered specifications into comprehensive, executable implementation plans that guide multi-step work before coding.

Core Features & Use Cases

Generates bite-sized tasks with clear ownership and acceptance criteria
Enforces DRY, TDD-oriented planning and documentation
Produces a plan document at docs/plans/YYYY-MM-DD-<feature-name>.md ready for execution

Quick Start

Create a detailed implementation plan from a feature spec and save it to docs/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about obra-superpowers-writing-plans

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

FAQPage Schema

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

Implementation plans are generated by parsing a feature spec to detail multi-step tasks, tests, and documentation, producing an executable markdown document at docs/plans/YYYY-MM-DD-<feature-name>.md.

What is the best way to plan multi-step refactoring and architectural changes?▼

Multi-step refactoring plans apply a TDD-oriented approach to break down architectural changes into bite-sized tasks with clear ownership, acceptance criteria, and required documentation for reliable execution.

How does TDD-oriented planning work for feature development?▼

TDD-oriented planning enforces DRY principles by structuring feature development into bite-sized tasks that define specific tests, acceptance criteria, and documentation steps before coding begins.

Do I need a specific file format for software engineering plan generation?▼

Plan generation requires following a strict format derived from the feature name in the frontmatter, saving the output directly to the docs/plans directory using the YYYY-MM-DD-<feature-name>.md naming convention.

Can I generate task-management documentation for scattered specifications?▼

Task-management documentation is generated by converting scattered specifications into comprehensive, executable plans that outline specific tasks, ownership details, and acceptance criteria for multi-step software work.

When should I not use an automated plan generation approach?▼

Automated plan generation should be avoided for single-step tasks or trivial changes that do not require detailed ownership assignment, acceptance criteria, or multi-step architectural documentation.