writing-plans

Generates bite-sized TDD implementation plans with exact files, test code, and commands from approved specs.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill writing-plans-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/writing-plans
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill writing-plans-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved spec into executable work often produces vague plans with placeholders, missing file paths, and untestable steps. This Skill converts a spec into a detailed, vertical-slice implementation plan that an executor (human or AI) can follow with zero prior context. ## Core Features & Use Cases - Bite-sized TDD tasks: Breaks features into 2-5 minute steps following the write-failing-test, implement, verify, commit cycle. - No-placeholder enforcement: Requires real code, exact file paths, and runnable commands with expected output in every step. - Vertical slice ordering: Orders tasks by foundation, risk, dependencies, and quick wins instead of horizontal layers, with checkpoints between phases. - Use Case: After writing a spec for an SOS emergency feature in a Flutter app, generate a plan where Task 1 delivers a working end-to-end slice (UI + repository + backend POST + database insert) with actual Dart test code and flutter test commands. ## Quick Start Ask the AI to write an implementation plan for the approved spec in docs/specs, saved to docs/plans with a companion tasks todo file.

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 from a feature spec?▼

Start with a plan header stating goal, architecture, tech stack, and spec reference, then break the feature into tasks of 2-5 minute steps. Each step needs exact file paths, complete code, runnable commands with expected output, and a commit step.

What is vertical slice task ordering in software planning?▼

Vertical slicing orders tasks so each one delivers a working end-to-end piece of functionality across UI, logic, and database, rather than completing all of one layer first. This produces testable software after every task and surfaces risks early.

When should I skip writing an implementation plan?▼

Skip the plan when the feature is smaller than one task and can be coded directly with TDD. Plans are required for features of three or more tasks, and multi-subsystem specs should be split into separate sub-project plans.

Why do implementation plans fail with placeholders like TODO?▼

Placeholders such as TBD, add error handling, or similar to Task N leave the executor without actionable content, since tasks may be read out of order. Every step must contain the actual code, exact commands, and expected output.

How do I verify an implementation plan before executing it?▼

Reread the plan checking three things: every spec requirement maps to a task, no placeholder patterns remain, and type and function names are consistent across all tasks. Fix issues inline and add tasks for any uncovered spec requirements.