skills.rest
handsomelong922
handsomelong922COMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Translate specifications into structured implementation plans with tasks and file changes.

Updated Apr 3, 2026
Search Tags:#planning#tdd#documentation#specifications#software-engineering#task-decomposition#implementation-plan
One-click install
npx skills add https://github.com/handsomelong922/my-codex-skills --skill writing-plans-handsomelong922
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/handsomelong922/my-codex-skills/tree/main/skills/writing-plans
Command: npx skills add https://github.com/handsomelong922/my-codex-skills --skill writing-plans-handsomelong922

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague specifications into structured, executable implementation plans, reducing ambiguity for engineers and stakeholders.

Core Features & Use Cases

  • Plan generation from a given spec, detailing required files, code, tests, and documentation.
  • Task-level decomposition with clear boundaries, milestones, and acceptance criteria.
  • Versioned, portable plan storage to support reproducible work and collaborative reviews.

Quick Start

Create a complete implementation plan from the provided spec 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 turn software specifications into actionable implementation plans?▼

Implementation plans translate specifications into structured task decomposition with clear scope, required file changes, testing steps, and documentation needs. This enforces consistent structure, traceability, and reproducibility for complex software projects.

What is task decomposition in software engineering planning?▼

Task decomposition is breaking specifications into actionable tasks with clear boundaries, milestones, and acceptance criteria. It ensures executable implementation steps are defined to reduce ambiguity for engineers and stakeholders.

How do I structure implementation plans for complex software projects?▼

Structure implementation plans by detailing required files, code modifications, tests, and documentation from a given spec. Save these versioned plans to a standardized path like docs/superpowers/plans/ for reproducible work and collaborative reviews.

Does this implementation plan generator support TDD workflows?▼

Yes, implementation plan generation supports TDD workflows by detailing required testing steps and acceptance criteria alongside code modifications. It ensures test boundaries are defined during task decomposition from the provided specifications.

Can I save generated implementation plans to a specific file path?▼

Yes, generated plans are saved to a standardized, portable path like docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. This versioned storage supports reproducible work and collaborative reviews across engineering teams.

What is the best way to reduce ambiguity in software engineering specifications?▼

The best way to reduce ambiguity is converting vague specifications into structured, executable implementation plans. This defines clear scope breakdown, required file changes, and task-level milestones for stakeholders.

Related Skills

Explore More Software Engineering Skills→
SSiertsemaSSiertsema

scope-statement-writing

Generate a complete project scope statement with boundaries and change protocol.

Community
Intermediate
xz1220xz1220

tdd

Enforce test-first development with a Red-Green-Refactor loop and strict stop rules.

Community
Basic
Patasse97Patasse97

tdd-guide

Generate tests, analyze coverage, and guide RED-GREEN-REFACTOR workflows across languages.

Community
Advanced
patrickrmoorepatrickrmoore

sddp-tasks

Decompose feature implementation plans into phase-organized developer tasks.

Community
Advanced