writing-plans

Translate written specs into actionable implementation plans with TDD and DRY.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers often struggle to translate a formal spec into concrete, executable steps. This Skill provides a structured blueprint that details required files, code sketches, tests, docs, and verification criteria, ensuring nothing is overlooked.

Core Features & Use Cases

  • Generate bite-sized tasks with precise file paths, edits, tests, and commands
  • Enforce DRY, YAGNI, and TDD principles throughout planning
  • Save plans to docs/plans/YYYY-MM-DD-<feature-name>.md for easy archival and review
  • Facilitate clear handoffs between planning, implementation, and verification

Quick Start

Use the writing-plans skill to create an implementation plan for a feature described in a spec.

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

Implementation plans are generated by translating a written spec into structured, bite-sized tasks detailing precise file paths, code sketches, tests, and verification commands. This ensures all required code changes and documentation steps are explicitly mapped before execution.

Can I enforce TDD and DRY principles when planning software features?

Yes, TDD, DRY, and YAGNI principles are enforced throughout the planning process. The generated blueprint structures tasks to explicitly require test creation and verification steps alongside code edits, ensuring clean, testable development practices are integrated from the start.

What is the best way to document implementation plans for team handoffs?

Documenting implementation plans involves saving the generated task blueprints to `docs/plans/YYYY-MM-DD-<feature-name>.md`. This markdown archival format facilitates clear review and smooth handoffs between planning, implementation, and verification phases.

Does planning automation work for debugging and documentation tasks?

Planning automation applies directly to pre-code phases, debugging, and documentation tasks. It breaks down these scenarios into explicit, executable steps with required file changes and verification criteria, preventing overlooked edge cases during complex troubleshooting.

How do I structure implementation tasks to avoid missing file changes or tests?

Structure implementation tasks by generating a blueprint that details required files, code sketches, tests, docs, and exact verification commands for each step. Frequent commits are enforced within these bite-sized tasks to maintain incremental progress and traceability.