SDLC Setup

Initialize the SDLC workflow for this project. This command:

1. Checks for required tools (gh CLI, git-spice)
2. Installs required GitHub CLI extensions
3. Creates .claude/sdlc.yaml configuration through interactive prompts

Steps

1. Check Prerequisites

# Check gh CLI
gh --version

# Check authentication
gh auth status

# Check for project scope (needed for GitHub Projects)
gh auth status 2>&1 | grep -i "project"

If gh CLI is not installed, direct user to https://cli.github.com/

If not authenticated, direct user to run gh auth login

If project scope is missing, inform user to run:

gh auth refresh -s project

2. Check/Install GitHub CLI Extensions

Check and install each required extension:

# gh-issue-ext for sub-issues, blocking, linked branches
gh extension list | grep -q "gh-issue-ext" || gh extension install jwilger/gh-issue-ext

# gh-project-ext for project board management
gh extension list | grep -q "gh-project-ext" || gh extension install jwilger/gh-project-ext

# gh-pr-review for PR review comment handling (reply, resolve threads)
gh extension list | grep -q "gh-pr-review" || gh extension install agynio/gh-pr-review

If extensions are already installed, offer to upgrade:

gh extension upgrade jwilger/gh-issue-ext
gh extension upgrade jwilger/gh-project-ext
gh extension upgrade agynio/gh-pr-review

3. Check for git-spice (optional)

command -v gs

If git-spice is available, note it for the config options.

4. Interactive Configuration

Use AskUserQuestion to gather project preferences:

Question 1: Development Mode

• Event Modeling (application development with workflows, slices, GWT)
• Traditional (PRD, architecture, feature/subtask breakdown)

Question 2: Git Workflow

• git-spice (stacked PRs) - only if git-spice is installed
• Standard (single branch per feature)

Question 3: GitHub Project

• Link to existing project (ask for project number/URL)
• Create new project
• No project board

Question 4: TDD Verbosity

• Silent (just use agents, no explanation)
• Brief (one-line notes about what's happening)
• Explain (full context about agent delegation)

5. Create Configuration

Create .claude/sdlc.yaml with the gathered settings:

# SDLC Configuration
# Generated by /sdlc:setup

mode: event-modeling  # or: traditional

git:
  workflow: git-spice  # or: standard
  require_clean: true

github:
  project: 11  # project number, or null if not using projects
  owner: jwilger  # project owner

board:
  statuses:
    - Backlog
    - Ready
    - In Progress
    - Review
    - Done

tdd:
  verbosity: brief  # silent | brief | explain
  bypass_patterns:
    # Documentation
    - "*.md"
    - "*.txt"
    - "*.rst"
    # Infrastructure
    - ".github/**"
    - "*.tf"
    - "*.tfvars"
    - "*.hcl"
    # Configuration
    - "Cargo.toml"
    - "package.json"
    - "pyproject.toml"
    - "*.yaml"
    - "*.yml"
    - "*.toml"
    - "*.json"
    # Build/tooling
    - "Makefile"
    - "Dockerfile"
    - "docker-compose*.yml"

Ensure .claude/ directory exists:

mkdir -p .claude

6. Initialize Event Model Docs (if applicable)

If mode is event-modeling, ask if user wants to create the docs structure:

mkdir -p docs/event_model/{workflows,scenarios}

Create template files if requested.

7. Display Success

Show summary of what was configured and next steps:

SDLC initialized successfully!

Configuration: .claude/sdlc.yaml
Mode: Event Modeling
Git Workflow: git-spice
GitHub Project: #11

Installed Extensions:
  - gh-issue-ext (sub-issues, blocking, branches)
  - gh-project-ext (project board management)
  - gh-pr-review (PR review comment handling)

Next steps:
  - /sdlc:work - Start working on an issue
  - /sdlc:design - Design event model workflows
  - Ask "what issues are ready?" to see available work

Auto-approval patterns to add to Claude settings:
  Bash(gh issue:*)
  Bash(gh issue-ext:*)
  Bash(gh project:*)
  Bash(gh project-ext:*)
  Bash(gh pr-review:*)
  Bash(gs:*)  # if using git-spice