writing-plans

Generates detailed implementation plans with bite-sized TDD tasks from specs.

Updated May 16, 2026
One-click install
npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill writing-plans-michalo1334
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/michalo1334/ScenarioImpactDSL/tree/main/.opencode/skills/writing-plans
Command: npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill writing-plans-michalo1334

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, files and tests are unspecified, and engineers without codebase context get stuck. This Skill produces a complete, step-by-step plan that an engineer with zero project context can execute directly. ## Core Features & Use Cases - Bite-Sized Task Decomposition: Breaks work into 2-5 minute steps following a strict TDD cycle (failing test, verify failure, minimal implementation, verify pass, commit). - No-Placeholder Enforcement: Requires exact file paths, complete code blocks, exact commands with expected output, and forbids TODOs or vague instructions. - Self-Review and Handoff: Includes a spec-coverage and type-consistency self-review checklist, plus an execution handoff offering subagent-driven or inline execution. - Use Case: Given a feature spec for a new API endpoint, produce a plan saved to docs/superpowers/plans/ with checkbox-tracked tasks covering tests, implementation, and commits. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan from your spec 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 produces a plan with a goal, architecture summary, tech stack, and checkbox-tracked tasks saved to docs/superpowers/plans/ by default.

How detailed should tasks be in an implementation plan?▼

Each step should be one action taking 2-5 minutes, such as writing a failing test, running it, implementing minimal code, and committing. Every step must include exact file paths, complete code, and commands with expected output.

What makes an implementation plan fail during execution?▼

Plans fail when they contain placeholders like TODO or 'add error handling', reference undefined types or functions, or describe what to do without showing the code. The skill's self-review checklist scans for these issues before handoff.

When should a spec be split into multiple implementation plans?▼

Split the spec when it covers multiple independent subsystems. Each plan should produce working, testable software on its own, so one plan per subsystem keeps tasks self-contained and independently executable.

How is a finished implementation plan executed?▼

After saving the plan, choose subagent-driven execution, which dispatches a fresh subagent per task with review between tasks, or inline execution, which runs tasks in batches with checkpoints in the current session.