sdlc-studio

# 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. This file is the always-loaded router. It carries only what is needed to route a request: philosophy gates, the Progressive Loading Guide, and pointers. The full command catalogue, argument reference, workflow diagrams, and reference index are loaded on demand from `help/help.md`, `help/arguments.md`, and `help/references.md`. ## 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. **Personas are working seats, not static artifacts** - goal-directed (Cooper) personas that c...