writing-plans

Create implementation plans mapping tasks to files, tests, and documentation.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/mnsgrosa/skills --skill writing-plans-mnsgrosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/mnsgrosa/skills/tree/main/skills/writing-plans
Command: npx skills add https://github.com/mnsgrosa/skills --skill writing-plans-mnsgrosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams produce comprehensive, implementation-ready plans for multi-step tasks before any code is touched, ensuring all steps, files, tests, and documentation are defined upfront.

Core Features & Use Cases

  • Self-contained planning that maps each task to the files, code changes, tests, and docs needed for a feature.
  • Clear task decomposition that breaks work into bite-sized, auditable steps suitable for versioned commits.
  • Plan portability and reuse, with standardized guidance on where plans are saved and how they are structured.

Quick Start

Create a complete implementation plan for the requested feature using a dedicated worktree and save it to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan for multi-step software tasks before coding?

To create an implementation plan, provide a feature spec to generate a self-contained plan mapping tasks to specific files, tests, and documentation. This planning process ensures all work steps are defined upfront before any code is touched.

What is the best way to break down software requirements into auditable worksteps?

The best way to break down software requirements is using structured task decomposition that maps each item to necessary files, code changes, and tests. This produces bite-sized, auditable steps suitable for versioned commits during implementation.

How do I map feature requirements to specific files and tests during task planning?

You map feature requirements to files and tests by applying planning logic that enforces file-level granularity. Each task in the plan header explicitly identifies the required code changes, test coverage, and documentation needed.

Where should I save generated implementation plans for team portability and reuse?

You should save generated implementation plans to a deterministic location like docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. Standardized save locations ensure plan portability and reuse across the team workflow.

Can I use this task planning approach for complex multi-step workflows without external dependencies?

Yes, you can plan multi-step workflows without external dependencies because the skill operates independently. It directly processes your spec to produce actionable documentation structured for versioned commits.