| name | sdlc-studio |
| description | The antidote to vibe coding: a full software engineering team at your fingertips. Create or reverse-engineer PRDs, TRDs, personas, epics, and user stories with acceptance criteria, then plan, implement, test, and verify code against them - plus an autonomous Goal-Driven sprint loop that drives a prioritised batch to a goal, an adversarial audit, status dashboards, reconciliation, change requests, RFCs, test specs, test automation, and bug tracking. Use when asked about PRDs, requirements documents, epics, user stories, personas, implementation planning, sprint or autonomous delivery, audit, test specs, test automation, project status, bugs, change requests, or any /sdlc-studio [type] [action] command. Run /sdlc-studio help for the catalogue and /sdlc-studio status for next steps. NOT for: one-off code questions, quick formatting or lint fixes, or repos where no software lifecycle is wanted - for a zero-setup taster on an existing repo, start with audit --profile repo. |
| license | MIT |
| compatibility | Requires Python 3.10+ for bundled scripts; gh CLI (authenticated) for GitHub sync commands. Agentic wave execution (--agentic) is Claude-Code-only. |
| metadata | {"version":"4.1.0","openclaw":{"emoji":"📋","requires":{"bins":["python3"]}}} |
| allowed-tools | Read, Glob, Grep, Write, Edit, Bash, Agent |
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 consult, seat-score the backlog, review diffs, and hold the author != reviewer gate.
Resolve one for any review: scripts/persona_resolve.py resolve --seat <role> --render review.
Operating Doctrine – onboarding to a project? Read reference-doctrine.md first. It is the project-agnostic working discipline (the skill is the operating system; RFC/CR/ADR choice; files-are-truth + reconcile-from-census; reconcile/verify/review cadence; ship-paperwork-in-the-same-commit; consult gates; TDD; cross-repo numbering; recall cross-project lessons/ before substantive decisions). A project's own agent-instructions file (AGENTS.md; Claude Code's CLAUDE.md can import it with @AGENTS.md) = this doctrine + that project's specifics; start from templates/agent-instructions.md. The cross-project lessons-learned folder is lessons/ (see help/lessons.md).
Quick Start
/sdlc-studio help
/sdlc-studio status
/sdlc-studio hint
/sdlc-studio review
/sdlc-studio reconcile
/sdlc-studio prd generate
/sdlc-studio epic
/sdlc-studio story
/sdlc-studio code plan
/sdlc-studio code implement
/sdlc-studio story implement
/sdlc-studio epic implement
/sdlc-studio project implement
For the full catalogue (bug, cr, rfc, persona, consult, chat, trd, test-*, repo map,
sync, and every flag), run /sdlc-studio help or read help/help.md.
Deterministic Entry Points (run the script, do not hand-do it)
Ids, index rows, status cascades, and AC verdicts are tool-allocated - hand-authoring
any of them is an error. For a mechanical task, reach for the script first
(full catalogue: reference-scripts.md):
| Doing... | Run |
|---|
| Create an artifact (bug/CR/story/epic/RFC) | scripts/artifact.py new --type bug --title "..." --affects "a.py, b.py" --points 3 |
| File a finding as a Bug/CR/RFC | scripts/file_finding.py file --type bug --title "..." --summary "..." --affects "a.py" --points 3 |
| Detect, then fix, index/status drift | scripts/reconcile.py detect then apply |
| Diagnose structure or status-vocab errors | scripts/validate.py check |
| Change a status (+ index/epic cascade) | scripts/transition.py set --id CR0001 --status Approved |
| Verify a story's executable ACs | scripts/verify_ac.py |
| Run the portable CI gate | scripts/gate.py |
| Gate a release tag (gate + executing AC verify, one exit code) | scripts/gate.py --release |
The interactive commands (/sdlc-studio bug create and friends) are wrappers over the
same allocation - a headless or consuming-project agent calls the scripts directly.
Get Help for Any Type
/sdlc-studio {type} help
Examples: /sdlc-studio epic help, /sdlc-studio code help, /sdlc-studio bug help.
When to Use
Use when asked about: PRD, TRD, epics, stories, personas, bugs, code planning, implementation, testing, test specs, test automation, project status, or any /sdlc-studio command.
Instructions
When invoked with /sdlc-studio [type] [action]:
- Parse Command: Extract type and action from arguments
- Load Help File: Read
help/{type}.md for command-specific guidance
- Check Philosophy: If generate mode, load
reference-philosophy.md#generate-mode FIRST
- Follow Progressive Loading:
- Load reference files only for multi-step workflows
- Section-read large references: for a reference over ~400 lines (epic,
story, code, outputs, decisions), read its Reading Guide / Contents first,
then load ONLY the named section (Grep the anchor, then an offset read) -
never whole-file-read a large reference for a single-section task
- Load templates only when creating artifacts
- Load decision files when choosing approaches (TDD, Ready status)
- Execute Workflow: Follow step-by-step procedure in reference file
- Update Status: Modify artifact status markers per
reference-outputs.md
- Validate: Check Ready criteria in
reference-decisions.md before proceeding
Note: Version checks run on hint and status commands only (see those help files).
See "Progressive Loading Guide" below for detailed file loading patterns.
Progressive Loading Guide
Claude loads files progressively based on task needs. Where a cell names a
section anchor, load that section only - and for any reference over ~400
lines, honour its Reading Guide instead of a whole-file read:
| Task Type | Primary Load | Secondary Load | Decision Load |
|---|
| Understanding a command | help/{type}.md | - | - |
| Full command catalogue | help/help.md | - | - |
| Argument / flag reference | help/arguments.md | - | - |
| Reference & template catalogue | help/references.md | - | - |
| Create mode workflow | help/{type}.md | reference-{domain}.md | reference-philosophy.md#create-mode |
| Generate mode workflow | reference-philosophy.md#generate-mode | help/{type}.md | reference-{domain}.md |
| Creating artifacts | scripts/artifact.py (new/batch allocates id + index row) | templates/core/{type}.md | reference-outputs.md |
| Filing a finding as Bug/CR/RFC | scripts/file_finding.py | templates/core/{type}.md | reference-audit.md |
| Loading modules | templates/modules/{domain}/*.md | - | - |
| Planning code | reference-code.md#code-plan-workflow | reference-decisions.md#story-ready | best-practices/{language}.md |
| Choosing TDD/Test-After | reference-decisions.md#tdd-decision-tree | reference-test-best-practices.md | - |
| Validating Ready status | reference-decisions.md#{type}-ready | reference-outputs.md | - |
| Document review | reference-review.md | reference-{doc}.md | - |
| Adversarial audit (weakness-hunt over the artifact graph) | reference-audit.md | templates/automation/audit-finder.md | scripts/file_finding.py |
| Schema upgrade (project artifacts) | reference-upgrade.md | reference-config.md | - |
| Skill self-update (check + upgrade the install) | reference-skill-update.md | scripts/version_check.py | help/skill-update.md |
| Portable CI quality gate (run the checks in any CI) | help/gate.md | scripts/gate.py | reference-scripts.md |
| Product layer / PVD (multi-repo product) | reference-pvd.md | templates/core/pvd.md | help/pvd.md |
| Project orchestration | reference-project.md | reference-epic.md | reference-config.md |
| Agentic execution | reference-agentic-lessons.md | reference-epic.md | - |
| Sprint (Goal-Driven Development loop) | reference-sprint.md | help/sprint.md | reference-project.md |
End-of-sprint report (sprint report: delivered, cost, velocity) | help/sprint.md | reference-sprint.md | scripts/sprint_report.py |
| Deploy last-mile (gate, verify, record - orchestrate-only) | reference-deploy.md | help/deploy.md | reference-config.md#deploy |
| Building agentic wave prompts | reference-agent-prompt-template.md | reference-repo-map.md | reference-agentic-lessons.md#lessons-accumulation |
| Change request workflow | help/cr.md | reference-cr.md | reference-outputs.md |
| RFC / design exploration | help/rfc.md | reference-rfc.md | reference-outputs.md |
| Invoking skill internals | reference-scripts.md | scripts/README.md | - |
| Ranking files for a story | reference-repo-map.md | help/repo-map.md | reference-agent-prompt-template.md#agent-prompt-template |
| Verifying ACs against codebase | reference-verify.md | help/verify.md | reference-reconcile.md#verify-scope |
| Mutation-checking the changed surface (can the tests fail?) | help/mutation.md | scripts/mutation.py | reference-test-best-practices.md#mutation-check |
| Syncing CR/Story/Epic with GitHub | reference-github-sync.md | help/github-sync.md | reference-cr.md#cr-sync-workflow |
| Onboarding to a project / operating doctrine | reference-doctrine.md | help/init.md | lessons/_index.md |
| Starting greenfield / "what order do I run things in?" | help/getting-started.md | help/init.md | reference-sprint.md |
| Adopting existing code / "get a spec out of this code" | help/brownfield-runbook.md | reference-philosophy.md | help/prd.md |
| Project constitution / machine-checkable principle gate | templates/constitution.md | scripts/constitution.py | reference-doctrine.md#constitution |
| Recording and loading project lessons | reference-agentic-lessons.md#lessons-accumulation | help/lessons.md | reference-agent-prompt-template.md#agentic-execution |
| Recalling cross-project lessons (before a decision) | lessons/_index.md | help/lessons.md | reference-doctrine.md |
| Operator patterns (memory drift, incident localisation, release-gate) | reference-operator-heuristics.md | templates/workflows/release-gate.md | reference-reconcile.md#numeric-claim-drift |
| Hypothesis discipline (don't guess root cause) | reference-operator-heuristics.md#hypothesis-discipline | reference-bug.md#bug-close-workflow | reference-test-best-practices.md#verification-depth-tiers |
| Preparing to tag a release | templates/workflows/release-gate.md | reference-operator-heuristics.md | reference-reconcile.md |
| Deploy readiness (cold-spawn, smoke budget, rollback, soak) | reference-deploy-readiness.md | reference-test-best-practices.md#verification-depth-tiers | reference-decisions.md#release-strategy-decision |
| Verification depth tiers (smoke / functional / conversational / soak / live) | reference-test-best-practices.md#verification-depth-tiers | templates/core/bug.md | templates/core/story.md |
| Test-timeout tuning (measure local + CI variance) | reference-test-best-practices.md#test-timeout-tuning | - | - |
| Validation workflows / advanced testing patterns | reference-test-validation.md | reference-test-best-practices.md | - |
| E2E mocking patterns and strategies | reference-test-e2e-guidelines.md | reference-test-best-practices.md#test-anti-patterns | - |
| Multi-persona pressure-test canvas (unsettled design) | reference-consult.md#pressure-test-canvas | reference-decisions.md | - |
| Creating or consulting personas / review seats | reference-persona.md#which-doc | help/persona.md | reference-consult.md |
| Test spec / test automation | help/test-spec.md | reference-test-spec.md | reference-test-automation.md |
| Plan-file lifecycle (active / archive / list) | reference-plan-files.md | help/plan.md | - |
| Reconcile cadence triggers | reference-reconcile.md#cadence-triggers | help/status.md#reconcile-recommendation | - |
| Transition an artifact's status (+ index/epic cascade) | scripts/transition.py | reference-outputs.md#status-transitions | reference-reconcile.md |
| Bounding large indexes (archival + slice-read) | reference-outputs.md#index-archival | scripts/archive.py | reference-reconcile.md |
Template structure:
| Path | Purpose |
|---|
templates/core/*.md | Streamlined core templates (v2) |
templates/indexes/*.md | Index file templates |
templates/modules/trd/*.md | Optional TRD modules (diagrams, containers, ADR) |
templates/modules/tsd/*.md | Optional TSD modules (contract, perf, security) |
templates/modules/epic/*.md | Optional Epic perspective modules |
templates/config-defaults.yaml | Skill default configuration |
Module loading flags:
| Flag | Modules Loaded |
|---|
trd create --with-diagrams | modules/trd/c4-diagrams.md |
trd create --with-containers | modules/trd/container-design.md |
trd create --full | All TRD modules |
epic --perspective engineering | modules/epic/engineering-view.md |
epic --perspective product | modules/epic/product-view.md |
epic --perspective test | modules/epic/test-view.md |
Reference file mapping:
Reference files follow the pattern reference-{domain}.md. When executing
a workflow, load the reference file matching the artifact type being created
or modified. Cross-domain files (reference-decisions.md, reference-outputs.md,
reference-philosophy.md) load as needed for validation, status updates, and
approach decisions. The full index is in help/references.md.
Type Reference
| Type | Description |
|---|
init | Initialise an empty project: folder tree, indexes, config, agent-instructions (greenfield step 1) |
pvd | Product Vision Document - the multi-repo product layer above the PRD (opt-in) |
prd | Product Requirements Document |
trd | Technical Requirements Document |
tsd | Test Strategy Document (project-level) |
persona | User Personas |
consult | Persona consultation on artefacts |
chat | Interactive persona sessions |
epic | Feature groupings (Epics) |
story | User Stories with acceptance criteria |
code | Implementation planning, testing, and quality |
test-spec | Consolidated test specification (plan + cases + fixtures) |
test-automation | Generate executable test code |
test-env | Containerised test environment setup |
bug | Bug tracking and traceability |
cr | Change requests (post-PRD change proposals) |
rfc | Request For Comments – design exploration of an unsettled space, pre-CR |
issue | Defect-side Discovery intake: a raw report, triaged into bugs |
refine | Decompose a request (RFC/CR) into an epic and stories, links wired |
triage | Decompose an Issue into the bugs that deliver its fix (mirror of refine) |
project | Project-level orchestration across all epics |
sprint | Goal-Driven Development loop: a prioritised batch driven along the goal ladder triage -> plan -> design -> done |
handoff | The run-close handoff guide: what remains, per item, with its pointer and a copilot-tail / judgement tag |
plan | Claude Code plan-file lifecycle (list, archive) |
decisions | Project decisions log (the project spine + delegated-agent handoff): add / list / promote |
retro | Sprint retro: what the batch taught and what changes because of it - the close gate reads its content |
lessons | Project and cross-project lessons: recall before a decision, record after one |
review | Unified PRD/TRD/TSD/Persona review against the codebase |
repo | Repository map: index symbols and imports, then rank files by relevance to a story |
migrate | Review every artefact and upgrade where safe: orchestrates conventions + version + sizing, reports what needs a human |
audit | Adversarial pressure-test over the whole artifact graph: refute-panel-verified weakness-hunt, triage-then-approve, cost-gated pre-flight |
reconcile | Detect and fix status drift across all artifacts |
gate | Portable, ecosystem-neutral CI quality gate over the deterministic checks |
deploy | Orchestrate-only deploy last-mile: gate, verify, record (operator-triggered, never autonomous) |
mutation | Executable mutation-check gate: prove the tests can FAIL (killed vs survived per mutation) |
skill-update | Check for and install a newer SDLC Studio release (the skill itself) |
status | Visual dashboard: Requirements, Code, Tests health |
hint | Single actionable next step |
help | Show command reference and examples |
Full Reference
The catalogues that used to live inline are now loaded on demand to keep this router lean:
| You need... | Read |
|---|
| Every command, grouped by pipeline, with examples | help/help.md (or run /sdlc-studio help) |
| The complete argument and flag table | help/arguments.md |
| Workflow diagrams (greenfield, brownfield, agentic, project) | help/help.md "Typical Workflows" |
The full reference-*.md index and template structure | help/references.md |
| Type-specific commands, prerequisites, output, examples | help/{type}.md |
| Step-by-step workflow detail for an artifact | reference-{domain}.md |
| Sprint loop (Goal-Driven Development) | help/sprint.md + reference-sprint.md |
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.
