Gate

Files (1)

• SKILL.md

SKILL.md (first lines)

# Gate Skill

Control phase transitions and approvals in the SDLC workflow.

## Automated validators (v0.15.0+)

Every `/gate check` and `/gate approve` now runs the Wave 3 validator suite via:

```bash
./scripts/validators/validate-phase-gate.sh <phase>
```

Phase arguments:

| Invocation | Phase arg |
|------------|-----------|
| Mode 1 phase N | `phase-<N>` (0-5) |
| Mode 2 deep | `onboard-deep` |
| `/security --deep` | `security-deep` |

Exit codes:
- `0` = all validators clean, gate passes
- `1` = one or more gaps (read JSON gap list on stdout)
- `2` = validator itself errored

The validator replaces subjective "read the file, rate completeness 1-10" with deterministic coverage checks (`scripts/validators/validate-architecture.sh`, `validate-owasp.sh`, `validate-api-coverage.sh`, `validate-erd-coverage.sh`, `validate-sequence-coverage.sh`, `validate-inventory.sh`).

Do not second-guess the validator. If it says clean, gate passes. If it says gap, close the gap -- do not override.

See `scripts/validators/README.md` for the full validator contract.

---

## Legacy confidence-loop flow (still used for unvalidatable artifacts)

For artifacts validators cannot check mechanically (narratives, research summaries), the legacy confidence-loop flow below remains in effect.

## Memory Integration

Gate decisions are critical project history. All approvals and bypasses are stored in memory for:
- **Audit trail** - Why was Phase 2 approved?
- **Cross-session context** - Recall gate history after compaction
- **Decision recovery** - What was the bypass reason?

### On Gate Approval

```
memory_store({
  content: "GATE APPROVED: Phase [N] ([Phase Name]). Documents validated: [list]. Approved by: @user",
  type: "decision",
  confidence: 1.0,
  citation: "docs/[phase-folder]/"
})
```

### On Gate Bypass

```
memory_store({
  content: "GATE BYPASS: Phase [N] bypassed. Reason: [reason]. Missing docs: [list]. Action required: [backfill plan]",
  type: "decision",
  confidence: 0.7
})
```

### On Task Verification

```
memory_store({
  content: "TASK VERIFIED: [TASK-XXX] at [confidence]% confidence. Issues: [if any]",
  type: "fact",
  confidence: 0.9,
  citation: "[primary deliverable file]"
})
```

---

## Commands

### `/gate check [--phase N]`

Check if a phase gate is satisfied.

**Examples:**
```
/gate check           # Check current phase
/gate check --phase 2 # Check specific phase
```

**Gate Requirements by Phase:**

| Phase | Requirements |
|-------|-------------|
| 0 | None (starting point) |
| 1 | Phase 0 documents exist and are approved |
| 2 | Phase 1 documents exist and are approved |
| 3 | Phase 2 documents exist and are approved |
| 4 | Phase 3 documents exist and are approved |

**Output (satisfied):**
```
Gate Check: Phase 2

Prerequisites (Phase 1):
  SCOPE.md exists (44 lines)
  RISKS.md exists (50 lines)
  CONSTRAINTS.md exists (26 lines)
  USER_PERSONAS.md exists (78 lines)
  Phase 1 approved on 2026-01-08

Gate Status: OPEN

Ready to run: /sdlc run --phase 2
```

**Output (not satisfied):**
```
Gate Check: Phase 2

From bpmforge/attest-claude, Apache-2.0.

More from bpmforge/attest-claude