Zygen SDLC Extension

Stage-gated SDLC orchestration for Cursor AI. Track tickets from intake to closure with automated gates and minimal friction.

What You Get

• Per-ticket trackers (docs/sdlc/<TICKET>.md) as single source of truth
• Wizard UI to collect missing inputs at any SDLC stage
• Cursor command (/sdlc <TICKET>) that orchestrates progression
• Gate enforcement (PRD → ADR/TRD → Test Plan → Code → Review → Merge)
• WIP lock prevents starting new tickets while one is active
• Flexible entry/exit — enter at any stage, exit at logical gates

Quick Start

1. Install

The extension auto-installs the kit when you open a workspace. Or run:

SDLC: Install Kit

This creates:

• .cursor/commands/sdlc.md — The /sdlc orchestrator command
• docs/sdlc/TICKET_TEMPLATE.md — Tracker template
• docs/sdlc/README.md — Usage guide

2. Start a Ticket

SDLC: Start Ticket (Wizard)

The wizard asks only missing, blocking inputs for the current stage:

• Intake: Ticket ID, owner, title, goal, AC, mode
• PRD: PRD file path or requirements
• Plan: ADR/TRD document
• TestPlan: Test plan details
• InDev+: No wizard questions (use /sdlc command)

3. Run in Cursor Chat

After wizard completes, a prompt is copied to clipboard. Paste it into Cursor chat:

/sdlc JIRA-123 Read docs/sdlc/JIRA-123.md and run

The /sdlc command will:

• Read tracker state
• Enforce gates for current stage
• Generate artifacts (PRD, ADR, code, tests)
• Ask 1-3 blocking questions if needed
• Update tracker after each iteration
• Output one next action

4. Resume Existing Ticket

SDLC: Resume Ticket

Select a ticket to continue. Prompt copied to clipboard.

How It Works

Stage Flow

Intake → PRD → Plan → TestPlan → InDev → InReview → InPR → Done
                                                          ↘ Blocked
                                                          ↘ Split
                                                          ↘ DeScoped
                                                          ↘ WontDo

Entry Points

• Intake: New ticket (wizard collects: ticket, owner, goal, AC, mode)
• PRD: Product owner enters (wizard asks: PRD file/requirements)
• Plan: Architect enters (wizard asks: ADR/TRD document)
• TestPlan: QA enters (wizard asks: test plan)
• InDev+: Developer enters (no wizard, use /sdlc directly)

Exit Points

• After PRD: PO can exit (Gate A approval)
• After ADR/TRD: Architect can exit (Gate B approval)
• After TestPlan: QA can exit (Gate C approval)
• InDev/InPR: Dev can exit (with mode override if no tests)
• Done: Requires PR link OR explicit override

Gate Approvals

Approve/reject gates with simple commands in Cursor chat:

• a or approve — approve current gate
• r or reject — reject with reason

Commands

Screenshots

Features

Stage-Aware Wizard

Wizard only asks questions required for the current stage:

• If starting at PRD stage → asks for PRD file/requirements only
• If starting at Plan stage → asks for ADR/TRD only
• No assumptions, no non-blocking questions

Minimal Clipboard Prompt

After wizard, clipboard contains:

/sdlc JIRA-123 Read docs/sdlc/JIRA-123.md and run

All intelligence lives in .cursor/commands/sdlc.md, not the prompt.

WIP Lock

If you have an active ticket (InDev/InReview/InPR), starting a new ticket is blocked. Options:

• Open active ticket
• Transfer ownership
• Terminalize active ticket

Flexible Terminalization

Close tickets with:

• Done: Requires PR link (or override)
• Blocked: External dependency
• Split: Ticket split into smaller ones
• DeScoped: Removed from scope
• WontDo: Decided not to implement

Requirements

• VS Code or Cursor
• Node.js 18+ (for development)
• Git repository (for auto-install detection)

Configuration

Set in VS Code settings:

• sdlc.autoInstallKit (default: true) — Auto-install kit on workspace open

Support

• Issues: GitHub Issues
• Documentation: See docs/sdlc/README.md after installation

Built for developers who want surgical, deterministic SDLC orchestration without noise.