writing-plans

Convert approved specs into slice-ordered implementation plans with exact file paths, test commands, and acceptance criteria.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/pgoell/pgoell-claude-tools --skill writing-plans-pgoell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/pgoell/pgoell-claude-tools/tree/main/plugins/workbench/skills/writing-plans
Command: npx skills add https://github.com/pgoell/pgoell-claude-tools --skill writing-plans-pgoell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a design spec or approved requirements into an executable implementation plan is error-prone: plans often contain vague steps, missing test commands, or placeholders that force the implementing agent to guess. This Skill produces concrete, slice-ordered plans that a fresh agent can execute step by step without conversation history. ## Core Features & Use Cases - Slice-based decomposition: Orders work as vertical, end-to-end increments starting with a tracer-bullet slice, each with exact file paths, type signatures, test commands, and acceptance criteria. - Placeholder prevention and review: Forbids TBD-style steps and dispatches an adversarial reviewer subagent (using the included prompt template) to verify spec coverage, name consistency, and testability before handoff. - Flexible output formats: Emits Markdown by default or styled HTML via the bundled template, with optional design-system overrides and configurable plan paths. - Use Case: After approving a spec for a new API feature, invoke this Skill to produce a plan document with checkbox TDD steps per slice, then hand it to a subagent-driven execution workflow. ## Quick Start Ask the agent to write an implementation plan for the approved spec at .workbench/specs/my-feature.md using the writing-plans skill.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write an implementation plan an AI agent can execute?

Structure the plan as vertical slices ordered from a tracer-bullet first slice, each with exact file paths, type signatures, test commands, and acceptance criteria. Use checkbox steps for write-test, run-test, implement, verify, and commit actions so a fresh agent needs no conversation history.

What is a tracer bullet slice in implementation planning?

A tracer bullet slice is the first slice of a plan: the thinnest end-to-end path through the system that is demoable. Each later slice adds one coherent capability while keeping the software demoable after every increment.

Should implementation plans include full code or just signatures?

Plans should work at program-design altitude: exact function signatures, call-stack sketches, and acceptance criteria, not full test or implementation code. The single exception is a tricky-kernel flag for algorithms where the code shape itself is the design decision.

Can the plan be exported as HTML instead of Markdown?

Yes. Markdown is the default, but a per-prompt override or a .workbench/config.md output-format entry switches output to HTML using the bundled plan template. An optional design system can inline custom colors, typography, and components into the artifact.

When should a spec be split into multiple implementation plans?

Split when the spec covers multiple independent subsystems. Each plan should produce working, testable software on its own, so one plan per independently testable change keeps slices coherent and reviewable.