SDD State Management

This skill covers how SDD tracks change set state and enforces phase gates.

State File

Every change set has a state file at changes/<name>/state.md:

# SDD State: <name>

## Lane

<full|vibe|bug>

## Phase

<current-phase>

## Phase Status

in_progress | complete

## Pending

<only unresolved items>

## Notes

<freeform - decisions, progress, context - cleared when phase complete>

Lanes Overview

Full Lane

The complete SDD experience. Specs are written before implementation.

Phases

ideation -> proposal -> specs -> discovery -> tasks -> plan -> implement -> reconcile -> finish

Phase Gates

Vibe Lane

Freedom to explore. Skip specs, get to building fast.

Flow

/sdd/fast/vibe <context>  →  /sdd/plan  →  /sdd/implement  →  [/sdd/reconcile  →  /sdd/finish]

Artifacts

Optional Completion

Reconcile and finish are optional:

• Throwing it away: Stop after implement
• Keeping it: Reconcile captures specs from implementation, finish syncs to canonical

Bug Lane

Hunt and fix. Triages the issue first.

Flow

/sdd/fast/bug <context>  →  /sdd/plan  →  /sdd/implement  →  [/sdd/reconcile  →  /sdd/finish]

Triage

The bug command determines if this is:

• Actual bug: Implementation doesn't match intent → proceed with bug lane
• Behavioral change: User wants different behavior → redirect to full lane with specs

Artifacts

Optional Completion

Reconcile and finish are optional:

• No spec impact: Stop after implement (most bug fixes)
• Specs affected: Reconcile captures changes, finish syncs

Thoughts Directory

For complex investigations, use thoughts/ as a free-form workspace:

changes/<name>/
  thoughts/
    investigation.md
    options.md

Purpose: Document thinking so users can continue in a new chat with full context.

Pending Semantics

## Pending is a ledger of unresolved items:

• Contains only unresolved items (blockers, decisions needed)
• Remove items when resolved (don't strike through)
• Leave it blank when nothing is pending
• Deferred ideas go elsewhere (e.g., docs/future-capabilities.md)

## Pending is NOT an approval log. Do not record approvals there.

Flexible Phase Management

Phase transitions are guided but not rigid. Users can skip phases or jump ahead if needed.

Core Principles

• Flexible flow: The phase sequence is a guide, not a strict process. Users can skip phases or jump ahead.
• User intent first: When users run a command, assume they know what they're doing. Provide guidance but don't block.
• Smart but not controlling: Suggest the right path, warn about skipped phases, confirm major jumps, but ultimately follow the user's lead.

Entry Check Logic

When a command is invoked, check the current state and handle appropriately:

1. Natural progression (previous phase is complete):

   • Update state.md: ## Phase → current command's phase, ## Phase Status: in_progress
   • Proceed with command

2. Jumping forward across multiple phases:

   • Show: "Skipping over [phase1, phase2] - are you sure?"
   • If confirmed: Update state.md to this phase, set ## Phase Status: in_progress

3. Going back to a previous phase:

   • Show: "Moving back to [phase] - this will reset its status to in_progress"
   • If confirmed: Update state.md to that phase, set ## Phase Status: in_progress

4. Same phase already complete:

   • Show: "This phase is complete - do you want to re-enter it?"
   • If confirmed: Set ## Phase Status: in_progress

5. Same phase in_progress or first run:

   • Continue with command (natural continuation)

Command Completion

When a command completes (user approves work):

• Set ## Phase Status: complete
• Clear ## Notes to empty string
• Do NOT advance to next phase - next command will handle that

Keeping Notes Updated

During command execution, keep ## Notes updated with:

• Decisions made
• Current progress
• Context about where we are
• Blockers or issues encountered

Notes are meant to capture state so work can be resumed later or in a new chat. They should be concise but informative.