skills.rest
LeroyAdonis
LeroyAdonisCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often start coding from a spec without a clear roadmap, leading to missed requirements, inconsistent structure, and untested code. This Skill turns a spec or requirements document into a comprehensive, step-by-step implementation plan that any developer can follow with zero prior context. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute steps following a strict TDD cycle: write failing test, verify failure, implement, verify pass, commit. - Standardized Plan Format: Produces a plan document with goal, architecture, tech stack, exact file paths, complete code snippets, and exact commands with expected output, saved to docs/plans/YYYY-MM-DD-<feature-name>.md. - Execution Handoff: Offers a choice between subagent-driven execution in the current session or a parallel session using an executing-plans skill. - Use Case: After brainstorming a new feature, invoke this Skill to produce a dated plan file that a fresh engineer or subagent can implement task-by-task with frequent commits. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan for your feature spec before writing any code.

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?▼

Invoke the writing-plans skill with your spec or requirements. It produces a Markdown plan with a goal, architecture summary, tech stack, and bite-sized tasks containing exact file paths, complete code, and test commands, saved to docs/plans/.

What is a good task granularity for implementation plans?▼

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

How does TDD fit into an implementation plan?▼

Every task follows a test-driven cycle: write a failing test first, verify it fails with the expected error, write the minimal implementation, verify it passes, then commit. The plan includes exact pytest commands and expected output for each step.

Where should implementation plan documents be saved?▼

Plans are saved to docs/plans/ with the filename 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 for implementation.

When should I not use a detailed implementation plan?▼

Skip the plan for trivial single-file changes or quick experiments where task breakdown overhead exceeds the work itself. The skill targets multi-step features where the implementer has zero codebase context.

Related Skills

Explore More Software Engineering Skills→
emmepraemmepra
1

issue-shaping

Shape rough requests into problem statements with constraints and acceptance criteria.

Community
Advanced
rapyuta-roboticsrapyuta-robotics

subagent-driven-development

Dispatch fresh subagents to execute independent tasks from an implementation plan.

Official
Basic
namanchopranamanchopra
5

plan-founder-review

Review technical plans for completeness, risk coverage, and codebase alignment.

Community
Advanced
tDaliletDalile

gsd:add-todo

Add todo items with titles and metadata to a tracking list.

Community
Basic