The Three Phases
Deep dive into Inception, Construction, and Operations
Overview
AI-DLC organizes development into three distinct phases, each with specialized agents and clear outputs.
Phase 1: Inception
Inception Agent
Captures intents, elaborates requirements, and decomposes work into manageable units.
Purpose
Transform high-level goals into well-defined, implementable work items.
Activities
Intent Capture
Gather the high-level goal: “User authentication system”
Requirement Elaboration
AI asks clarifying questions, generates user stories and NFRs
System Context
Define boundaries, interfaces, and constraints
Unit Decomposition
Break intent into loosely-coupled, independently developable units
Bolt Planning
Plan the bolts needed to implement each story
Key Outputs
| Artifact | Description |
|---|---|
requirements.md |
User stories, acceptance criteria, NFRs |
system-context.md |
Boundaries, interfaces, constraints |
units.md |
Unit definitions with dependencies |
| Bolt Plans | Ordered list of bolts per unit |
Phase 2: Construction
Construction Agent
Executes bolts through validated stages, producing tested, production-ready code.
Purpose
Transform specifications into working, tested code through disciplined stages.
Bolt Stages
Each bolt type progresses through validated stages:
For complex business logic and domain modeling:
1. Domain Model
Model the business logic using DDD principles:
- Identify aggregates, entities, value objects
- Define domain events and commands
- Establish ubiquitous language
2. Technical Design
Apply patterns and make architecture decisions:
- Choose implementation patterns
- Define interfaces and contracts
- Plan data structures
3. ADR Analysis (Optional)
Document significant architectural decisions:
- Context and problem statement
- Options considered
- Decision and rationale
- Consequences
4. Implement
Generate production code:
- Follow coding standards
- Apply design patterns
- Write clean, maintainable code
5. Test
Verify correctness:
- Unit tests for domain logic
- Integration tests for interfaces
- Acceptance tests for stories
For UI, integrations, and utilities:
1. Plan
Define what to build:
- Review stories and requirements
- List specific deliverables
- Identify dependencies
- Define acceptance criteria
2. Implement
Write the code:
- Setup file structure
- Implement core functionality
- Handle edge cases
- Add documentation
3. Test
Verify the implementation:
- Write unit tests
- Run test suite
- Verify acceptance criteria
- Document results
Human Checkpoints
Bolt Types
| Type | Best For | Stages |
|---|---|---|
| DDD Construction | Complex domain logic, business rules | Model → Design → ADR → Code → Test |
| Simple Construction | UI, integrations, utilities | Plan → Implement → Test |
Phase 3: Operations
Operations Agent
Deploys, verifies, and monitors the system in production.
Purpose
Take constructed features to production and ensure they run reliably.
Activities
Build
Compile, bundle, and prepare deployment artifacts
Deploy
Deploy to target environment (staging, production)
Verify
Run smoke tests, health checks, and validation
Monitor
Set up logging, metrics, and alerting
Key Outputs
| Artifact | Description |
|---|---|
| Deployment Units | Containerized or packaged applications |
| Runbooks | Operational procedures |
| Monitoring Config | Dashboards and alerts |
Phase Transitions
Inception → Construction
When moving from Inception to Construction:
- All units are defined with clear boundaries
- Stories have acceptance criteria
- Bolt plans are approved
- Dependencies are mapped
Construction → Operations
When moving from Construction to Operations:
- All bolts are completed and validated
- Tests are passing
- Code review is complete
- Documentation is updated
Master Agent Role
The Master Agent orchestrates across phases:
- Routing: Directs to the appropriate agent
- Context: Maintains awareness of project state
- Guidance: Helps navigate the methodology
- Standards: Enforces project conventions