writing-plans

Generate step-by-step implementation plans with exact file paths and test commands.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/treejh/ai-agent-skills --skill writing-plans-treejh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/treejh/ai-agent-skills/tree/main/skills/writing-plans
Command: npx skills add https://github.com/treejh/ai-agent-skills --skill writing-plans-treejh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns vague specs or requirements into a concrete, testable implementation plan so engineers can start coding with clear, minimal-risk steps and frequent commits.

Core Features & Use Cases

  • Bite-sized task decomposition: Breaks work into 2–5 minute actionable steps (write failing test, run, implement, run, commit).
  • Exact file and test guidance: Specifies which files to create or modify, exact test commands, and expected outcomes.
  • Plan persistence and handoff: Saves plans to docs/plans/YYYY-MM-DD-<feature-name>.md for subagent execution or human follow-up.
  • Ideal for: multi-file feature work, mid-sized tasks, TDD workflows, and coordinated subagent-driven execution.

Quick Start

Run the writing-plans skill with a clear feature specification to generate and save a dated, bite-sized implementation plan to docs/plans.

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 feature specifications into actionable implementation plans?

Implementation plans decompose feature specifications into 2–5 minute actionable steps, specifying exact file paths, test commands, and expected outcomes. This breakdown enables engineers to start coding with clear, minimal-risk steps and frequent commits.

How do I generate a TDD workflow plan with exact file changes and test commands?

Generating a TDD workflow plan involves providing a feature specification to produce step-by-step actions with exact file paths, test commands, and commit steps. The output sequences the process of writing failing tests, running them, implementing code, and committing.

Does this implementation plan generator work for multi-file feature work and subagent execution?

Yes, the implementation plan generator suits mid-sized or multi-file development tasks and coordinated subagent-driven execution. It saves plans to a dated docs/plans filename for seamless handoff to subagents or human developers.

What is the best way to prepare for a pre-coding design session for mid-sized tasks?

Preparing for a pre-coding design session involves turning vague requirements into a concrete, testable implementation plan. This process clarifies task sequencing and exact file changes before coding begins, ensuring minimal-risk development steps.

Where are the generated implementation plans saved for developer workflow handoff?

Generated implementation plans are saved to docs/plans/YYYY-MM-DD-<feature-name>.md. This dated markdown file format ensures easy tracking, persistence, and handoff for subagent-driven execution or human follow-up.