ADLC Workflow
Every task follows the same coordination pattern. No exceptions.
The Golden Rule
HITL/Manager → Product Owner → Cloud Architect → Specialist → Evidence
- You (HITL) give a directive
- Product Owner validates requirements and priority
- Cloud Architect designs technical approach
- Specialists execute (infra, QA, security, etc.)
- Evidence collected in
tmp/<project>/
Six-Phase Lifecycle
PLAN → BUILD → TEST → DEPLOY → MONITOR → OPERATE
[A] [A] [HITL] [HITL] [HITL] [HITL]
[A] = Autonomous [HITL] = Requires your approval
| Phase | You Do | Agents Do |
|---|---|---|
| Plan | Describe what you want | Decompose into stories, create ADRs |
| Build | Review progress | Write code, IaC, tests |
| Test | Approve test plan | Run Tier 1/2/3 tests |
| Deploy | Approve deployment | Execute terraform/cdk apply |
| Monitor | Review dashboards | Set up alerts, SLOs |
| Operate | Handle incidents | Create runbooks, playbooks |
Quick Start Examples
New Feature
You: "Add S3 bucket with encryption for audit logs"
↓
Product Owner validates requirements
↓
Cloud Architect designs (CDK vs Terraform, encryption type)
↓
Infrastructure Engineer implements
↓
QA Engineer tests (Tier 1 → 2 → 3)
↓
Evidence in tmp/<project>/
Using SpecKit Commands
# 1. Define the feature
/speckit.specify "Add encrypted S3 bucket for audit logs"
# 2. Plan the implementation
/speckit.plan
# 3. Generate tasks
/speckit.tasks
# 4. Execute all tasks
/speckit.implement
# 5. Reflect on the session
/speckit.retrospective
Infrastructure Deployment
# Terraform workflow
/terraform:test # Run all test tiers
/terraform:cost # Estimate costs
/terraform:diff # Check for breaking changes
# CDK workflow
/cdk:test # Run all test tiers
/cdk:synth # Validate synthesis
/cdk:diff # Check for breaking changes
Evidence Directory
Every action produces evidence:
tmp/<project>/
├── coordination-logs/ # PO + CA approval records
├── test-results/ # Tier 1/2/3 results
├── screenshots/ # Visual verification
├── terraform-plans/ # IaC plan outputs
└── retrospectives/ # Session reflections
Anti-Patterns to Avoid
| Don't | Do Instead |
|---|---|
| Skip PO + CA coordination | Always invoke both first |
| Claim "done" without evidence | Put artifacts in tmp/ |
| Describe what you'll do (NATO) | Show what you did |
| Deploy without testing | Run Tier 1 → 2 → 3 |
| Ignore session learnings | Run /speckit.retrospective |