Phase 2 Playbook — Foundation & Scaffolding
Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector
Objective
Build the technical and operational foundation that all subsequent work depends on. Get the skeleton standing before adding muscle. After this phase, every developer has a working environment, a deployable pipeline, and a design system to build with.Pre-Conditions
Workstreams
Workstream A: Infrastructure (Day 1-3, Parallel)
DevOps Automator
CI/CD Pipeline + Infrastructure
- CI/CD Pipeline (GitHub Actions/GitLab CI)
- Security scanning
- Automated testing
- Build and containerization
- Blue-green deployment
- Automated rollback
- Infrastructure as Code
- Environment provisioning
- Secrets management
Infrastructure Maintainer
Monitoring & Cloud Setup
- Cloud resource provisioning
- Auto-scaling configuration
- Load balancer setup
- Monitoring stack (Prometheus/DataDog)
- Custom dashboards (Grafana)
- Centralized logging
- Alert rules
- Security hardening
Studio Operations
Process Setup
- Git workflow (branch strategy)
- PR review process
- Merge policies
- Communication channels
- Documentation templates
- Collaboration tools
- Project board setup
Workstream B: Application Foundation (Day 1-4, Parallel)
- Frontend Developer
- Backend Architect
- UX Architect
Project ScaffoldingDeliverables:
- Framework setup (React/Vue/Angular)
- TypeScript configuration
- Build tooling (Vite/Webpack/Next.js)
- Testing framework (Jest/Vitest + Testing Library)
- Design system implementation
- Base component library (Button, Input, Card, Layout)
- Theme system (light/dark/system)
- Application shell (routing, layouts, error boundaries)
Verification Checkpoint (Day 4-5)
Evidence Collector Verification
Evidence Collector Verification
Verify with screenshot evidence:
Verdict: PASS / FAIL with specific issues
- ✅ CI/CD pipeline executes successfully (show pipeline logs)
- ✅ Application skeleton loads in browser (desktop screenshot)
- ✅ Application skeleton loads on mobile (mobile screenshot)
- ✅ Theme toggle works (light + dark screenshots)
- ✅ API health check responds (curl output)
- ✅ Database is accessible (migration status)
- ✅ Monitoring dashboards are active (dashboard screenshot)
- ✅ Component library renders (component demo page)
Verdict: PASS / FAIL with specific issues
Quality Gate Checklist
| # | Criterion | Evidence Source | Status |
|---|---|---|---|
| 1 | CI/CD pipeline builds, tests, deploys | Pipeline execution logs | ☐ |
| 2 | Database schema deployed | Migration success output | ☐ |
| 3 | API scaffold responding | curl response evidence | ☐ |
| 4 | Frontend skeleton renders | Evidence Collector screenshots | ☐ |
| 5 | Monitoring dashboards active | Dashboard screenshots | ☐ |
| 6 | Design system tokens implemented | Component library demo | ☐ |
| 7 | Theme toggle functional | Before/after screenshots | ☐ |
| 8 | Git workflow documented | Studio Operations playbook | ☐ |
Gate Decision
- PASS
- FAIL
Proceed to Phase 3Working skeleton with full DevOps pipelineDual sign-off: DevOps Automator (infrastructure) + Evidence Collector (visual)
Handoff to Phase 3
Phase 2 → Phase 3 Handoff Package
Phase 2 → Phase 3 Handoff Package
For all Developer Agents:
- Working CI/CD pipeline (auto-deploys on merge)
- Design system tokens and component library
- API scaffold with auth and health checks
- Database with schema and seed data
- Git workflow and PR process
- Application URLs (dev, staging)
- Screenshot capture methodology
- Component library reference
- Brand guidelines for visual verification
- Sprint Prioritizer backlog (from Phase 1)
- Task list with acceptance criteria (from Phase 1)
- Agent assignment matrix (from NEXUS strategy)
- Quality thresholds for each task type
- Dev environment: [URL]
- Staging environment: [URL]
- Monitoring dashboard: [URL]
- CI/CD pipeline: [URL]
- API documentation: [URL]
Phase 2 is complete when the skeleton application is running, the CI/CD pipeline is operational, and the Evidence Collector has verified all foundation elements with screenshots.