writing-plans

Spawn a planner subagent to generate implementation plans from design specifications.

9|3|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/mattdurham/bob --skill writing-plans-mattdurham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/mattdurham/bob/tree/main/skills/writing-plans
Command: npx skills add https://github.com/mattdurham/bob --skill writing-plans-mattdurham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to generate comprehensive, implementation-level plans from a formal spec or requirements before touching code. It spawns a dedicated planner subagent to produce a step-by-step plan that documents files to touch, code changes, tests, and documentation, ensuring alignment with DRY, YAGNI, and TDD principles.

Core Features & Use Cases

  • Spawns a background planner subagent to draft a complete implementation plan from design input.
  • Reads design from bots/design.md and writes the resulting plan to bots/plan.md.
  • Enforces a task-by-task execution flow with explicit files, test guidance, and commit steps, enabling clean, incremental development.

Quick Start

Run this skill to spawn a planner subagent, read bots/design.md, and output the plan to bots/plan.md.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an implementation plan from a design specification?

You generate an implementation plan by spawning a background planner subagent that reads your design specification and writes a detailed, step-by-step execution blueprint covering files, code changes, tests, and documentation.

What is the best way to enforce TDD and DRY principles before writing code?

To enforce TDD and DRY principles before coding, you spawn a planner subagent to produce a task-by-task implementation plan that explicitly defines test guidance and incremental commit steps for clean development.

How do I create a step-by-step engineering plan for incremental commits?

Creating an engineering plan for incremental commits involves generating a task-by-task blueprint that documents specific files to touch and code changes, waiting for completion notification before proceeding to the next task.

Does this implementation planner require a specific file format for design input?

Yes, this implementation planner requires design input to be read from the bots/design.md file, and it writes the resulting step-by-step implementation plan directly to bots/plan.md.

Can I use a subagent to document files to touch and code changes automatically?

Yes, you can spawn a background planner subagent to automatically draft a complete implementation plan detailing exact files to touch, code changes, tests, and documentation from your design specification.