writing-plans

Generate implementation plans with file paths, code examples, and verification steps.

1|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/timbuchinger/loadout --skill writing-plans-timbuchinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/timbuchinger/loadout/tree/main/skills/writing-plans
Command: npx skills add https://github.com/timbuchinger/loadout --skill writing-plans-timbuchinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of highly detailed and actionable implementation plans, ensuring that any developer, regardless of codebase familiarity, can execute tasks with precision and confidence. It eliminates ambiguity and reduces planning overhead.

Core Features & Use Cases

  • Bite-Sized Task Granularity: Breaks down work into atomic, 2-5 minute steps, each independently verifiable.
  • Comprehensive Detail: Includes exact file paths, complete code examples, precise commands, and clear verification steps for every task.
  • TDD & Commit Guidance: Integrates Test-Driven Development principles and conventional commit message guidelines directly into the plan.
  • Use Case: After a design is finalized for a new user authentication module, this Skill helps you generate a step-by-step plan, complete with code snippets and test instructions, ready for immediate execution by a team member.

Quick Start

Write an implementation plan for adding email validation to the user signup process, including TDD steps and exact file paths.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a software feature into executable implementation tasks?

Implementation plans decompose features into atomic, 2-5 minute tasks with exact file paths, complete code examples, and verification steps. Each task is independently executable and testable, enabling precise delegation and reducing ambiguity for any developer regardless of codebase familiarity.

What should a detailed implementation plan include?

Comprehensive plans include exact file paths, complete runnable code blocks, precise commands to execute, explicit verification criteria, TDD test guidance, and conventional commit message templates. This ensures developers can act immediately without guessing or seeking clarification.

How do I integrate TDD principles into my implementation planning?

Test-Driven Development guidance is embedded directly into task sequences, specifying test cases before implementation and verification steps after each task. This ensures code meets requirements and reduces rework.

Can I use implementation plans for onboarding new team members?

Yes. Bite-sized tasks with complete detail, clear file paths, and runnable code examples allow new developers to execute work confidently without deep codebase knowledge, accelerating onboarding and reducing planning overhead.

When should I create an implementation plan instead of starting to code?

Generate plans after design is finalized and you have clear requirements. Plans work best for feature work, refactoring, or delegation scenarios where bite-sized, verifiable tasks reduce execution risk and improve coordination.

What format and location should implementation plans follow?

Plans are saved as Markdown files at docs/plans/YYYY-MM-DD-<feature-name>.md, organizing touched files, commands, test procedures, and verification criteria in a single, version-controlled reference document.