writing-plans

Generate implementation plans with explicit file, test, and documentation steps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bjconlan/burndown --skill writing-plans-bjconlan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/bjconlan/burndown/tree/main/.gemini/skills/writing-plans
Command: npx skills add https://github.com/bjconlan/burndown --skill writing-plans-bjconlan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables engineers to convert a high-level spec into a complete, actionable implementation plan before writing code. It makes explicit which files to touch, what to implement, how to test, and what docs may be required, ensuring a clear, auditable path from concept to delivery.

Core Features & Use Cases

  • Document all steps and deliverables for each task, including files, tests, and docs.
  • Promote DRY, YAGNI, TDD principles and frequent commits to maintain quality and traceability.
  • Assume the engineer has zero context about the codebase and domain; produce a plan as bite-sized tasks.

Quick Start

Create a complete implementation plan and save it to docs/plans/YYYY-MM-DD-writing-plans.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan from a high-level spec before coding?

To generate an implementation plan from a high-level spec, convert your requirements into bite-sized, actionable tasks. The plan explicitly details which files to touch, what tests to write, and required documentation, saving automatically to docs/plans/YYYY-MM-DD-writing-plans.md.

What is the best way to break down multi-step software development tasks for engineers lacking codebase context?

Breaking down multi-step software development tasks requires assuming zero codebase context. The process produces explicit, bite-sized steps covering file modifications, TDD testing requirements, and documentation updates to ensure a clear, auditable path from concept to delivery.

How does task-breakdown planning enforce DRY, YAGNI, and TDD principles during software development?

Task-breakdown planning enforces DRY, YAGNI, and TDD principles by structuring the implementation plan around frequent commits and explicit testing steps. It documents all deliverables to maintain quality and traceability throughout the software development lifecycle.

Does implementation planning work without existing codebase or domain knowledge?

Implementation planning works without existing codebase or domain knowledge by assuming zero engineer context. It creates a complete, actionable path from concept to delivery by making every file modification, test, and documentation requirement explicit as bite-sized tasks.

Where are generated implementation plans saved in the project directory?

Generated implementation plans are saved in the project directory as markdown files. The planning workflow automatically outputs the comprehensive task breakdown to docs/plans/YYYY-MM-DD-writing-plans.md to ensure plans are auditable and accessible.