writing-plans

Generate structured Markdown implementation plans with file paths, tests, and commit messages.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/jmmL/dr3-old --skill writing-plans-jmml
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/jmmL/dr3-old/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/jmmL/dr3-old --skill writing-plans-jmml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams produce complete, implementation plans for features before any code is written, reducing ambiguity and guiding development, testing, and documentation.

Core Features & Use Cases

  • Structured plan generation: outlines scope, milestones, required files, tests, and reviews for a given feature.
  • Context-aware planning: assumes zero context in the codebase and provides a step-by-step plan suitable for shared understanding.
  • Documentation-ready outputs: saves plan documents to a conventional location and formats them for version control.

Quick Start

Provide the feature name and any constraints to generate a new implementation plan. Review the resulting document and adjust details as needed. The plan will be saved to docs/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create a structured implementation plan for a software feature before coding?

Generate a structured implementation plan by providing the feature name and constraints. The Skill outputs a Markdown document outlining scope, milestones, required files, and tests, saved to docs/plans/YYYY-MM-DD-<feature-name>.md.

What is zero-context blueprinting in software engineering planning?

Zero-context blueprinting generates a step-by-step implementation plan assuming no prior codebase knowledge. It provides exact file paths, commit messages, and testing steps, ensuring shared understanding across engineers before development begins.

How do I break down a software feature into tasks and tests for version control?

Break down a feature by generating a plan that specifies files, test cases, and commit messages. The output is a version-control-ready Markdown file detailing exact file paths and testing steps required for implementation.

Can I generate a documentation-ready implementation plan for a GitHub repository?

Yes, the Skill generates a documentation-ready implementation plan formatted for GitHub. The plan is saved as a Markdown document to a conventional repository location, containing exact file paths, commit messages, and testing steps.

Does this planning approach work for projects requiring detailed file path and commit specifications?

Yes, this approach produces a comprehensive Markdown plan detailing exact file paths, tasks, and commit messages. It is designed for projects needing zero-context blueprinting across the entire codebase before implementation.