skills.rest
tmtgroupbot
tmtgroupbotCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generates detailed implementation plans with bite-sized TDD tasks from specs or requirements.

Updated Mar 30, 2026
Search Tags:#planning#tdd#markdown#git workflow#task breakdown#implementation plan#spec
One-click install
npx skills add https://github.com/tmtgroupbot/lptracker-deploy --skill writing-plans-tmtgroupbot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tmtgroupbot/lptracker-deploy/tree/main/skills/writing-plans
Command: npx skills add https://github.com/tmtgroupbot/lptracker-deploy --skill writing-plans-tmtgroupbot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often start coding multi-step features without a clear roadmap, leading to missed requirements, poor test coverage, and inconsistent execution. This Skill turns a spec or requirements document into a comprehensive implementation plan that any developer can follow, even with zero codebase context. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute steps following TDD: write failing test, verify failure, implement, verify pass, commit. - Exact File Paths and Code: Every task specifies exact files to create or modify, complete code snippets, and exact commands with expected output. - Execution Handoff: After saving the plan to docs/plans/, offers subagent-driven execution in the current session or parallel execution in a new session. - Use Case: You have a feature spec for adding user authentication. Run this Skill to produce a dated plan document with ordered tasks, test code, implementation code, and commit steps ready for execution. ## Quick Start Use the writing-plans skill to create an implementation plan for the feature spec I just described.

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 before coding a feature?▼

Start from a spec or requirements document and break the work into bite-sized tasks of 2-5 minutes each. Each task lists exact files to create or modify, complete test and implementation code, commands with expected output, and a commit step.

What is the best task granularity for TDD implementation plans?▼

Each step should be a single action taking 2-5 minutes: write the failing test, run it to confirm failure, write minimal implementation, run tests to confirm pass, then commit. This keeps progress verifiable and commits frequent.

Where should implementation plan documents be saved?▼

Save plans as Markdown files under docs/plans/ using the naming format YYYY-MM-DD-feature-name.md. Each plan starts with a header stating the goal, architecture, tech stack, and a pointer to the executing-plans skill.

Can I execute a plan with subagents after writing it?▼

Yes. After saving the plan, you can choose subagent-driven execution in the current session, which dispatches a fresh subagent per task with code review between tasks, or open a parallel session using the executing-plans skill.

When should I not write a detailed implementation plan?▼

Skip detailed planning for trivial single-step changes or exploratory spikes where requirements are unclear. The plan format assumes a defined spec and multi-step work; without requirements, brainstorm first to produce a spec.

Related Skills

Explore More Software Engineering Skills→
sirius-cc-wusirius-cc-wu
3

create-feature-worktree

Move staged changes into a new branch and create a dedicated Git worktree.

Community
Intermediate
cristoslccristoslc

writing-plans

Generates detailed implementation plans with bite-sized TDD tasks from specs or requirements.

Community
Intermediate
ChoreShoreChoreShore

coding-styles

Apply SOLID, DRY, KISS, and YAGNI principles during development decisions.

Official
Intermediate
busboom-software-studiobusboom-software-studio
1

oop

Apply small targeted changes directly on master with test suite runs.

Official
Intermediate