writing-plans

Generate implementation plans with tasks, file paths, code snippets, and test steps.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill writing-plans-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/workflow/writing-plans
Command: npx skills add https://github.com/ajsai47/holyclaude --skill writing-plans-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent, error-prone implementation of multi-step features from specs, where engineers lack full context of the codebase and best practices, leading to rework, missed requirements, and inconsistent code quality.

Core Features & Use Cases

  • Structured Task Decomposition: Breaks down specs into bite-sized, actionable tasks with exact file paths, code snippets, test steps, and commit commands, so engineers never have to guess what to do next.
  • Best Practice Enforcement: Automatically embeds DRY, YAGNI, TDD, and frequent commit guidelines into every plan, ensuring consistent, high-quality implementation across the team.
  • Use Case: For example, if you have a spec to add user authentication to your app, this Skill generates a complete plan with failing tests, minimal implementation steps, and validation checks, so any engineer can implement it correctly without prior knowledge of your codebase.

Quick Start

Provide your feature spec or requirements to the writing-plans skill to generate a complete, actionable implementation plan with test steps and commit guidance.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn feature specs into actionable implementation plans for software development?

You can generate a comprehensive implementation plan by providing your feature spec, which decomposes requirements into bite-sized tasks with exact file paths, code snippets, test steps, and commit commands to eliminate implementation guesswork.

What is the best way to break down software requirements into TDD task workflows?

Spec decomposition breaks requirements into actionable tasks enforcing Test-Driven Development, DRY, and YAGNI principles. It defines failing tests, minimal implementation steps, and validation checks to ensure consistent, high-quality code workflows across your team.

Does this implementation planning approach work without prior knowledge of my codebase?

Yes, implementation plans are context-agnostic and provide exact file paths, code snippets, and commit commands. This allows any engineer to implement features correctly from a spec without needing prior knowledge of the existing codebase.

Can I validate plan completeness against spec requirements before coding starts?

Yes, plan validation checks completeness against spec requirements to ensure buildable, error-free implementation. This prevents inconsistent, error-prone implementation and reduces rework by validating all requirements are covered before coding.

How do I enforce frequent commit best practices during feature implementation?

Implementation plans automatically embed frequent commit guidelines and exact commit commands into every task breakdown. This enforces best practices throughout the software development workflow, ensuring consistent code quality and traceable progress.