writing-plans

Create step-by-step TDD implementation plans with file paths and tests.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/augustscl/awesome-xiawang-skills --skill writing-plans-augustscl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/augustscl/awesome-xiawang-skills/tree/main/writing-plans-0.1.0
Command: npx skills add https://github.com/augustscl/awesome-xiawang-skills --skill writing-plans-augustscl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts loose specifications and multi-step requirements into clear, test-driven implementation plans so an unfamiliar engineer can implement features reliably and with minimal back-and-forth.

Core Features & Use Cases

  • Complete, file-level guidance: exact files to create or modify, line ranges, and tests to add or update.
  • TDD-first, bite-sized steps: every task is a 2–5 minute actionable step such as "write the failing test" and "implement minimal code".
  • Execution handoff and conventions: includes required plan header, filename save convention, and options for subagent-driven or parallel execution when moving from planning to implementation.

Quick Start

Use the writing-plans skill to produce a TDD implementation plan from the provided spec and save it 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 a software specification into a TDD implementation plan?

To turn a spec into a TDD implementation plan, this Skill generates bite-sized 2–5 minute steps like writing failing tests and minimal code, providing exact file paths and commit guidance for unfamiliar engineers.

What is the best way to plan multi-step engineering tasks for new developers?

The best way to plan multi-step engineering tasks for new developers is generating file-level guidance with precise edits, test examples, and a required plan header, ensuring reliable execution with minimal back-and-forth.

How do I create bite-sized tasks for test-driven development?

You create bite-sized tasks for test-driven development by processing requirements into 2–5 minute actionable steps, explicitly detailing the failing tests to write and the minimal code to implement for each task.

Can I generate file-level coding instructions from loose requirements?

Yes, you can generate file-level coding instructions from loose requirements by converting specifications into plans that include exact files to create or modify, line ranges, and specific tests to add or update.

Does writing-plans support subagent-driven or parallel execution?

Writing-plans supports subagent-driven or parallel execution by including specific options and conventions for execution handoff when transitioning from the generated planning phase to actual implementation.