LaunchOS Project Lifecycle

Complete end-to-end product development pipeline — from vision to verified deployment

Program & Project Kickoff Reference

Workshop-Driven Engagement Pipeline

0
Program
Kick-Off
App mode only
1
Required
Vision
Mandatory gate
2
Optional
UX Research
Full process
3
Optional
Architecture
Full process
4
Optional
Story Map
Full process
5
Required
Design
Both paths
6
Gate
Write Tests
3 quality gates
7
Automated
Build
Robo Builder
8
Automated
Test
Robo Test
9
Verified
Deploy
Robo Deploy

Lifecycle Phases

Each phase produces deliverables that feed the next — nothing proceeds without quality verification

W1 Vision & Discovery REQUIRED
  • Business problem definition
  • User persona identification
  • Product vision statement
  • Success criteria & OKRs
  • Scope boundaries
  • Stakeholder mapping
▸
W2 UX Research OPTIONAL
  • Journey mapping
  • Empathy maps
  • Service blueprints
  • Touchpoint analysis
  • UX principles
  • Usability strategy
▸
W3 Architecture OPTIONAL
  • Tech stack decisions (ADRs)
  • System design (C4 model)
  • Data model design
  • Integration architecture
  • NFRs defined
  • Security architecture
▸
W4 Story Mapping OPTIONAL
  • Story map backbone
  • Walking skeleton
  • Release slicing
  • Epic breakdown
  • Prioritization (MoSCoW/RICE)
  • Sprint planning
▸
W5 Design REQUIRED
  • Design specifications
  • Wireframes & mockups
  • Interaction specs
  • Stories refined
  • Acceptance criteria
  • Backfill if skipped W2-W4
▸
G Quality Gates MANDATORY
  • Story unit tests written
  • Capability E2E tests written
  • Sprint coverage verified
  • All gates must pass
  • PM enforces gates
▸
W7 Build ROBO BUILDER
  • Story = build unit
  • Code generated
  • Unit tests run per story
  • Build fails if tests fail
  • Artifacts stored
▸
W8 Verify ROBO TEST
  • L1: Capability unit + E2E
  • L2: Sprint full regression
  • SAST security scan
  • OWASP Top 10 check
  • Sprint test report
  • Auto-create bugs
▸
W9 Deploy ROBO DEPLOY
  • Verified code deployed
  • Infrastructure provisioned
  • Release notes generated
  • Rollback capability
  • Monitoring enabled

Mandatory Quality Gates

No code enters build without passing all three gates — enforced by the PM agent

Gate 1: Story Unit Tests

Every story must have unit tests before "Ready for Build"

  • Test file references story ID
  • Happy path + error + edge cases
  • 1 test per acceptance criterion minimum
  • Tests map to story's AC

Gate 2: Capability E2E Tests

Every capability must have E2E tests before stories can build

  • Test file references epic ID
  • Full user workflow validated
  • Cross-story integration tested
  • Positive and negative scenarios

Gate 3: Sprint Start Gate

All tests must exist before sprint can activate

  • 100% stories have unit tests
  • 100% capabilities have E2E tests
  • Coverage report generated
  • Zero gaps permitted

AI Agent Roles

Specialized agents handle each phase of the build-test-fix cycle

📋

Project Manager

Orchestrates workshops, manages scheduling, enforces quality gates, tracks engagement health, advocates for UX

🔨

Robo Builder

Builds each story as a unit, runs unit tests during build, generates code from stories + designs + tests

🔍

Robo Test

L1: Capability verification. L2: Sprint regression + SAST + OWASP. Creates bugs automatically on failure

🐛

Robo Debug

Auto-fixes bugs on agent-owned stories. Analyzes failures, implements fixes, re-runs tests. Humans fix human bugs

Robo Test Execution Pipeline

Trigger
Capability Complete
Unit Tests (all stories) Capability E2E Tests
PASS → Verified ✓
FAIL → Create Bugs
Trigger
All Capabilities Verified
All Unit Tests All Capability E2E Sprint E2E Integration SAST Security Scan OWASP Top 10
PASS → Sprint Tested ✓
FAIL → Create Bugs
Output
Sprint Test Report
Unit Results E2E Results SAST Findings OWASP Status Health Score Action Items
Displayed on
Sprint View Page

Bug Detection & Resolution Flow

Robo Test
Detects Failure
→
Bug Created
Linked to Story + Epic
→
Route by
Story Owner
→
Agent-Owned →
Robo Debug (auto-fix)
Human-Owned →
Human Developer (manual)
→
Robo Test
Re-validates

Full Traceability Chain

Theme
→
Epic
→
Story
→
Design
→
Tests
→
Build
→
Verified ✓

Every artifact is traceable back to its origin — from strategic theme through verified deployment.
No orphan code. No untested features. No untracked decisions.

LaunchOS — AI-Powered Project Lifecycle  |  Use this diagram in the Program Kick-Off (W0) and Workstream Vision (W1) presentations

Related: Executive Summary  |  Roadmap & Gantt