writing-plans

Decompose feature specifications into testable implementation steps with validation methods.

2.6k|696|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/zts212653/clowder-ai --skill writing-plans-zts212653
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/zts212653/clowder-ai/tree/main/cat-cafe-skills/writing-plans
Command: npx skills add https://github.com/zts212653/clowder-ai --skill writing-plans-zts212653

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates high-level specifications into actionable, step-by-step implementation plans, reducing guesswork and miscommunication during project kickoff.

Core Features & Use Cases

  • Converts requirements into concrete tasks with file changes, tests, and validation steps.
  • Emphasizes TDD, DRY, and YAGNI to keep scope tight and maintainable.
  • Provides traceability from acceptance criteria to actionable implementation steps.

Quick Start

Provide a feature spec or user story to generate a step-by-step implementation plan.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I decompose a feature spec into actionable implementation steps?

To decompose a spec, provide a feature spec or user story to generate a step-by-step implementation plan detailing incremental tasks, required artifacts, and validation methods.

What is the best way to plan tasks before coding using TDD?

Planning tasks before coding using TDD translates requirements into concrete tasks with file changes and validation steps, emphasizing TDD, DRY, and YAGNI to keep scope tight and maintainable.

How do I ensure traceability from acceptance criteria to executable tasks?

Traceability from acceptance criteria to executable tasks is achieved by detailing incremental tasks and required artifacts that map directly to the original specification requirements.

Does spec decomposition work for complex feature development?

Spec decomposition applies to feature development where clarifying tasks before coding is essential, reducing guesswork and miscommunication during project kickoff regardless of complexity.

Do I need to provide a full specification to generate an implementation plan?

You need to provide a feature spec or user story as input to generate an actionable, step-by-step implementation plan with clearly defined file changes and tests.