csdlc-breakdown

Break down design documents into structured stories with acceptance criteria.

Updated Apr 10, 2026

Search Tags:#workflow #agile #backlog #breakdown #design-doc #story-decomposition

Ready to run

npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-breakdown

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: csdlc-breakdown
Source: https://github.com/danhannah94/claymore-plugins/tree/main/csdlc/skills/csdlc-breakdown
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down refined design documents into structured, implementable stories with clear acceptance criteria, guiding developers from concept to backlog.

Core Features & Use Cases

Converts design docs into discrete, story-level artifacts with IDs, scope, acceptance criteria, target files, boundaries, and dependencies.
Supports Foundry-based workflows or local-file workflows for Step 1 decomposition.
Produces a sequenced plan that clarifies serial vs parallel work and prerequisite foundation stories.

Quick Start

Provide your refined design doc to begin breaking it down into stories.

Frequently Asked Questions about csdlc-breakdown

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

FAQPage Schema

How do I break down a design doc into actionable agile stories?▼

Breaking down a design doc involves decomposing the refined document into structured stories with clear scope, acceptance criteria, target files, and boundaries for implementation.

What is story decomposition for a project backlog?▼

Story decomposition is the process of identifying project prefixes, scopes, and dependencies to deliver a ready-to-implement backlog with sequenced stories from a design document.

Does design doc to story breakdown work with local files?▼

Yes, design doc to story breakdown supports both Foundry-based workflows and local-file workflows, allowing you to process your design documents and generate implementable stories.

How do I sequence an agile backlog to clarify parallel work?▼

You sequence an agile backlog by analyzing story dependencies and boundaries to produce a sequenced plan that clarifies serial versus parallel work and identifies prerequisite foundation stories.

Can I generate acceptance criteria and target files from a design document?▼

Yes, you can generate acceptance criteria and target files from a design document by decomposing it into story-level artifacts that satisfy requirements for IDs, titles, scope, and complexity.