skills.rest
earchibald
earchibaldCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with task lists, file touchpoints, tests, and commit guidance.

70|6|Updated Feb 8, 2026
Search Tags:#workflow#planning#tdd#software-engineering#task-breakdown#implementation-plan#planning-docs
One-click install
npx skills add https://github.com/earchibald/vsc-superpowers --skill writing-plans-earchibald
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/earchibald/vsc-superpowers/tree/main/.agents/skills/write-plan
Command: npx skills add https://github.com/earchibald/vsc-superpowers --skill writing-plans-earchibald

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform scattered specifications and requirements into a clear, executable plan that guides implementation, testing, and documentation.

Core Features & Use Cases

  • Structured planning: converts specs into a task-by-task plan with file touchpoints, tests, and docs.
  • Save and reference: stores plans in docs/plans/YYYY-MM-DD-<feature-name>.md for versioned reference.
  • TDD-aligned workflow: emphasizes test-first steps, small commits, and incremental delivery.

Quick Start

Provide a feature spec or requirements and I will generate a complete 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 convert a feature specification into an implementation plan?▼

To convert a feature specification into an implementation plan, provide the spec to generate a comprehensive document with task lists, file touchpoints, tests, and commit guidance for structured execution.

What is the best way to structure a TDD-aligned workflow for software engineering tasks?▼

A TDD-aligned workflow structures software engineering tasks by emphasizing test-first steps, small commits, and incremental delivery within a generated plan document for systematic implementation.

How do I break down a software development task into structured steps?▼

Task breakdown for software development transforms scattered requirements into a step-by-step plan that guides implementation, testing, and documentation through clearly defined executable tasks.

Can I generate planning docs that include file touchpoints and test guidance for bug fixes?▼

Yes, generating planning docs applies to bug fixes and feature development by producing a comprehensive plan document that specifies file touchpoints, required tests, and documentation updates.

Where are generated implementation plans stored for versioned reference?▼

Generated implementation plans are stored as versioned reference files in docs/plans/YYYY-MM-DD-<feature-name>.md to maintain structured planning history.

Does this planning approach work for research tasks that require structured steps?▼

Yes, this planning approach works for research tasks by generating comprehensive implementation plans that translate requirements into structured steps with task lists and documentation guidance.

Related Skills

Explore More Software Engineering Skills→
micaelmaltamicaelmalta
1

architect

Draft technical specifications covering architecture, APIs, data models, and migrations.

Community
Advanced
mintuzmintuz
3

refactoring

Plans behavior-preserving code restructuring with reversible baselines and characterization tests.

Community
Intermediate
benjgradbenjgrad

writing-plans

Generate detailed implementation plans with tasks, files, tests, and commits.

Community
Advanced
SunS1eep1ngSunS1eep1ng

planning-with-files

Create persistent multi-step task plans using markdown files.

Community
Advanced