skills.rest
robertphyatt
robertphyattCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert design documents into step-by-step implementation plans with file paths.

7|1|Updated Mar 26, 2026
Search Tags:#planning#tdd#implementation#software-engineering#project-management#design-docs#task-breakdown
One-click install
npx skills add https://github.com/robertphyatt/ironclaude --skill writing-plans-robertphyatt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/robertphyatt/ironclaude/tree/main/worker/skills/writing-plans
Command: npx skills add https://github.com/robertphyatt/ironclaude --skill writing-plans-robertphyatt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating high-level design discussions into precise, executable plans is time-consuming and error-prone. This skill bridges the gap by generating bite-sized tasks with exact file paths, code snippets, and acceptance criteria, ensuring consistent handoffs from design to implementation.

Core Features & Use Cases

  • Plan generation: Convert a design document into a comprehensive implementation plan with 2-5 minute steps and explicit file locations.
  • TDD-focused: Enforce a red-green-red cycle by requiring tests to be written before implementations and validated as part of each task.
  • Phase gating: Include memory of prior context, phase-based progress, and design alignment to reduce scope drift across teams.
  • Quick Start guidance: Provide an actionable sentence to trigger plan creation from a given design doc path.

Quick Start

Provide a path to a design document ending with -design.md to 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 design document into an actionable implementation plan?▼

Yes, you can enforce TDD in your implementation plans. The generated tasks enforce a red-green-red cycle, requiring tests to be written before implementations and validated as part of each step's acceptance criteria.

What is the best way to break down complex software features for engineers?▼

You need a completed design document saved with a -design.md file extension. This serves as the input format, allowing the tool to parse your high-level design and automate the transformation into executable steps.

Does plan generation help prevent scope drift in project management?▼

Yes, plan generation prevents scope drift by including phase gating and memory of prior context. This enforces design alignment and tracks phase-based progress throughout the software engineering implementation lifecycle.

How do I start generating a plan from an existing design doc?▼

To start generating a plan, provide an actionable sentence triggering creation from your design doc path. Ensure the file ends with -design.md to satisfy the gating rules and output a complete implementation plan.

Related Skills

Explore More Software Engineering Skills→
epieczkoepieczko

epic.write

Generate structured Agile Epic Markdown documents from initiative details.

Community
Intermediate
cryptopaficryptopafi

writing-plans

Generate implementation plans with TDD tasks, file paths, and test commands.

Community
Advanced
labs21-devlabs21-dev
28

implement

Enforce RED-GREEN-REFACTOR cycles and update status.json with evidence.

Official
Advanced
ghufronbagaskaraghufronbagaskara

plan

Generate markdown implementation plans with test-driven development steps.

Community
Intermediate