This document outlines the complete workflow and interactions between the six specialized agents in your development ecosystem, designed to take product ideas from concept to fully tested implementation with comprehensive validation, quality assurance, and production-ready infrastructure.
An interactive version of these Agent Instructions is available in Claude.
Open the interactive Claude Artifact
Role: Market feasibility, monetization assessment, and business case development Input: Raw product ideas and market context Output: Business case analysis and Product Manager handoff prompt
Role: Product strategy, MVP planning, requirements definition, and UI/UX handoff preparation Input: Business case from Business Analyst Agent Output: Product requirements, UI/UX handoff package, and FOUR handoff prompts
Role: Technical architecture design, implementation oversight, and multi-agent coordination Input: Product requirements from Product Manager Agent Output: Technical architecture plan with visual diagrams and THREE handoff prompts
Role: Implementation planning, TDD development, and code structure design Input: Architecture specifications and challenge/collaboration cycle Output: Phased implementation with comprehensive testing and documentation
Role: Infrastructure as code, CI/CD pipelines, monitoring, security automation, and environment management Input: Architecture specifications and challenge/collaboration cycle Output: Production-ready infrastructure and deployment automation
Role: Product validation, integration testing, and end-to-end testing Input: Architecture specifications, implementation summaries, and challenge/collaboration cycle Output: Automated test suites and product validation reports
Role: Code quality review and compliance validation Input: Implementation code and handoff specifications Output: Quality feedback and approval validation
Role: UI/UX design, flows, and component specifications Input: Product requirements and personas from Product Manager Agent Output: Annotated mockups, design system snapshot, and TWO handoff prompts (SE, QA)
The matrix below clarifies who is Responsible (R), Accountable (A), Consulted (C), and Informed (I) for major lifecycle activities across agents.
| Activity | Business Analyst | Product Manager | Architect | Software Engineer | DevOps Engineer | QA Engineer | Code Reviewer | UI/UX Design |
|---|---|---|---|---|---|---|---|---|
| Market analysis & opportunity sizing | R/A | C | I | I | I | I | I | I |
| Business case & monetization | R/A | C | I | I | I | I | I | I |
| Product strategy & requirements | C | R/A | C | I | I | C | I | C |
| UI/UX design, flows, and mockups | I | C | C | I | I | C | I | R/A |
| Technology stack evaluation | I | C | R/A | C | C | C | I | I |
| Architecture design & diagrams | I | I | R/A | C | C | C | I | C |
| Challenge & agreement cycle | I | I | A | R | R | R | C | C |
| Implementation planning (phases) | I | I | C | R/A | C | C | I | C |
| Development per phase (TDD) | I | I | I | R | C | C | C | I |
| Code review & standards compliance | I | I | I | C | I | I | R/A | I |
| Architecture compliance review | I | I | R/A | C | I | I | C | I |
| Infrastructure design & CI/CD | I | I | C | C | R/A | I | I | I |
| Test strategy & product validation | I | I | C | C | I | R/A | I | C |
| Release readiness & deployment | I | I | C | C | R/A | C | C | I |
| Handoff prompts & documentation | C | R/A | R/A | C | C | C | C | R |
Notes:
- Accountable (A) indicates final decision ownership. When two agents are marked A, they are co-owners for that activity within their domain scope (e.g., PM for product-facing artifacts, Architect for technical artifacts).
- Activities span the end-to-end workflow; some occur iteratively across phases.
graph TD
A[User Presents Idea] --> B[Business Analyst Agent]
B --> B1[Market & Business Analysis]
B1 --> B2[Business Case Development]
B2 --> B3[User Review & Approval]
B3 --> B4[Generate PM Handoff Prompt]
B4 --> C[Product Manager Agent]
C --> C1[Product Strategy & MVP Planning]
C1 --> C2[Technology Stack Evaluation]
C2 --> C3[Prepare UI/UX Handoff]
C3 --> C4[User Review & Approval]
C4 --> C5[Generate 4 Handoff Prompts]
C5 --> D[Architect Agent]
C5 --> E[Software Engineer Agent - Queued]
C5 --> F[QA Engineer Agent - Queued]
C5 --> U[UI/UX Design Agent]
D --> D1[Technology Stack Evaluation]
D1 --> D2[Design Architecture]
D2 --> D3[Create Visual Diagrams]
D3 --> D4[User Review & Approval]
D4 --> D5[Generate 3 Handoff Prompts]
D5 --> E
D5 --> G[DevOps Engineer Agent]
D5 --> F
%% UI/UX Design Flow
U --> U1[Design Experience & Mockups]
U1 --> Ux[PM Review]
Ux --> Uy{PM Agreement?}
Uy -->|No| Uz[PM Feedback]
Uz --> U1
Uy -->|Yes| U2[User Review & Approval]
U2 --> U3[Generate 2 Handoff Prompts]
U3 --> E
U3 --> F
%% Challenge and Agreement Cycle
E --> E1[Review Architecture Handoff]
G --> G1[Review Architecture Handoff]
F --> F1[Review Architecture Handoff]
E1 --> E2{Agreement?}
G1 --> G2{Agreement?}
F1 --> F2{Agreement?}
E2 -->|No| E3[Generate Challenge Prompt]
G2 -->|No| G3[Generate Challenge Prompt]
F2 -->|No| F3[Generate Challenge Prompt]
E3 --> D6[Address Challenges]
G3 --> D6
F3 --> D6
D6 --> D7[Update Architecture]
D7 --> D5
E2 -->|Yes| H[All Agents in Agreement]
G2 -->|Yes| H
F2 -->|Yes| H
%% Implementation Phase
H --> I[DevOps: Infrastructure Design]
H --> J[Software Engineer: Implementation Planning]
I --> I1[IaC Development]
I1 --> I2[CI/CD Pipeline Setup]
I2 --> I3[Monitoring & Security Setup]
I3 --> I4[Environment Management]
J --> J1[Phased Development Planning]
J1 --> J2[Phase Implementation]
J2 --> K[Code Reviewer Agent]
K --> K1[Code Quality Review]
K1 --> K2{Issues Found?}
K2 -->|Yes| K3[Return to Software Engineer]
K3 --> J2
K2 -->|No| K4[Code Approved]
K4 --> L[Commit to Git Repository]
L --> M[Architect Agent Review]
M --> M1{Architecture Compliant?}
M1 -->|No| M2[Generate Fix Prompt]
M2 --> J2
M1 -->|Yes| N{More Phases?}
N -->|Yes| O[Next Phase Approval]
O --> J2
N -->|No| P[Generate QA Handoff]
P --> F4[QA Implementation & Testing]
F4 --> Q[Product Validated & Complete]
style A fill:#e1f5fe
style B fill:#f3e5f5
style C fill:#f3e5f5
style D fill:#e8f5e8
style E fill:#fff3e0
style G fill:#e3f2fd
style F fill:#fce4ec
style K fill:#e0f2f1
style Q fill:#c8e6c9
- Market Analysis: Conduct comprehensive market research and competitive analysis
- Business Case Development: Assess monetization potential and financial viability
- Risk Assessment: Evaluate market, technology, and financial risks
- Go/No-Go Recommendation: Provide clear business recommendation
- User Validation: Present business case for approval
- Product Manager Handoff: Generate business-validated handoff prompt
- Product Manager Agent Prompt:
AGENT TYPE: PRODUCT MANAGER AGENT- Business context with market opportunity and recommended business model
- Business Context Integration: Incorporate business analysis findings into product strategy
- Technology Stack Evaluation: Assess if default technology stack is optimal for business objectives
- MVP Planning: Create structured epic breakdown with themes, features, and user stories
- UI/UX Handoff Preparation: Prepare a dedicated handoff package for the UI/UX Design Agent
- User Validation: Present complete product plan for approval
- Multi-Agent Handoff: Create FOUR specialized prompts (Architecture, UI/UX, Software Engineer, QA)
- Architect Agent Prompt:
AGENT TYPE: ARCHITECTURE AGENT- Product requirements with business context and confirmed technology stack - UI/UX Design Agent Prompt:
AGENT TYPE: UI/UX DESIGN AGENT- Experience objectives, personas, screen inventory, and constraints - Software Engineer Agent Prompt:
AGENT TYPE: SOFTWARE ENGINEER AGENT- Implementation context (queued until architecture complete and designs ready) - QA Engineer Agent Prompt:
AGENT TYPE: QA ENGINEER AGENT- Testing requirements with UI validation needs (queued until architecture complete and designs ready)
- Technology Stack Evaluation: Assess default stack and recommend alternatives when beneficial
- Requirements Analysis: Review product specifications and UI mockups with confirmed technology stack
- Architecture Design: Create technical architecture within confirmed technology constraints
- Visual Documentation: Generate architectural diagrams using Mermaid
- User Review: Present architecture and diagrams for approval
- Multi-Agent Handoff: Create THREE detailed handoff prompts for implementation agents
- Experience Design: Create flows, wireframes/mockups, and design system snapshot
- Feasibility Alignment: Confirm feasibility within the architecture and stack
- PM Review & Agreement Loop: Present designs to the Product Manager for approval; if not approved, receive feedback and iterate until both PM and UI/UX Design Agents agree
- User Review: Present designs for user approval after PM agreement
- Handoff Generation: Provide two handoffs to Software Engineer and QA Engineer Agents
- Software Engineer Agent Handoff:
AGENT TYPE: SOFTWARE ENGINEER AGENTwith complete specifications - DevOps Engineer Agent Handoff:
AGENT TYPE: DEVOPS ENGINEER AGENTwith infrastructure requirements - QA Engineer Agent Handoff:
AGENT TYPE: QA ENGINEER AGENTwith architecture behavior specifications
- Simultaneous Review: Software Engineer, DevOps Engineer, and QA Engineer Agents review architecture handoff
- Individual Assessment: Each agent evaluates handoff against their domain expertise
- Challenge Generation: Agents generate challenge prompts if concerns exist
- Architecture Response: Architect Agent addresses challenges and updates specifications
- Iterative Refinement: Cycle continues until all agents are in agreement
- Final Agreement: All agents confirm readiness to proceed
# AGENT TYPE: ARCHITECTURE AGENT
# [Agent Name] Challenge Prompt: [Issue/Concern Title]
## Domain-Specific Concerns
[Specific concerns from agent's perspective]
## Impact Assessment
[How concerns affect implementation/infrastructure/testing]
## Recommended Solutions
[Suggested architectural modifications]
## Questions for Architect Agent
[Specific questions requiring clarification]
# AGENT TYPE: ARCHITECTURE AGENT
# [Agent Name] Agreement Confirmation: [Project Name]
## Architecture Review Complete
[Confirmation that specifications are acceptable]
## Ready to Proceed
[Specific capabilities ready for implementation]
- Infrastructure Technology Evaluation: Assess infrastructure stack and recommend alternatives
- Infrastructure as Code Design: Create comprehensive infrastructure definitions
- CI/CD Pipeline Design: Plan automated build, test, and deployment pipelines
- Monitoring Strategy: Design application and infrastructure monitoring
- Security Automation: Plan automated security controls and compliance
- Environment Management: Design development, staging, and production environments
- Software Engineer Coordination: Collaborate on local and cloud development support
- Implementation Technology Evaluation: Assess implementation stack and recommend alternatives
- Environment Assessment: Validate development setup requirements
- Library Preferences: Confirm third-party library choices
- Architecture Integration: Incorporate architectural specifications
- Phase Planning: Break work into logical phases and present plan for approval
- DevOps Coordination: Work with DevOps Engineer on deployment strategies
- Phase Execution: Software Engineer Agent provides ONE phase prompt at a time
- TDD Implementation: Follow Test-Driven Development methodology
- Code Review: Code Reviewer Agent validates implementation against handoff specifications
- Iterative Refinement: Fix issues until Code Reviewer approval achieved
- Git Commit: Code committed to repository after approval
- Architecture Validation: Architect Agent reviews committed code for compliance
- Phase Completion: User approval before proceeding to next phase
- Code Quality: Code Reviewer Agent ensures handoff compliance and coding standards
- Architecture Compliance: Architect Agent validates implementation matches specifications
- Infrastructure Readiness: DevOps Engineer Agent ensures infrastructure supports implementation
- Testing Preparation: QA Engineer Agent receives implementation summaries for test planning
- Testing Technology Evaluation: Assess testing stack and recommend alternatives
- Implementation Summary Review: Receive summary from Software Engineer Agent
- Test Strategy Development: Create comprehensive testing approach using confirmed testing frameworks
- Product Validation: Test implemented product against all requirements
- UI Validation: Test UI against Product Manager mockups using confirmed UI testing framework
- Architecture Behavior Testing: Validate product behavior against Architecture specifications
- Integration Testing: Comprehensive component interaction testing
graph LR
A[Architect Agent] --> B[Generate 3 Handoffs]
P[Product Manager Agent] --> X[Generate UI/UX Handoff]
X --> U[UI/UX Design Review]
U --> U1{PM Agreement?}
U1 -->|No| U2[PM Feedback]
U2 --> U
U1 -->|Yes| U3[Design Ready]
B --> C[Software Engineer Review]
B --> D[DevOps Engineer Review]
B --> E[QA Engineer Review]
C --> F{Agreement?}
D --> G{Agreement?}
E --> H{Agreement?}
F -->|No| I[Challenge Prompt]
G -->|No| I
H -->|No| I
I --> J[Architecture Updates]
J --> A
F -->|Yes| K[Implementation Ready]
G -->|Yes| K
H -->|Yes| K
graph LR
A[Software Engineer] --> B[Implementation]
B --> C[Code Reviewer]
C --> D{Handoff Compliant?}
D -->|No| E[Feedback to SE]
D -->|Yes| F[Git Commit]
E --> A
F --> G[Architecture Review]
G --> H{Architecture Compliant?}
H -->|No| I[Fix Prompt to SE]
H -->|Yes| J[Phase Complete]
I --> A
graph LR
A[DevOps Engineer] --> B[Infrastructure Design]
B --> C[Software Engineer Coordination]
C --> D[Local Development Support]
D --> E[Cloud Development Support]
E --> F[CI/CD Integration]
F --> G[Production Deployment]
AGENT TYPE: BUSINESS ANALYST AGENT: Market analysis and business case handoffAGENT TYPE: PRODUCT MANAGER AGENT: Product requirements and business contextAGENT TYPE: UI/UX DESIGN AGENT: UI/UX designs, interaction specs, and design systemAGENT TYPE: ARCHITECTURE AGENT: Technical specifications, challenges, and updatesAGENT TYPE: SOFTWARE ENGINEER AGENT: Implementation specifications, fixes, and summariesAGENT TYPE: DEVOPS ENGINEER AGENT: Infrastructure requirements and coordinationAGENT TYPE: QA ENGINEER AGENT: Testing requirements and validation needsAGENT TYPE: CODE REVIEWER AGENT: Quality assurance and compliance feedback
- Business Analyst → Product Manager: Market analysis and business model recommendations
- Product Manager → Architecture: Product requirements with business context and technology stack
- Product Manager → UI/UX Design: Experience objectives, personas, and screen inventory
- UI/UX Design → Software Engineer/QA: Annotated designs and validation specs
- Architecture → Software Engineer/DevOps/QA: Technical specifications with challenge/agreement cycle
- Software Engineer ↔ DevOps Engineer: Local and cloud development coordination
- Software Engineer → Code Reviewer: Implementation validation and quality assurance
- Architecture ← Software Engineer/DevOps/QA: Challenge prompts and agreement confirmations
- Code Reviewer → Software Engineer: Quality feedback and compliance validation
- Architecture → Software Engineer: Architecture compliance validation and fix prompts
- Software Engineer → QA Engineer: Implementation summary and testing handoff
- Business Analyst Agent: Business case validation and Go/No-Go decisions
- Product Manager Agent: Product strategy validation, technology stack confirmation, and UI mockup review
- Architect Agent: Architecture review, technology stack confirmation, and challenge resolution
- DevOps Engineer Agent: Infrastructure technology stack confirmation and operational requirements
- Software Engineer Agent: Implementation technology stack confirmation, environment setup, and phase approvals
- QA Engineer Agent: Testing technology stack confirmation and testing scope validation
- Development Process: Phase-by-phase implementation with quality gates
- Final Delivery: Business-validated, tested, and production-ready solution
- Product Manager Agent: Evaluates stack against business objectives and market requirements
- Architect Agent: Evaluates stack against technical architecture and system requirements
- Software Engineer Agent: Evaluates stack against implementation productivity and development requirements
- DevOps Engineer Agent: Evaluates stack against infrastructure and operational requirements
- QA Engineer Agent: Evaluates stack against testing framework compatibility and effectiveness
- User Approval Gates: All technology stack changes require explicit user approval
- Cross-Agent Alignment: Technology decisions propagate through all downstream agents
- Documentation Updates: All agents update processes based on confirmed technology stack
- Integration Validation: Technology choices validated across the entire ecosystem
- Business Analyst Agent: Market viability and business model validation
- Product Manager Agent: Product strategy validation and technology stack confirmation
- Architect Agent: Technical architecture review with challenge/agreement cycle
- Software Engineer Agent: Phase-by-phase development with quality validation
- DevOps Engineer Agent: Infrastructure compliance and operational excellence validation
- Code Reviewer Agent: Implementation quality and handoff compliance validation
- QA Engineer Agent: Product validation against requirements and architectural specifications
- User presents idea → Business Analyst Agent evaluates market and business viability
- Business case validation → User approves business opportunity and monetization strategy
- Product Manager creates strategy → Product requirements, technology evaluation, and UI mockups
- Product strategy approval → User confirms product approach and technology stack
- Architect Agent designs system → Technical specifications with confirmed technology stack
- Architecture approval → User validates architectural approach and visual diagrams
- Multi-agent handoff → Architect Agent generates three handoff prompts
- Challenge & agreement cycle → Software Engineer, DevOps Engineer, and QA Engineer review and challenge if needed
- Final agreement → All agents confirm readiness to proceed with implementation
- Infrastructure preparation → DevOps Engineer designs IaC, CI/CD, monitoring, and security
- Implementation planning → Software Engineer creates phase plan with DevOps coordination
- Phase implementation → TDD development with Code Reviewer validation
- Architecture validation → Architect Agent reviews committed code for compliance
- Iterative development → Repeat implementation cycle for all phases
- QA validation → QA Engineer validates complete product against all requirements
- Production deployment → DevOps Engineer enables production deployment with monitoring
- Project complete → Fully tested, documented, and production-ready solution
- Market Analysis: Thorough feasibility assessment before product development
- Business Model Alignment: Revenue strategy integrated throughout development
- Technology Optimization: Stack evaluation at multiple points for optimal choices
- Product Strategy: Clear requirements and user-focused design with visual mockups
- Technical Architecture: Robust, scalable system design with multi-agent validation
- Infrastructure Excellence: Production-ready infrastructure with automation and monitoring
- Implementation Quality: Professional code standards with TDD methodology
- Product Validation: Comprehensive quality assurance against all requirements
- Challenge-Driven Architecture: Multi-agent review prevents downstream issues
- Technology Stack Consensus: All agents align on optimal technology choices
- Iterative Refinement: Multiple validation points ensure quality at each stage
- Cross-Agent Coordination: Software Engineer and DevOps Engineer collaboration ensures seamless development
- Quality Assurance: Multiple review layers ensure implementation compliance
- Infrastructure as Code: Reproducible, version-controlled infrastructure
- CI/CD Automation: Automated build, test, and deployment pipelines
- Monitoring and Security: Comprehensive observability and automated security controls
- Environment Management: Consistent development, staging, and production environments
- Cloud Cost Optimization: DevOps Engineer responsible for maintaining cost-effective infrastructure
- Local and Cloud Support: Seamless development experience across environments
- Latest Technology Stack: Always using latest stable versions of all libraries and frameworks
- Comprehensive Change Tracking: Complete changelog documentation for all modifications
- Business Validation: Ideas validated for viability before development investment
- Technology Optimization: Stack choices optimized for both capability and cost
- Local Development: Minimal cloud costs during development phase
- Automated Operations: Reduced operational overhead through automation
- Phased Approach: User control over development progression with quality gates
- Market-Driven Development: All projects validated for business opportunity and competitive advantage
- Technology-Business Alignment: Technology choices optimized for business objectives
- Revenue Model Integration: Business models supported throughout entire development and infrastructure
- Operational Excellence: Production-ready infrastructure with monitoring, security, and automation
- Multi-Point Validation: Business, product, architecture, implementation, infrastructure, and testing validation
- Challenge-Driven Architecture: Proactive issue identification through multi-agent review
- Technology Consensus: All agents align on optimal technology choices for their domains
- Quality Gates: Multiple validation points ensure quality at each development stage
- Proactive Issue Resolution: Challenge and agreement cycle prevents downstream problems
- Technology Optimization: Stack evaluation at multiple points ensures optimal choices
- Cross-Agent Coordination: Software Engineer and DevOps Engineer collaboration eliminates integration issues
- Automated Operations: Infrastructure automation reduces operational overhead
- Parallel Preparation: Multiple agents can work simultaneously within coordinated workflow
- Infrastructure Excellence: Production-ready infrastructure from day one
- Deployment Automation: Automated CI/CD pipelines for reliable deployments
- Monitoring and Security: Comprehensive observability and security automation
- Environment Consistency: Identical environments from development to production
- Operational Support: Full monitoring, alerting, and incident response capabilities
- Business Feasibility: Market and financial viability confirmed before development
- Technology Validation: Technology choices validated across all agent domains
- Architecture Review: Multi-agent challenge process identifies issues early
- Quality Assurance: Implementation compliance validated at multiple levels
- Operational Readiness: Infrastructure and deployment risks addressed proactively
This enhanced agent ecosystem provides a complete, professional development workflow that takes raw business ideas from initial concept through market validation to production-ready implementation while maintaining high quality standards, business viability, operational excellence, cost efficiency, and user control throughout the entire process.
The agent ecosystem is designed to be extensible and will continue to evolve with additional specialized agents to provide even more comprehensive coverage of the product development and business lifecycle:
Status: Already integrated above. This item has been implemented; see Agent Ecosystem Components and workflow updates.
Role: Marketing strategy and campaign development Purpose: Generate comprehensive marketing materials and strategies for products built with the agent ecosystem Responsibilities:
- Develop marketing strategies based on business analysis
- Create marketing content and campaigns
- Generate social media strategies and content
- Develop brand positioning and messaging
- Coordinate with Sales Agent for integrated marketing-sales campaigns
Role: Customer support and knowledge management Purpose: Provide automated customer support and create comprehensive support documentation Responsibilities:
- Generate FAQs and knowledge base articles
- Handle basic customer support inquiries
- Escalate complex issues to appropriate agents
- Pass bug reports to QA Engineer Agent for evaluation
- Forward feature suggestions to Product Manager Agent for consideration
- Maintain support documentation and troubleshooting guides
Role: Sales strategy and customer acquisition Purpose: Drive sales campaigns and provide sales support materials Responsibilities:
- Develop sales strategies and pitches
- Create sales materials and presentations
- Work with Marketing Agent on integrated campaigns
- Generate lead qualification and nurturing strategies
- Develop pricing strategies and sales processes
- Create customer onboarding and retention programs
- Focused Expertise: Each agent becomes more specialized in their domain
- Improved Quality: Deeper expertise leads to higher quality outputs
- Better Collaboration: Clearer boundaries and handoff points between agents
- End-to-End Support: From idea conception to customer support
- Integrated Workflows: Seamless handoffs between all business functions
- Comprehensive Documentation: Full coverage of product lifecycle documentation
- Automated Support: Reduce manual support overhead
- Marketing Automation: Streamlined marketing and sales processes
- Continuous Improvement: Feedback loops from support to product development
These future agents will be developed and integrated into the ecosystem based on:
- User feedback and demand
- Ecosystem maturity and stability
- Integration complexity and testing requirements
- Business value and impact assessment
The modular design of the current agent ecosystem ensures that new agents can be seamlessly integrated without disrupting existing workflows.
To improve reliability, traceability, and automation of inter-agent handoffs, future iterations will introduce a flow-based orchestration using n8n:
- Triggering
- Webhook/Manual triggers to start flows from user actions or CI events
- Scheduled triggers for recurring validations or syncs
- Routing & Handoffs
- Dedicated nodes per agent to package, validate, and dispatch handoff payloads
- Conditional routing for challenge/agreement loops (branch on approval/feedback)
- State & Persistence
- Use n8n data stores (and/or external DB) to persist handoff status, versions, and audit logs
- Idempotency keys on messages to prevent duplicate processing
- Reliability
- Built-in retries with backoff and dead-letter handling for failed steps
- Notifications on failures and approvals (email/Slack/MS Teams nodes)
- Integration
- GitHub nodes for changelog commits and PR automation
- Issue tracker nodes to open/close work items based on handoff outcomes
- Artifact storage for prompts, designs, and reports
- Security & Access
- Scoped credentials per integration
- Sanitization steps for prompt payloads
Initial rollout will focus on orchestrating the Product Manager → UI/UX → Software Engineer/QA flow and the Architecture challenge/agreement loop. Subsequent phases will extend orchestration to DevOps pipelines and production approval gates.