Phase Enforcement Skill

Claude MUST check current phase before any work, REFUSE work that belongs to later phase.

Priority 1: Phase Gate Enforcement

Before any work:

1. Read .aid/state.json for current phase
2. Classify the requested work
3. Check if work is allowed
4. REFUSE if not allowed (show violation)
5. At phase completion: mandatory sub-agent review
6. After review passes: collect feedback via /aid end

Mandatory: Sub-Agent Review at Transitions

Before Phase N -> N+1:

1. Claude spawns review sub-agent
2. Sub-agent reviews all deliverables
3. Returns PASS/FAIL with findings
4. FAIL: Address issues, retry
5. PASS: Proceed to feedback

5-Phase Development Lifecycle

Work Classification

Phase Permissions

Phase 1: [requirements]
Phase 2: [requirements, architecture]
Phase 3: [requirements, architecture, planning]
Phase 4: [requirements, architecture, planning, coding]
Phase 5: [all]

Gate Check Requirements

Phase 1 -> 2

• PRD exists in docs/prd/
• User stories defined
• Acceptance criteria complete
• Sub-agent review PASSED
• Feedback collected

Phase 2 -> 3

• Tech Spec exists
• Architecture diagram
• API contracts
• Security assessment
• Sub-agent review PASSED

Phase 3 -> 4

• Implementation Plan exists
• Tasks broken down
• Dependencies identified
• Test strategy defined
• Sub-agent review PASSED

Phase 4 -> 5

• Code implemented
• Tests passing
• Coverage meets threshold
• Sub-agent review PASSED

Violation Template

PHASE GATE VIOLATION

Current Phase: [N] [Name]
Requested: [What]
Category: [Category]

This work belongs to Phase [X].

Complete these first:
[List incomplete phases]

Commands:
  /phase      - See status
  /gate-check - See requirements
  /aid end    - Complete with feedback

Sub-Agent Review Prompts

PRD Review (Phase 1 -> 2)

Checklist - ALL must pass:
[ ] Problem statement clear
[ ] User stories As/I want/So that format
[ ] Acceptance criteria for each story
[ ] Non-functional requirements
[ ] Success metrics measurable
[ ] Scope boundaries explicit
[ ] No implementation details

Tech Spec Review (Phase 2 -> 3)

Checklist:
[ ] Architecture diagram
[ ] Components defined
[ ] Data models with TypeScript
[ ] API contracts
[ ] Database schema
[ ] Security assessment
[ ] Error handling strategy
[ ] References PRD

Impl Plan Review (Phase 3 -> 4)

Checklist:
[ ] Tasks < 4 hours each
[ ] Acceptance criteria per task
[ ] Dependencies identified
[ ] Ordered by dependency
[ ] Test strategy defined
[ ] Coverage target (70%)
[ ] Step-by-step order explicit

Development Review (Phase 4 -> 5)

Checklist:
[ ] All tasks complete
[ ] Tests passing
[ ] Coverage >= 70%
[ ] Lint passes
[ ] Build succeeds
[ ] No critical vulnerabilities
[ ] Documentation updated

Exceptions

Always Allowed

• Reading files
• Documentation updates
• Answering questions
• /phase, /gate-check, /aid end

Override

• User says "override: [reason]"
• Log in .aid/overrides.log
• Does NOT skip sub-agent review for critical failures

State File: .aid/state.json

{
  "current_phase": 2,
  "phase_name": "tech-spec",
  "feature_name": "user-auth",
  "phases_completed": [1],
  "documents": {
    "prd": "docs/prd/2024-12-11-user-auth.md"
  },
  "subagent_review": {
    "phase_1": {"status": "passed"}
  }
}