generating-constrained-specs

# Constrained Spec Generation

This skill generates PRD and architecture documents that are constrained by the decision ledger.

## Core Principle

**No spec section without a DEC-* reference.**

Every requirement, every architecture choice, must trace back to an explicit decision. This prevents:
- Ungrounded requirements
- Hidden assumptions
- Scope creep
- Orphaned features

## Prerequisites

- Decisions complete (`/ledger-decide`)
- `04-decisions/DECISIONS.yaml` exists
- `05-risks/RISKS.yaml` exists

## Workflow

Use TodoWrite to track these mandatory steps:

<required>
1. Load decisions and risks
2. Generate PRD with decision citations
3. Validate PRD constraint gate
4. Generate architecture with decision citations
5. Validate architecture constraint gate
6. Cross-reference risks in both documents
</required>

### Step 1: Load Decisions and Risks

Read:
- `04-decisions/DECISIONS.yaml` - All decisions
- `05-risks/RISKS.yaml` - All risks
- `03-synthesis/CROSS-SYNTHESIS.md` - Context

Build decision index for quick lookup.

### Step 2: Generate PRD

Write `06-prd/PRD.md` using template from [references/prd-template.md](references/prd-template.md).

**Constraint enforcement:**
Every section heading must include decision reference:
```markdown
## 2. Target Users (DEC-scope-power-users-first)
```

Every requirement must cite decisions:
```markdown
### 2.1 Primary Users
Power users within SMB organizations who manage complex workflows.
(DEC-scope-power-users-first, DEC-scope-smb-segment)
```

### Step 3: Validate PRD Constraint Gate

Check every PRD section:
- [ ] Section heading has DEC-* reference
- [ ] Requirements cite supporting decisions
- [ ] Risks are cross-referenced where relevant

**Gate failure:** If any section lacks DEC-* reference, cannot proceed.

### Step 4: Generate Architecture

Write `07-architecture/ARCHITECTURE.md` using template from [references/architecture-template.md](references/architecture-template.md).

**Constraint enforcement:**
```markdo