본문으로 건너뛰기
cccskills
무료GitHub에 공개

phase-enforcement

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구Jira
설치 방법 보기

포함된 파일(5)

  • SKILL.md7.0 KB
  • references/phase-gates.md25.5 KB
  • references/quality-feedback.md15.4 KB
  • references/skill-integration.md28.3 KB
  • SKILL.extended.md18.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Phase Enforcement

Check current phase before any work. REFUSE work that belongs to a later phase.

Exceptions (skill does not block these)

Always Allowed: Reading files, documentation updates, questions, /phase, /gate-check

Override: User says "override: [reason]" - logged to .aid/overrides.log

Priority 1: Phase Gate Enforcement

Before any work:

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

Mandatory: Sub-Agent Review at Transitions

Before Phase N -> N+1:

  1. Spawn the phase-review-agent using the Task tool:
    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"
    )
    
  2. Sub-agent reviews all deliverables
  3. Returns PASS/FAIL with findings
  4. FAIL: Address issues, retry
  5. PASS: Proceed to feedback

Variable Extraction

VariableSourceHow to Extract
{{PHASE_NUMBER}}.aid/state.jsonRead current_phase field
{{PHASE_NAME}}.aid/state.jsonRead phase_name field
{{PHASE_CHECKLIST}}Gate Check Requirements (below)Use the checklist for the current phase transition
{{DELIVERABLES}}Phase output foldersRead all files from the phase's output folder (e.g., docs/research/ for Phase 0, docs/prd/ for Phase 1)

6-Phase Development Lifecycle

PhaseNameDocumentFolder
0DiscoveryResearch & Validationdocs/research/
1PRDProduct Requirementsdocs/prd/
2Tech SpecTechnical Specificationdocs/tech-spec/
3Impl PlanTask Breakdowndocs/implementation-plan/
4DevelopmentCode & Testssrc/
5QA & ShipDeploymentProduction

Work Classification

CategoryExamplesFirst Allowed
researchStakeholders, competitive analysis, discoveryPhase 0
requirementsPRD, user stories, acceptance criteriaPhase 1
architectureSystem design, APIs, schemasPhase 2
planningJira, task breakdown, consolidationPhase 3
codingComponents, tests, implementationPhase 4
qaTesting, deployment, releasePhase 5

Phase Permissions

PhaseAllowedBlocked
0 Discoveryresearchrequirements, architecture, planning, coding, qa
1 PRDresearch, requirementsarchitecture, planning, coding, qa
2 Tech Specresearch, requirements, architectureplanning, coding, qa
3 Impl Planresearch, requirements, architecture, planningcoding, qa
4 Developmentresearch, requirements, architecture, planning, codingqa
5 QA & Shipall-

Phase-Specific WHY Questions

PhaseCore 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?"

Gate Check Requirements

Phase 0 -> 1

  • Research folder exists in docs/research/
  • Research report with problem statement (SCQ format)
  • Stakeholders identified and mapped
  • Competitive analysis documented
  • Traceability matrix created
  • Go/No-Go decision documented
  • Sub-agent review PASSED

Phase 1 -> 2

  • PRD exists in docs/prd/
  • User stories defined
  • Acceptance criteria complete
  • Requirements linked to research IDs (RES-XXX)
  • Sub-agent review PASSED

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 first: [List]

Commands: /phase, /gate-check, /aid end

Sub-Agent Review Prompts

Discovery Review (Phase 0 -> 1)

  • Problem statement clear (SCQ format)
  • Stakeholders identified
  • Competitive analysis documented
  • Traceability matrix created
  • Go/No-Go decision with justification
  • No implementation details

PRD Review (Phase 1 -> 2)

  • Problem statement clear
  • User stories As/I want/So that
  • Acceptance criteria per story
  • Non-functional requirements
  • Measurable success metrics
  • No implementation details

Tech Spec Review (Phase 2 -> 3)

  • Architecture diagram
  • Components defined
  • Data models (TypeScript)
  • API contracts
  • Database schema
  • Security assessment
  • References PRD

Impl Plan Review (Phase 3 -> 4)

Phase 3 Golden Rules:

  1. NO WORD LEFT BEHIND - PRD → Epic/Story, Tech Spec → Task
  2. SMALL TASKS - Larger docs = smaller tasks
  3. PROCESS IN CHUNKS - Read → Write immediately
  4. VERIFY - 100% coverage required

Sub-Phases: 3a Consolidation → 3b Breakdown → 3c Enrichment → 3d Jira → 3e Verification

Checklist:

  • Contradiction log created
  • Source documents fixed
  • Consolidated spec created
  • Hierarchy: Epic → Story → Task
  • Tasks sized appropriately
  • All 8 required fields per Task
  • 100% PRD/Tech Spec coverage
  • Enriched files staged
  • Jira populated with ADF

Development Review (Phase 4 -> 5)

  • All tasks complete
  • Tests passing
  • Coverage >= 70%
  • Lint passes
  • Build succeeds
  • No critical vulnerabilities

State Files

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"
}

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ilandahan/AID102026년 9월 23일 업데이트

AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ilandahan/AID102026년 9월 23일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ilandahan/AID102026년 9월 23일 업데이트

aid-prd

무료

AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ilandahan/AID102026년 9월 23일 업데이트

AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ilandahan/AID102026년 9월 23일 업데이트

AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ilandahan/AID102026년 9월 23일 업데이트

ilandahan의 스킬 모두 보기

이 스킬의 문제 신고