writing-plans

Creates step-by-step implementation plans with exact file paths, code, and test commands.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill writing-plans-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/writing-plans
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill writing-plans-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into working code often fails because the plan is too vague for an engineer (or AI agent) with zero codebase context. This Skill converts requirements into a granular, actionable implementation plan where every task includes exact file paths, complete code, and verification commands. ## Core Features & Use Cases - Granular Task Breakdown: Splits work into 2-5 minute steps following the RED-GREEN-REFACTOR TDD cycle, from failing test to commit. - Structured Templates: Provides a plan header template (goal, architecture, tech stack) and a per-task template covering files, test code, run commands with expected output, and commit steps. - Pipeline Integration: Fits between requirements gathering and execution, handing off to the executing-plans skill with a verification-before-completion quality gate. - Use Case: After brainstorming a new API endpoint feature, use this Skill to produce a plan document listing every file to create or modify, the failing test to write first, the minimal implementation, and the exact pytest commands to verify each step. ## Quick Start Ask the AI to write an implementation plan for your feature spec using the writing-plans skill before touching 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 from a feature spec?

Start with a plan header stating the goal, architecture, and tech stack, then break work into tasks of 2-5 minute steps. Each task lists exact files to create or modify, a failing test, the minimal implementation, run commands with expected output, and a commit step.

How to structure tasks in a TDD implementation plan?

Structure each task around the RED-GREEN-REFACTOR cycle: write the failing test, run it to verify failure, write minimal code to pass, run tests to verify pass, then commit. Every step includes exact commands and expected output.

When should I write an implementation plan before coding?

Write a plan after brainstorming or requirements gathering and before touching code, especially for multi-step tasks. It assumes the engineer has zero codebase context, so document everything needed including files, code, and verification steps.

What are the limitations of a pre-written implementation plan?

A plan assumes the spec is stable and the described approach fits the codebase; discoveries during execution may require replanning. It also depends on downstream execution and verification steps, such as executing-plans and verification-before-completion, to deliver results.

Can an AI agent execute a plan written with this approach?

Yes, the plan is designed for zero-context executors, including AI agents, because it contains exact file paths, complete code rather than vague instructions, and exact commands with expected output. The executing-plans skill consumes the plan task by task.