skills.rest
otto-poblysh
otto-poblyshCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert feature specifications into multi-step implementation plans with file paths and test-first tasks.

Updated Apr 24, 2026
Search Tags:#documentation#implementation planning#task breakdown#test-driven development#engineering workflow#spec decomposition
One-click install
npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill writing-plans-otto-poblysh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/otto-poblysh/pedagemy-early-access/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill writing-plans-otto-poblysh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns ambiguous specs into clear, build-ready implementation plans that an engineer can follow with minimal ramp-up and without guessing.

Core Features & Use Cases

  • Multi-step implementation planning: Converts a feature spec into an end-to-end, task-by-task plan that covers files, tests, and commits.
  • Context-reset and decomposition: Assumes zero codebase context, maps file structure, and suggests splitting by independent subsystems when needed.
  • TDD-oriented, bite-sized steps: Enforces a 2–5 minute per step cadence, including failing tests first, minimal implementations second, and repeated verification.

Quick Start

Use the writing-plans skill when you have a spec for a multi-step engineering task and want an implementation plan saved under 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 turn a feature specification into an actionable implementation plan?▼

Implementation planning decomposes feature specs into end-to-end, task-by-task engineering plans. It maps file structures and outputs DRY plans with explicit file paths and checkbox task steps for multi-step execution.

Can I use test-driven development to break down a large feature spec?▼

Yes, you can use test-driven development to break down specs. The Skill enforces a 2–5 minute per step cadence, scheduling failing tests first, minimal implementations second, and repeated verification.

When do I need task decomposition for multi-step engineering tasks?▼

Task decomposition is needed for multi-step engineering tasks requiring file-level guidance. The Skill assumes zero codebase context, maps file structure, and suggests splitting work by independent subsystems when needed.

What is the best way to create build-ready plans with explicit file paths?▼

The best way to create build-ready plans is to process a spec through this Skill. It generates a DRY plan with explicit file paths and checkbox task steps, saved under the docs/superpowers/plans/ directory.

Does implementation planning work without existing codebase context?▼

Yes, implementation planning works without existing codebase context. The Skill assumes zero prior knowledge, maps the required file structure independently, and outputs file-level guidance for execution.

Related Skills

Explore More Software Engineering Skills→
zhanglongxiao111zhanglongxiao111
35

writing-plans

Translate implementation specifications into step-by-step TDD engineering plans.

Community
Intermediate
tiancaiamaotiancaiamao
5

planning

Manage task plans and progress with checkbox tracking for multi-step software work.

Community
Intermediate
Steve-Smith-CODESteve-Smith-CODE

speckit-taskstoissues

Convert local task lists into GitHub issues with duplicate detection.

Community
Advanced
qq824045252-ship-itqq824045252-ship-it

superpowers-writing-plans

Convert high-level specs into task-by-task implementation plans with file touchpoints.

Community
Advanced