/sdlc-studio [type] [action] - SDLC pipeline: requirements, specifications, code, testing. Run /sdlc-studio help for commands and /sdlc-studio status for next steps.
Instrucciones de origen · Vista previa de solo lectura
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.
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.
Critical Philosophy (Read This First)
Two modes for every artifact type:
Mode
Purpose
When to Use
create
Author new specifications from user input
Greenfield projects, new features
generate
Extract specifications from existing code
Brownfield projects, documentation gaps
New to Create vs Generate? Read reference-philosophy.md - it explains why these modes exist and how they differ fundamentally.
Using generate mode? You MUST read reference-philosophy.md#generate-mode first - generated specs must be validated by tests.
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.
Quick Start
/sdlc-studio help# Show command reference
/sdlc-studio status # Check pipeline state and next steps
/sdlc-studio prd generate
/sdlc-studio trd generate
/sdlc-studio epic
/sdlc-studio story
/sdlc-studio bug
/sdlc-studio code plan
/sdlc-studio code implement
/sdlc-studio code
/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
# Create PRD from codebase
# Create TRD from codebase
# Generate Epics from PRD
# Generate Stories from Epics
# Create or list bugs
# Plan implementation for story
# Execute implementation plan
test
# Run tests with traceability
# Verify code against AC
# Run linters and checks
# Create test strategy document
# Generate test specifications
# Generate executable tests
# Preview story workflow
# Execute story workflow (all phases)
# Preview epic workflow (all stories)
# Execute epic workflow (all stories)
Get Help for Any Type
/sdlc-studio {type} help# Show help for specific type
Examples:
/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
For output formats, status values, and file locations: See reference-outputs.md
Examples
# 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.
Typical Workflow
Greenfield (Create Mode)
PRD → 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:
PRD → TRD → Personas → Epics → Stories
│
story plan --story US0001
│
story implement --story US0001
│
(all 7 phases run automatically)
Or at the epic level:
PRD → TRD → Personas → Epics → Stories
│
epic plan --epic EP0001
│
epic implement --epic EP0001
│
(all stories processed in dependency order)
Workflow phases per story:
Plan (code plan)
Test Spec (test-spec)
Tests (test-automation)
Implement (code implement)
Test (code test)
Verify (code verify)
Check (code check)
Review (status review)
Brownfield (Specification Extraction)
prd 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
code plan → code implement → code test → code verify → code check
/sdlc-studio status # Visual dashboard - what needs attention?
/sdlc-studio status --brief # Quick: Requirements 85% | Code 90% | Tests 94%
/sdlc-studio hint # Single next step
/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.
