writing-plans

Generate step-by-step implementation plans with file paths, code snippets, and commands.

1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/bgrober/indie-stack --skill writing-plans-bgrober
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/bgrober/indie-stack/tree/main/skills/writing-plans
Command: npx skills add https://github.com/bgrober/indie-stack --skill writing-plans-bgrober

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill generates comprehensive, step-by-step implementation plans for complex tasks, ensuring developers have all the necessary context and instructions to complete the work efficiently and correctly.

Core Features & Use Cases

  • Detailed Task Breakdown: Divides large features into small, actionable tasks (e.g., write test, implement code, commit).
  • Contextual Information: Includes file paths, code snippets, commands, and expected outputs for each step.
  • Use Case: Before starting development on a new feature, use this Skill to generate a detailed plan that guides the developer through writing tests, implementing the minimal code, and committing changes, ensuring adherence to TDD and DRY principles.

Quick Start

Use the writing-plans skill to generate an implementation plan for the user authentication feature.

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 multi-step software development task into actionable steps?

Implementation plans break down multi-step software development tasks by generating bite-sized, actionable steps that include exact file paths, code snippets, commands, and expected outputs. This ensures developers have all necessary context to complete work systematically.

How does TDD workflow integrate with implementation plan generation?

TDD workflow integrates with implementation plan generation by structuring granular steps to guide developers through writing tests first, implementing minimal code, and committing changes. This enforces adherence to TDD, DRY, and YAGNI principles during systematic development.

What is the best way to document expected outputs for granular development tasks?

The best way to document expected outputs for granular development tasks is to include them directly in detailed implementation plans alongside exact file paths, code snippets, and commands. This provides comprehensive context and verifies each step's completion.

Can I use detailed task breakdowns for complex features if the implementer has minimal prior context?

Yes, detailed task breakdowns are designed for implementers with minimal prior context. The generated plans provide comprehensive, step-by-step instructions with exact file paths and code snippets to complete complex features efficiently and correctly.

When do I need a detailed implementation plan for a new software feature?

You need a detailed implementation plan for a new software feature before starting development. It generates comprehensive, step-by-step instructions that divide large features into small, actionable tasks, ensuring efficient and correct completion with minimal prior context.