AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AID methodology phase gate enforcement. Ensures work follows correct 6-phase order (Discovery -> PRD -> Tech Spec -> Impl Plan -> Dev -> QA & Ship). Enforces gates, validates transitions. Use before any work to check the current phase and refuse work belonging to a later phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Check current phase before any work. REFUSE work that belongs to a later phase.
Always Allowed: Reading files, documentation updates, questions, /phase, /gate-check
Override: User says "override: [reason]" - logged to .aid/overrides.log
Before any work:
.aid/state.json for current phase.aid/context.json for current task and stepBefore Phase N -> N+1:
Task(
subagent_type: "general-purpose",
model: "opus",
prompt: [Read ../../agents/phase-review-agent.md, replace {{PHASE_NUMBER}}, {{PHASE_NAME}}, {{PHASE_CHECKLIST}}, {{DELIVERABLES}}],
description: "Phase gate validation"
)
| Variable | Source | How to Extract |
|---|---|---|
{{PHASE_NUMBER}} | .aid/state.json | Read current_phase field |
{{PHASE_NAME}} | .aid/state.json | Read phase_name field |
{{PHASE_CHECKLIST}} | Gate Check Requirements (below) | Use the checklist for the current phase transition |
{{DELIVERABLES}} | Phase output folders | Read all files from the phase's output folder (e.g., docs/research/ for Phase 0, docs/prd/ for Phase 1) |
| Phase | Name | Document | Folder |
|---|---|---|---|
| 0 | Discovery | Research & Validation | docs/research/ |
| 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 |
|---|---|---|
| research | Stakeholders, competitive analysis, discovery | Phase 0 |
| requirements | PRD, user stories, acceptance criteria | Phase 1 |
| architecture | System design, APIs, schemas | Phase 2 |
| planning | Jira, task breakdown, consolidation | Phase 3 |
| coding | Components, tests, implementation | Phase 4 |
| qa | Testing, deployment, release | Phase 5 |
| Phase | Allowed | Blocked |
|---|---|---|
| 0 Discovery | research | requirements, architecture, planning, coding, qa |
| 1 PRD | research, requirements | architecture, planning, coding, qa |
| 2 Tech Spec | research, requirements, architecture | planning, coding, qa |
| 3 Impl Plan | research, requirements, architecture, planning | coding, qa |
| 4 Development | research, requirements, architecture, planning, coding | qa |
| 5 QA & Ship | all | - |
| Phase | Core WHY Question |
|---|---|
| 0 Discovery | "WHY is this problem worth solving?" |
| 1 PRD | "WHY does the user need this?" |
| 2 Tech Spec | "WHY this architecture?" |
| 3a Consolidation | "WHY does this contradiction exist? WHY this resolution?" |
| 3b Breakdown | "WHY this task size? WHY these dependencies?" |
| 3c Jira Population | "WHY is this information complete? WHY can dev work from this alone?" |
| 4 Development | "WHY this code? WHY these connections?" |
| 5 QA & Ship | "WHY is this test? WHY is this ready?" |
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:
Read both before enforcing gates: state.json determines the phase, context.json provides task-level awareness.
.aid/state.json
{
"current_phase": 2,
"phase_name": "tech-spec",
"feature_name": "user-auth",
"phases_completed": [0, 1],
"subagent_review": {"phase_0": {"status": "passed"}, "phase_1": {"status": "passed"}}
}
.aid/context.json
{
"current_task": "Design authentication API",
"current_step": "Define API contracts",
"progress": "in-progress",
"last_updated": "2024-12-21T10:00:00Z"
}
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.