Menu
AID methodology phase gate enforcement. Ensures work follows correct phase order (PRD -> Tech Spec -> Impl Plan -> Dev -> QA). Enforces gates, validates transitions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.
AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.
AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.
| name | phase-enforcement |
| description | AID methodology phase gate enforcement. Ensures work follows correct phase order (PRD -> Tech Spec -> Impl Plan -> Dev -> QA). Enforces gates, validates transitions. |
Claude MUST check current phase before any work, REFUSE work that belongs to later phase.
Before any work:
.aid/state.json for current phaseBefore Phase N -> N+1:
| Phase | Name | Document | Folder |
|---|---|---|---|
| 1 | PRD | Product Requirements | docs/prd/ |
| 2 | Tech Spec | Technical Specification | docs/tech-spec/ |
| 3 | Impl Plan | Task Breakdown | docs/implementation-plan/ |
| 4 | Development | Code & Tests | src/ |
| 5 | QA & Ship | Deployment | Production |
| Category | Examples | First Allowed |
|---|---|---|
| requirements | PRD, user stories | Phase 1 |
| architecture | System design, APIs | Phase 2 |
| planning | Jira, task breakdown | Phase 3 |
| coding | Components, tests | Phase 4 |
| qa | Testing, deployment | Phase 5 |
PHASE GATE VIOLATION
Current Phase: [N] [Name]
Requested: [What]
Category: [Category]
This work belongs to Phase [X].
Complete first: [List]
Commands: /phase, /gate-check, /aid end
Phase 3 Golden Rules:
Sub-Phases: 3a Consolidation → 3b Breakdown → 3c Enrichment → 3d Jira → 3e Verification
Checklist:
Always Allowed: Reading files, documentation updates, questions, /phase, /gate-check
Override: User says "override: [reason]" - logged to .aid/overrides.log
.aid/state.json:
{
"current_phase": 2,
"phase_name": "tech-spec",
"feature_name": "user-auth",
"phases_completed": [1],
"subagent_review": {"phase_1": {"status": "passed"}}
}