skills.rest
cristoslc
cristoslcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

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

Updated Dec 20, 2025
Search Tags:#planning#tdd#markdown#task breakdown#implementation plan#git worktree#spec
One-click install
npx skills add https://github.com/cristoslc/LLM-personal-agent-patterns --skill writing-plans-cristoslc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/cristoslc/LLM-personal-agent-patterns/tree/main/L3-agents-core/.agents/skills/writing-plans
Command: npx skills add https://github.com/cristoslc/LLM-personal-agent-patterns --skill writing-plans-cristoslc

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 commits. This Skill turns a spec or requirements document into a comprehensive, step-by-step implementation plan that any developer can follow without prior 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 minimal code, verify pass, commit. - Standardized Plan Format: Produces plans with exact file paths, complete code snippets, exact commands with expected output, and a required header 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: Given a feature spec for a new API endpoint, generate a plan where each task lists exact files to create or modify, failing tests to write first, and commit commands, ready for task-by-task execution. ## Quick Start Ask the agent to use the writing-plans skill to create an implementation plan from 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?▼

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, a failing test first, minimal implementation, verification commands, and a commit step.

How to structure a TDD task breakdown for a multi-step feature?▼

Structure each task as five steps: write the failing test, run it to confirm failure, write minimal code to pass, run the test to confirm it passes, then commit. Include exact commands with expected output for every run step.

Where should implementation plans be saved in a repository?▼

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

When should I not use a detailed implementation plan?▼

Skip full planning for trivial single-step changes or quick experiments where task breakdown overhead exceeds the work itself. The skill targets multi-step tasks derived from a spec, typically run in a dedicated worktree.

How are implementation plans executed after being written?▼

After saving the plan, choose subagent-driven execution in the current session with a fresh subagent per task and code review, or open a parallel session that executes the plan task-by-task with checkpoints.

Related Skills

Explore More Software Engineering Skills→
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

brainstorming

Shape vague product ideas into clear design directions before implementation.

Community
Advanced
samixismesamixisme

parallel-task

Parse development plans and execute tasks across subagents in dependency-driven waves.

Community
Advanced
tony30552001tony30552001

plan-eng-review

Review architecture, data flow, diagrams, edge cases, test coverage, and performance.

Community
Advanced
busboom-software-studiobusboom-software-studio
1

oop

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

Official
Intermediate