writing-plans

Generate step-by-step implementation plans with file changes, tests, and documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to convert vague multi-step requirements into a concrete, executable plan. It generates a complete blueprint that can guide engineers, testers, and documentation efforts before any code is written.

Core Features & Use Cases

  • Plan generation: Produce a step-by-step implementation plan that identifies files to touch, tests to write, and documentation to create.
  • Work breakdown & governance: Organize tasks into bite-sized steps suitable for version control commits and incremental delivery.
  • Consistent plan artifacts: Ensure plans follow a repeatable template and can be saved to a predictable location for future reference.

Quick Start

Create an implementation plan for a new feature, including tasks, files to touch, tests, docs, and commit steps; save the plan 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 turn vague software requirements into an actionable implementation plan?

To turn vague requirements into an implementation plan, use a structured task breakdown approach that identifies specific files to modify, tests to write, and documentation to generate before coding begins.

What is the best way to break down multi-step engineering tasks for version control?

The best way to break down multi-step engineering tasks is organizing work into bite-sized steps suitable for incremental delivery, ensuring each step aligns with a reproducible plan document for version control commits.

How do I generate a TDD workflow plan that includes documentation and file changes?

Generate a TDD workflow plan by producing a comprehensive blueprint that explicitly lists required file changes, corresponding test cases, and necessary documentation steps prior to writing any implementation code.

Can I save reproducible engineering plan documents to a specific directory path?

Yes, you can save reproducible engineering plan documents to a predictable directory path like docs/plans/YYYY-MM-DD-<feature-name>.md, ensuring consistent plan artifacts for future reference and version tracking.

Does writing an implementation plan before coding work for complex feature documentation?

Writing an implementation plan before coding works for complex features by generating a complete blueprint that guides engineering, testing, and documentation efforts, converting vague multi-step requirements into concrete executable steps.