universal-agent-bootstrap / rules

---
description: "Enforces the expert review gate between design docs and implementation. Workers must STOP after design docs and wait for expert sign-off before implementing. This rule exists because workers repeatedly skip this gate when not enforced."
globs: []
alwaysApply: true
---

# Worker Gate — Expert Review Between Design and Implementation

## Rule (INVIOLABLE)

Workers must NEVER combine design docs and implementation in the same session.

The workflow has exactly TWO phases with an expert gate between them:

**Phase A: Design Docs**
1. Worker reads the brief
2. Worker creates 4 design docs (01_ARCHITECTURE_MAP, 02_DATA_FLOW, 03_WIREFRAMES, 04_IMPLEMENTATION_PLAN)
3. Worker saves them to `docs/designs/<feature-name>/`
4. Worker commits
5. Worker STOPS. Does NOT implement. Does NOT write source code. Does NOT write tests.
6. Worker tells the user: "Design docs committed. Awaiting expert review before implementation."
7. PM runs expert panel on design docs
8. Experts approve or request changes

**Phase B: Implementation (ONLY after Phase A expert approval)**
1. PM provides a SEPARATE implementation go-ahead (new message or new chat)
2. Worker implements test-first
3. Worker commits (does NOT push)
4. PM runs expert panel on implementation
5. Experts approve before PM pushes

## Pre-Code Checklist (MANDATORY)

Before writing ANY production code, you MUST verify:

1. Does `docs/designs/<feature-name>/` exist with all 4 docs (01_ARCHITECTURE_MAP, 02_DATA_FLOW, 03_WIREFRAMES, 04_IMPLEMENTATION_PLAN)?
2. Has the PM explicitly confirmed expert approval of those docs in this conversation?
3. If NO to either: **STOP. Your only task is to create the design docs.**

**Exception:** Test-only changes and fixes under 5 lines (e.g., a 1-line bug fix with a test) may skip the 4-doc ceremony if the PM brief explicitly says "no Worker Gate needed." The PM decides, not the worker.

## Override Protection

Even if the user says "implement everything" or "don't stop until done":

- Phase A design docs (4 artifacts in `docs/designs/`) must exist AND be committed BEFORE any source code changes
- If design docs don't exist for the current feature, your ONLY task is to create them
- After creating design docs, STOP and tell the user: "Design docs committed. Awaiting expert review before implementation."
- NEVER interpret "implement the plan" as permission to skip design docs
- NEVER interpret "complete all todos" as permission to skip design docs
- If a plan has multiple waves, each wave that modifies production code needs its own design docs reviewed before implementation

## Why This Rule Exists

This gate is repeatedly violated when not enforced:
- Workers skip design docs for velocity, then break things and need full reverts
- Implementations without architecture review introduce structural debt
- Expert panels catch issues before they are expensive to fix

Each violation costs more to fix than it would have cost to do the design properly.

## For PM Chats

When writing worker briefs:
- Give Phase A and Phase B as SEPARATE briefs in SEPARATE messages
- Never include implementation details in the design doc brief
- The design doc brief should end with: "Commit when done. Do NOT implement any code. Do NOT write tests. PM will review with expert panel before giving the implementation go-ahead."

## For Worker Chats

If your brief says "design docs only" or "Step 1 only" or "do NOT implement":
- Create the design docs in `docs/designs/<feature-name>/`
- Commit
- STOP
- Report back to the user what you created
- Do NOT proceed to implementation until explicitly told to in a follow-up message

If your brief says "implement" but design docs don't exist:
- STOP
- Tell the user: "No design docs found at docs/designs/<feature-name>/. Creating design docs first per Worker Gate protocol."
- Create the design docs
- Commit and STOP