  _____ ____  _     _____   _____ _             _ _
 / ____|  _ \| |   / ____| / ____| |           | (_)
| (___ | | | | |  | |     | (___ | |_ _   _  __| |_  ___
 \___ \| | | | |  | |      \___ \| __| | | |/ _` | |/ _ \
 ____) | |_| | |__| |____  ____) | |_| |_| | (_| | | (_) |
|_____/|____/|_____\_____||_____/ \__|\__,_|\__,_|_|\___/

      From PRD to Quality, Fully Tested Code

A Claude Code skill for managing the full software development lifecycle.

What is This?

SDLC Studio is a skill (plugin) for Claude Code, Anthropic's official CLI tool for working with Claude. It adds commands that help you manage the entire software development process:

Write Product Requirements Documents (PRDs)
Break work into Epics and User Stories
Plan and implement code changes
Generate and run tests
Track bugs

The idea (for beginners)

Most AI coding jumps straight from a vague prompt to code, then drifts as the project grows. SDLC Studio adds the steps a real team uses, so Claude always has the context it needs to stay on track:

Requirements → Epics → User Stories → Plan → Code → Tests

Each step writes a plain markdown file under sdlc-studio/ in your project. You stay in control: review each artefact, then run the next command. Start a brand-new project with prd create, or point it at existing code with prd generate. If you ever lose your place, /sdlc-studio status shows where you are and /sdlc-studio hint tells you the single next thing to do.

New in v1.6.0

Four capabilities that keep status honest and keep agents grounded on large codebases:

Executable acceptance criteria – acceptance criteria run real tests, so a story's Verified state is derived from the code, not just claimed.
Repo map – a pure-Python indexer feeds agents the right files to read first, so they stop hallucinating APIs.
GitHub Issues sync – two-way sync of Change Requests, Stories, and Epics with GitHub Issues via the gh CLI.
Per-project lessons – failures from past runs are remembered and injected into future agent prompts.

Full details are under Workflows below.

New to Claude Code? You'll need to install Claude Code first before installing this skill.

Prerequisites

Before installing SDLC Studio, ensure you have:

Requirement	How to check	Install guide
Claude Code	Run `claude --version`	Getting Started
curl or wget (macOS/Linux)	Run `curl --version`	Usually pre-installed on macOS/Linux
PowerShell (Windows)	Run `$PSVersionTable.PSVersion`	Pre-installed on Windows

Installation

Option 1: One-line installer (recommended)

macOS/Linux - open your terminal and run:

curl -fsSL https://raw.githubusercontent.com/DarrenBenson/sdlc-studio/main/install.sh | bash

Windows - open PowerShell and run:

irm https://raw.githubusercontent.com/DarrenBenson/sdlc-studio/main/install.ps1 | iex

This installs SDLC Studio globally, making it available in all your projects.

What this does:

Downloads the latest version from GitHub
Creates ~/.claude/skills/ if it doesn't exist
Installs the skill files

Option 2: Install for a single project only

If you only want the skill available in one project:

macOS/Linux:

cd /path/to/your/project
curl -fsSL https://raw.githubusercontent.com/DarrenBenson/sdlc-studio/main/install.sh | bash -s -- --local

Windows - download the installer first, then run with options:

cd C:\path\to\your\project
irm https://raw.githubusercontent.com/DarrenBenson/sdlc-studio/main/install.ps1 -OutFile install.ps1
.\install.ps1 -Local

This creates .claude/skills/sdlc-studio/ in your current directory.

Option 3: Install a specific version

macOS/Linux:

curl -fsSL https://raw.githubusercontent.com/DarrenBenson/sdlc-studio/main/install.sh | bash -s -- --version v1.2.0

Windows:

.\install.ps1 -Version v1.2.0

Option 4: Manual installation

If you prefer not to use the installer script:

macOS/Linux:

# Clone the repository
git clone https://github.com/DarrenBenson/sdlc-studio.git
cd sdlc-studio

# Copy to your Claude Code skills directory
mkdir -p ~/.claude/skills
cp -r .claude/skills/sdlc-studio ~/.claude/skills/

Windows:

# Clone the repository
git clone https://github.com/DarrenBenson/sdlc-studio.git
cd sdlc-studio

# Copy to your Claude Code skills directory
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null
Copy-Item -Recurse .claude\skills\sdlc-studio "$HOME\.claude\skills\"

Verify Installation

After installing, verify it works:

Start Claude Code in any project directory:
```
cd /path/to/any/project
claude
```
Run the help command inside Claude Code:
```
/sdlc-studio help
```
You should see a list of available commands.
Check the status:
```
/sdlc-studio status
```
This shows the current state of your SDLC pipeline (empty for a new project).

Quick Start

Once installed, here's how to get started inside Claude Code:

First time? Check the status

/sdlc-studio status

This shows what artifacts exist and suggests next steps.

Don't know what to do next?

/sdlc-studio hint

This gives you a single, actionable next step based on your project's current state.

Starting a new project?

/sdlc-studio prd create

Claude will ask you questions about your project and create a Product Requirements Document.

Have existing code?

/sdlc-studio prd generate

Claude analyses your codebase and creates a PRD based on what it finds.

Common Commands

Command	What it does
`/sdlc-studio help`	Show all available commands
`/sdlc-studio status`	Show pipeline state and progress
`/sdlc-studio hint`	Get a single suggested next action
`/sdlc-studio prd create`	Create a new PRD interactively
`/sdlc-studio prd generate`	Generate PRD from existing code
`/sdlc-studio epic`	Generate Epics from your PRD
`/sdlc-studio story`	Generate User Stories from Epics
`/sdlc-studio code plan`	Plan implementation for a story
`/sdlc-studio code implement`	Execute your implementation plan
`/sdlc-studio epic implement --agentic`	Autonomous concurrent epic execution
`/sdlc-studio project plan`	Preview full-PRD execution order
`/sdlc-studio project implement --agentic`	Execute every epic in dependency order
`/sdlc-studio cr create`	Open a change request for post-PRD scope changes
`/sdlc-studio cr action --cr CR-NNNN`	Turn a CR into epics and stories
`/sdlc-studio reconcile --dry-run`	Detect index, dependency, and checkbox drift
`/sdlc-studio reconcile --verify`	Run executable AC verifiers and update Verified state
`/sdlc-studio repo map build`	Index the repo for Agent Prompt Templates
`/sdlc-studio repo map query --story US0001`	Rank files by relevance to a story
`/sdlc-studio cr sync`	Two-way sync CRs with GitHub Issues
`/sdlc-studio lessons list`	Print accumulated per-project lessons
`/sdlc-studio bug`	Report a new bug

Workflows

New Project (Greenfield)

Follow this sequence to build from scratch:

/sdlc-studio prd create        # 1. Define what you're building
/sdlc-studio trd create        # 2. Define technical approach
/sdlc-studio persona           # 3. Define who will use it
/sdlc-studio epic              # 4. Break into Epics
/sdlc-studio story             # 5. Break into Stories
/sdlc-studio tsd               # 6. Define test strategy
/sdlc-studio test-spec         # 7. Create test specifications
/sdlc-studio code plan         # 8. Plan first story
/sdlc-studio code implement    # 9. Build it

Existing Project (Brownfield)

Use generate to reverse-engineer documentation from code:

/sdlc-studio prd generate      # Analyse code, create PRD
/sdlc-studio trd generate      # Document technical decisions
/sdlc-studio persona generate  # Infer users from code
/sdlc-studio epic              # Create Epics for future work
/sdlc-studio story             # Break into Stories

Agentic Epic Execution

Use --agentic to run an entire epic autonomously. Stories are analysed for dependencies and hub file overlap, then executed in concurrent waves where safe:

/sdlc-studio epic plan --epic EP0001 --agentic       # Analyse and preview waves
/sdlc-studio epic implement --epic EP0001 --agentic   # Execute concurrently

Falls back to sequential for any stories with shared file conflicts. See /sdlc-studio epic help for details.

Full-Project Execution

Run the entire PRD in one pass. The project command builds a dependency graph across all epics, sorts them topologically, then executes each one, checkpoint-committing and reconciling between epics.

/sdlc-studio project plan                               # Preview execution order and waves
/sdlc-studio project implement --agentic                 # Execute every epic
/sdlc-studio project implement --agentic --from stories  # Generate missing stories first
/sdlc-studio project implement --resume EP0003           # Resume after a failure

State is persisted at sdlc-studio/.local/project-state.json so runs are resumable.

Change Requests

Post-PRD changes flow through the CR lifecycle rather than editing the PRD directly:

/sdlc-studio cr create              # Capture a new change request
/sdlc-studio cr list --status proposed
/sdlc-studio cr action --cr CR-0001 # Turn it into epics and stories
/sdlc-studio cr review              # Staleness and completion checks
/sdlc-studio cr close --cr CR-0001  # Mark Complete, Rejected, or Deferred

Reconcile Drift

Mechanical drift detection and repair across stories, epics, PRD, change requests, and index files:

/sdlc-studio reconcile --dry-run              # Preview changes
/sdlc-studio reconcile                        # Apply fixes
/sdlc-studio reconcile --scope stories        # Limit to a single artefact type
/sdlc-studio reconcile --verify               # Run executable AC verifiers

Reconcile is idempotent and runs automatically at epic and wave boundaries during agentic execution.

Executable Acceptance Criteria (v1.6.0)

Acceptance criteria can declare a verifier expression that reconcile runs against the live codebase. Status stops lying because the Verified state is derived, not asserted:

### AC1: Happy path email login
- **Given** a registered account
- **When** the user submits valid credentials
- **Then** they are redirected to /dashboard
- **Verify:** pytest tests/unit/auth/test_login.py::test_email_happy
- **Verified:** yes (2026-04-15)

Supported verifier prefixes: pytest, jest, vitest, go, file, grep, http ... -- <jq>, shell. Optional strict gate (require_ac_verification: true in config) refuses to mark a story Done until every AC passes.

Repo Map for Agent Prompts (v1.6.0)

The Agent Prompt Template's READ THESE FILES FIRST list is derived automatically from a pure-Python repo indexer so agents stop hallucinating APIs on large codebases:

/sdlc-studio repo map build
/sdlc-studio repo map query --story US0001 --top 10

Supports Python (stdlib ast), TypeScript, JavaScript, Go, Rust, Java, Kotlin, C#, Ruby, PHP, Swift. No ctags dependency.

GitHub Issues Sync (v1.6.0)

Two-way sync between local CR / Story / Epic files and GitHub Issues via the gh CLI. A CR and its linked Issue are two representations of the same record:

/sdlc-studio cr sync                      # Push + pull CRs
/sdlc-studio project sync                 # All three types
/sdlc-studio project sync cascade         # Merged-PR cascade candidates

Labels use the sdlc: prefix (sdlc:cr, sdlc:story, sdlc:status:*, sdlc:priority:P1..P4). Requires gh CLI authenticated. See reference-github-sync.md for setup.

Per-Project Lessons (v1.6.0)

sdlc-studio/.local/lessons.md accumulates failure patterns specific to the current project. Loaded at every agentic wave start and injected into Agent Prompt Templates as a Known Pitfalls on This Project section:

/sdlc-studio lessons list                 # Print accumulated lessons
/sdlc-studio lessons add                  # Interactive add

Daily Development

/sdlc-studio code plan         # Plan your changes
/sdlc-studio code implement    # Make the changes
/sdlc-studio code review       # Review what you built
/sdlc-studio code test         # Run tests

Output Structure

SDLC Studio creates a sdlc-studio/ directory in your project:

sdlc-studio/
  prd.md                      # Product Requirements Document
  trd.md                      # Technical Requirements Document
  tsd.md                      # Test Strategy Document
  personas.md                 # User Personas
  epics/
    _index.md                 # Epic registry
    EP0001-*.md               # Individual Epic files
  stories/
    _index.md                 # Story registry
    US0001-*.md               # Individual Story files
  bugs/
    _index.md                 # Bug registry
    BG0001-*.md               # Individual Bug files
  plans/
    _index.md                 # Plan registry
    PL0001-*.md               # Implementation plans
  test-specs/
    _index.md                 # Spec registry
    TSP0001-*.md              # Test Specifications

tests/                        # Generated test code (in project root)
  unit/
  integration/
  api/
  e2e/

Troubleshooting

"Command not found" when running /sdlc-studio

The skill isn't installed correctly. Check:

Is the skill in the right place?
```
ls ~/.claude/skills/sdlc-studio/SKILL.md
```
If this file doesn't exist, reinstall.
For project-level installs, check:
```
ls .claude/skills/sdlc-studio/SKILL.md
```

Try reinstalling:

curl -fsSL https://raw.githubusercontent.com/DarrenBenson/sdlc-studio/main/install.sh | bash

Installer fails to download

Check your internet connection and that you can access GitHub:

curl -I https://github.com/DarrenBenson/sdlc-studio

If you're behind a corporate proxy, you may need to configure proxy settings.

Commands run but nothing happens

Make sure you're running commands inside Claude Code, not in your regular terminal. Start Claude Code first:

claude

Then type the /sdlc-studio commands at the Claude Code prompt.

Updating

To update to the latest version, simply run the installer again:

macOS/Linux:

curl -fsSL https://raw.githubusercontent.com/DarrenBenson/sdlc-studio/main/install.sh | bash

Windows:

irm https://raw.githubusercontent.com/DarrenBenson/sdlc-studio/main/install.ps1 | iex

The installer removes the old version before installing the new one.

Uninstalling

Global installation

macOS/Linux:

rm -rf ~/.claude/skills/sdlc-studio

Windows:

Remove-Item -Recurse -Force "$HOME\.claude\skills\sdlc-studio"

Project-level installation

macOS/Linux:

rm -rf .claude/skills/sdlc-studio

Windows:

Remove-Item -Recurse -Force .claude\skills\sdlc-studio

Getting Help

Inside Claude Code:

/sdlc-studio help              # Show all commands
/sdlc-studio prd help          # Help for PRD commands
/sdlc-studio epic help         # Help for Epic commands
/sdlc-studio test-spec help    # Help for test specification

Documentation

SKILL.md - Full command reference
reference-philosophy.md - Create vs Generate modes (read first)
reference-project.md - Full-PRD orchestration
reference-cr.md - Change request lifecycle
reference-reconcile.md - Drift detection and repair
reference-agentic-lessons.md - Production patterns for agentic execution
reference-outputs.md - Canonical completion cascades
reference-workflow-personas.md - Three Amigos consultation model
reference-repo-map.md - AST repo indexer design (v1.6.0)
reference-verify.md - Executable AC verifier DSL (v1.6.0)
reference-github-sync.md - GitHub Issues two-way sync (v1.6.0)
reference-scripts.md - Skill-internal scripts convention (v1.6.0)
reference-*.md - Domain-specific workflows
best-practices/ - Quality guidelines

Contributing

See CONTRIBUTING.md for guidelines.

Licence

MIT Licence - see LICENSE for details.

What is This?

The idea (for beginners)

New in v1.6.0

Prerequisites

Installation

Option 1: One-line installer (recommended)

Option 2: Install for a single project only

Option 3: Install a specific version

Option 4: Manual installation

Verify Installation

Quick Start

First time? Check the status

Don't know what to do next?

Starting a new project?

Have existing code?

Common Commands

Workflows

New Project (Greenfield)

Existing Project (Brownfield)

Agentic Epic Execution

Full-Project Execution

Change Requests

Reconcile Drift

Executable Acceptance Criteria (v1.6.0)

Repo Map for Agent Prompts (v1.6.0)

GitHub Issues Sync (v1.6.0)

Per-Project Lessons (v1.6.0)

Daily Development

Output Structure

Troubleshooting

"Command not found" when running /sdlc-studio

Installer fails to download

Commands run but nothing happens

Updating

Uninstalling

Global installation

Project-level installation

Getting Help

Documentation

Contributing

Licence

Yorumlar (0)