writing-plans

Drafts implementation plans with tasks, tests, and docs into dated files.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/jbro/pi-agent --skill writing-plans-jbro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/jbro/pi-agent/tree/main/skills/superpowers/writing-plans
Command: npx skills add https://github.com/jbro/pi-agent --skill writing-plans-jbro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating thorough, reusable implementation plans for multi-step tasks when engineers lack domain context.

Core Features & Use Cases

  • Write end-to-end implementation plans that specify required files, tests, docs, and commits.
  • Break work into bite-sized tasks suitable for a rapid, iterative workflow (DRY, YAGNI, TDD).
  • Save plans to the docs/plans/YYYY-MM-DD-<feature-name>.md file and provide clear handoff instructions.

Quick Start

Create a complete plan for the requested feature.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write implementation plans for complex tasks with clear step-by-step instructions?

Implementation plans for complex tasks are drafted by breaking work into bite-sized tasks, tests, and documentation. The output enforces DRY, YAGNI, and TDD principles, specifying required files and commits for a complete iterative workflow.

What is the best way to document implementation plans for engineers lacking domain context?

Documenting implementation plans for engineers lacking domain context involves generating thorough, reusable files saved to docs/plans/YYYY-MM-DD-<feature-name>.md. These plans provide clear handoff instructions, specifying required tests, docs, and commits for immediate execution.

Can I use this planning approach for a TDD workflow with git worktrees?

Yes, this planning approach applies directly to a TDD workflow with git worktrees. It breaks work into step-by-step tasks suitable for rapid, iterative development, enforcing DRY and YAGNI throughout the specified commits and tests.

Does generating an implementation plan require any specific project dependencies?

Generating an implementation plan requires no specific project dependencies. It operates independently to draft comprehensive task lists, required files, and documentation, saving the output directly to your project's docs directory.

Why should I use automated implementation planning instead of manually writing task lists?

Automated implementation planning saves thorough, reusable plans to a standardized docs path, ensuring engineers with little context receive clear handoff instructions. It consistently enforces DRY, YAGNI, and TDD rules throughout the workflow, avoiding manual oversight gaps.

What are the limitations of using generated implementation plans for rapid iterative workflows?

Generated implementation plans are limited to structuring documentation, tasks, and tests for rapid iterative workflows. They provide the step-by-step roadmap and handoff instructions but do not automatically execute the code changes or run the tests themselves.