writing-plans

Create detailed implementation plans from specs with file paths and validation steps.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/ilderaj/superpowering-with-files --skill writing-plans-ilderaj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ilderaj/superpowering-with-files/tree/main/harness/upstream/superpowers/skills/writing-plans
Command: npx skills add https://github.com/ilderaj/superpowering-with-files --skill writing-plans-ilderaj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and documenting complex tasks can be error-prone and time-consuming. The Writing Plans skill creates a clear, executable plan from a spec or requirements, outlining which files to touch, how to modify them, what tests to add, and how to commit changes.

Core Features & Use Cases

  • Comprehensive task decomposition: Breaks a spec into concrete, testable tasks with explicit file changes and milestones.
  • Structured plan templates: Provides a consistent plan structure that can be followed by engineers or subagents.
  • Plan governance and traceability: Documents dependencies, risks, and expected outcomes to improve collaboration and review.

Quick Start

Provide a feature name and spec to generate a full step-by-step implementation plan.

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 from a spec for multi-step tasks?

Create an implementation plan by providing a feature name and spec to generate a step-by-step plan. This plan outlines necessary files, code changes, tests, and commits for multi-step tasks spanning multiple subsystems.

What's the best way to break down complex requirements into testable tasks?

Break down complex requirements through comprehensive task decomposition. This process splits a spec into concrete, testable tasks with explicit file changes, clear task boundaries, and defined milestones for reproducible execution.

Does this planning approach work for tasks that span several subsystems and teams?

Planning works for tasks spanning several subsystems and teams by documenting dependencies, risks, and expected outcomes. This governance and traceability improves collaboration and review across distributed engineering efforts.

Can I use these plan templates to guide engineers or subagents through execution?

You can use structured plan templates to guide engineers or subagents through execution. The templates provide a consistent plan structure that ensures explicit file paths and validation steps are followed for reproducible results.

What do I need to provide to generate a full step-by-step implementation plan?

You need to provide a feature name and a spec or requirements document. The skill then processes these inputs to create a detailed plan documenting which files to touch, how to modify them, and what tests to add.