---

name: sdlc-studio description: /sdlc-studio [type] [action] - SDLC pipeline: requirements, specifications, code, testing. Run /sdlc-studio help for commands and /sdlc-studio status for next steps. allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion

SDLC Studio

Manage project specifications and test artifacts. Supports the full pipeline from PRD creation through Epic decomposition, User Story generation, and streamlined test automation.

Create vs Generate: Know the Difference

Generate mode is NOT documentation. It produces a migration blueprint - a specification detailed enough that another team could rebuild the system in a different technology stack. Generated specs MUST be validated by running tests against the existing implementation.

New to Create vs Generate? Read reference-philosophy.md first - it explains why these modes exist and how they differ fundamentally.

Quick Start

Copy/sdlc-studio help                    # Show command reference
/sdlc-studio status                  # Check pipeline state and next steps
/sdlc-studio prd generate            # Create PRD from codebase
/sdlc-studio trd generate            # Create TRD from codebase
/sdlc-studio epic                    # Generate Epics from PRD
/sdlc-studio story                   # Generate Stories from Epics
/sdlc-studio bug                     # Create or list bugs
/sdlc-studio code plan               # Plan implementation for story
/sdlc-studio code implement          # Execute implementation plan
/sdlc-studio code test               # Run tests with traceability
/sdlc-studio code verify             # Verify code against AC
/sdlc-studio code check              # Run linters and checks
/sdlc-studio tsd                      # Create test strategy document
/sdlc-studio test-spec               # Generate test specifications
/sdlc-studio test-automation         # Generate executable tests
/sdlc-studio story plan              # Preview story workflow
/sdlc-studio story implement         # Execute story workflow (all phases)
/sdlc-studio epic plan               # Preview epic workflow (all stories)
/sdlc-studio epic implement          # Execute epic workflow (all stories)

Get Help for Any Type

Copy/sdlc-studio {type} help             # Show help for specific type

Examples:

Copy/sdlc-studio prd help                # PRD commands and options
/sdlc-studio epic help               # Epic generation help
/sdlc-studio bug help                # Bug tracking help
/sdlc-studio code help               # Code plan/test/verify/check help
/sdlc-studio test-spec help          # Test specification help
/sdlc-studio test-automation help    # Test automation help

Each help page shows:

• Available actions and what they do
• Prerequisites
• Output format and location
• Examples
• Next steps

When to Use

• "Create a PRD for this project"
• "Generate requirements from this codebase"
• "Create a TRD for this project"
• "Generate technical requirements from this codebase"
• "Generate epics from the PRD"
• "Create user stories from the epics"
• "Create personas for this project"
• "Report a bug I found"
• "List all open bugs"
• "Fix this bug"
• "Plan the implementation for this story"
• "Implement the plan for this story"
• "Implement this story with TDD"
• "Check my code quality"
• "Verify my code against acceptance criteria"
• "Run the tests for this epic" → /sdlc-studio code test --epic EP0001
• "Generate test specifications"
• "Create automated tests from specs"
• "What's the current status of my specs?"
• "Run the full workflow for this story"
• "Implement all stories in this epic"
• "Show me the workflow plan for US0024"
• /sdlc-studio prd, /sdlc-studio trd, /sdlc-studio epic, /sdlc-studio story, /sdlc-studio persona
• /sdlc-studio bug, /sdlc-studio bug list, /sdlc-studio bug fix, /sdlc-studio bug verify, /sdlc-studio bug close
• /sdlc-studio code plan, /sdlc-studio code implement, /sdlc-studio code test, /sdlc-studio code verify, /sdlc-studio code check
• /sdlc-studio tsd, /sdlc-studio test-spec, /sdlc-studio test-automation
• /sdlc-studio story plan, /sdlc-studio story implement, /sdlc-studio epic plan, /sdlc-studio epic implement
• /sdlc-studio status

File Loading Guide

Claude loads files progressively - only what's needed for the current task.

Loading hierarchy:

CopyLevel 1: SKILL.md (Always loaded - "what can I do?")
    ↓
Level 2: help/{type}.md (On command - "how do I do X?")
    ↓
Level 3: reference-*.md (Deep workflow - "step-by-step for X")
    ↓
Level 4: templates/*.md (Creating artifacts - "what goes in the file?")

Pattern-based loading:

Reference file mapping:

Arguments

Type Reference

Command Reference

Pipeline Status

Requirements Pipeline

Technical Requirements

Bug Tracking

Development Pipeline

Testing Pipeline

Workflow Automation

Workflows

For detailed step-by-step workflows, see reference files:

• reference-requirements.md - PRD, TRD, Persona workflows
• reference-specifications.md - Epic, Story, Bug workflows
• reference-code.md - Code plan, implement, review, check, test workflows
• reference-testing.md - TSD, Test Spec, Test Automation workflows

---

Output Formats

Each type with {NNNN} also has an _index.md registry.

Examples

Copy# Requirements
/sdlc-studio prd generate             /sdlc-studio prd create
/sdlc-studio epic                     /sdlc-studio story --epic EP0001

# Bugs
/sdlc-studio bug                      /sdlc-studio bug list --status open
/sdlc-studio bug fix --bug BG0001     /sdlc-studio bug verify --bug BG0001

# Development (manual)
/sdlc-studio code plan --story US0001 /sdlc-studio code implement
/sdlc-studio code implement --tdd     /sdlc-studio code implement --no-docs
/sdlc-studio code test --story US0001 /sdlc-studio code verify
/sdlc-studio code check

# Workflow automation (recommended)
/sdlc-studio story plan --story US0001    /sdlc-studio story implement --story US0001
/sdlc-studio epic plan --epic EP0001      /sdlc-studio epic implement --epic EP0001
/sdlc-studio story implement --from-phase 3  # Resume from phase
/sdlc-studio epic implement --story US0002   # Resume from story

# Testing
/sdlc-studio test-spec --epic EP0001  /sdlc-studio test-automation
/sdlc-studio status

See help/{type}.md for full examples per type.

Error Handling

Missing prerequisites: Prompts to run earlier pipeline step (e.g., no PRD → prd, no epics → epic, no stories → story, no plans → code plan). Existing files: Warns and asks to continue unless --force. No type: Asks user which type. ID collision: Auto-increments. Open questions: Reports and pauses. Unknown language: Asks user to specify framework. Incomplete scope: Plans MUST cover all in-scope items and ACs; blocks if items deferred to "future stories".

Typical Workflow

Greenfield (Create Mode)

CopyPRD → TRD → Personas → Epics → Stories
                                  │
                    ┌─────────────┴─────────────┐
                    │                           │
              TDD Path                    Test-After Path
              (test-first)                (code-first)
                    │                           │
              test-spec                    code plan
                    │                           │
              code plan                   code implement
                    │                           │
         code implement --tdd              test-spec
                    │                           │
              code verify                 test-automation
                    │                           │
              code test                     code verify
                                                │
                                            code test

Per-story choice: You choose TDD or Test-After for each story, not globally. Both paths produce the same artifacts, just in different order.

Automated Workflow (Recommended)

For streamlined development, use workflow automation:

CopyPRD → TRD → Personas → Epics → Stories
                                  │
                          story plan --story US0001
                                  │
                          story implement --story US0001
                                  │
                          (all 7 phases run automatically)

Or at the epic level:

CopyPRD → TRD → Personas → Epics → Stories
                                  │
                          epic plan --epic EP0001
                                  │
                          epic implement --epic EP0001
                                  │
                          (all stories processed in dependency order)

Workflow phases per story:

1. Plan (code plan)
2. Test Spec (test-spec)
3. Tests (test-automation)
4. Implement (code implement)
5. Test (code test)
6. Verify (code verify)
7. Check (code check)

Brownfield (Specification Extraction)

Copyprd generate → trd generate → persona generate → epic → story generate → test-spec → test-automation → code test (VALIDATE)

Critical: The code test step validates specs against reality. Not optional.

Development Cycle

Copycode plan → code implement → code test → code verify → code check

Status: Draft/Ready → Planned → In Progress → Review → Done

Daily Usage

Copy/sdlc-studio status          # What needs attention?
/sdlc-studio code plan       # Plan next story
/sdlc-studio code implement  # Execute plan

See Also

Philosophy: reference-philosophy.md - Read this first. Explains Create vs Generate modes and why generate mode produces migration blueprints, not documentation.

Decisions: reference-decisions.md - Decision impact matrix, TDD decision tree, Ready status criteria, cross-stage validation checkpoints.

Help: help/help.md (main), help/{type}.md (type-specific)

References: reference-prd.md, reference-trd.md, reference-persona.md (Requirements), reference-epic.md, reference-story.md, reference-bug.md (Specifications), reference-architecture.md (Architecture), reference-code.md (Code, Test), reference-testing.md (Test artifacts), reference-test-best-practices.md (Test pitfalls), reference-test-e2e-guidelines.md (E2E patterns)

Templates: templates/prd-template.md, trd-template.md, epic-template.md, story-template.md, personas-template.md, plan-template.md, plan-index-template.md, bug-template.md, bug-index-template.md, tsd-template.md, test-spec-template.md, automation/*.template