csdlc-doc

Generate Step 0 design docs for projects, epics, or subsystems using bundled templates.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: csdlc-doc
Source: https://github.com/danhannah94/claymore-plugins/tree/main/csdlc/skills/csdlc-doc
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates Step 0 design docs for features, epics, or projects, enabling fast alignment and reducing ambiguity before development.

Core Features & Use Cases

  • Generate a Step 0 design doc tailored to project, epic, or subsystem level using the bundled templates.
  • Guide collaborative refinement and breakdown workflows to produce actionable stories and acceptance criteria.
  • Use case: a product team documents a new feature with goals, success metrics, and boundaries before coding begins.

Quick Start

Draft a Step 0 design doc for your feature using the appropriate template level and begin refinement.

Frequently Asked Questions about csdlc-doc

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

FAQPage Schema
How do I generate a Step 0 design doc for a new feature?

To generate a Step 0 design doc, use bundled templates tailored to project, epic, or subsystem levels to draft precise documentation with goals, success metrics, and boundaries before coding begins.

What is a Step 0 design doc and when do I need one?

A Step 0 design doc is a foundational project document that enables fast alignment and reduces ambiguity before development. You need one when starting a new feature, epic, or subsystem.

Can I use these design doc templates for both epics and subsystems?

Yes, you can use the bundled templates for project, epic, and subsystem levels. They guide refinement and alignment to produce a ready-to-refine document tailored to your specific scope.

How do I refine a design doc after the initial draft?

You refine a design doc by using collaborative refinement workflows and further prompts like /refine and /breakdown. This process guides the initial draft into actionable stories and acceptance criteria.

Where can I save the generated design documentation?

You can save the generated design documentation locally or to Foundry. The output serves as a ready-to-refine foundation for subsequent workflows like /refine and /breakdown.

Are there limitations to using automated design doc generation?

The main limitation is that the generated design doc is a ready-to-refine draft rather than a final specification. It requires collaborative refinement and breakdown workflows to produce actionable stories.