phase-enforcement

Enforce phase gates and validate transitions across AI.D project stages.

9|2|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/ilandahan/AID --skill phase-enforcement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-enforcement
Source: https://github.com/ilandahan/AID/tree/main/.claude/skills/phase-enforcement
Command: npx skills add https://github.com/ilandahan/AID --skill phase-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces disciplined phase progression in AI.D projects, ensuring teams do not skip mandatory gates and that phase transitions are validated and auditable.

Core Features & Use Cases

  • Enforces Phase gates (PRD → Tech Spec → Implementation Plan → Development → QA) to maintain alignment with business goals.
  • Spawns mandatory Sub-Agent reviews at each phase transition to verify deliverables.
  • Collects feedback at phase end and stores it for continuous improvement and skill enhancements.
  • Provides override mechanisms with caution and proper logging when necessary.

Quick Start

Use this skill to verify the current phase, perform gate checks, and ensure prerequisites are met before starting work.

Frequently Asked Questions about phase-enforcement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce phase gates to prevent skipping stages in project workflows?

Phase gates enforce sequential progression across PRD, Tech Spec, Implementation Plan, Development, and QA stages. This prevents out-of-sequence work by validating phase transitions, checking prerequisites, and ensuring alignment with business goals before advancing.

What is the best way to validate deliverables before a phase transition?

Validating deliverables before a phase transition is handled by spawning mandatory sub-agent reviews. These sub-agents verify the completed work against phase requirements, ensuring prerequisites are met and documentation is approved.

How do I collect and store phase feedback for continuous workflow improvement?

Phase feedback is collected at the end of each phase and stored directly in the ~/.aid/feedback/pending/ directory. This records transition validation data to support continuous process improvement and future skill enhancements.

Can I override phase enforcement when skipping a gate is necessary?

Override mechanisms are available for phase enforcement when necessary, but they require caution. Using an override properly logs the transition to maintain an auditable record, ensuring the workflow remains documented despite skipping standard gates.

When do I need sub-agent reviews in a gated development cycle?

Sub-agent reviews are needed at every phase transition within a gated development cycle. They verify deliverables, validate that prerequisites are met, and ensure work does not advance out of sequence before moving to the next stage.