Stage 2: Requirements and Solution Design
Stage 2: Requirements and Solution Design
Owner: Pablo (Production Line Architect) Reviewers: Elena (Enterprise Architect), Clara (CTO) Blueprint stage: Stage 2 -- Requirements and Solution Design
Trigger
Production brief received from Camille (Stage 1 gate passed).
Inputs
| Source | What |
|---|---|
| Camille (Stage 1) | Production brief with intake answers |
| Client | Domain documentation, existing artifacts, tool data |
| Elena | Architecture standards and guidance |
| Ada | Pattern catalog reference |
| Work order (if exists) | Product-specific configuration and reference implementation |
Activities
2.1 Decompose Requirements
Map each client use case to agent capabilities. Determine which capabilities are in scope, out of scope, or future. Define the skill set -- identify standard skills (from work order reference) and custom skills needed.
2.2 Define Agent Capabilities
For each capability in scope, specify:
| Column | Description |
|---|---|
| Capability | What the talent can do |
| Skills | Which .claude/commands/ implement it |
| Patterns | Which agentic patterns power it |
| Inputs | What the skill needs |
| Outputs | What the skill produces |
2.3 Design Tool Integration (if applicable)
Map the client tool's data model, define validation rules, design import/export, document field mappings.
2.4 Design Domain Mapping
Map client methodology phases to skills, identify terminology, define deliverable codes and naming conventions.
2.5 Estimate Build Effort
Break down by assembly phase (A through H). Reference the work order for product-type-specific estimates if a similar product has been built before.
2.6 Align with Dana on Delivery
Coordinate delivery timeline, handover scheduling, client communication plan.
Outputs
| Deliverable | Format | Destination |
|---|---|---|
| Solution specification | Markdown | Reviewed by Clara/Elena |
| Capability-to-skill mapping | Table in solution spec | Used by Ada (Stage 3) |
| Build effort estimate | Section in solution spec | Confirmed by Pablo |
| Delivery schedule | Markdown | Coordinated with Dana |
Quality Gate
Gate: Solution spec approved by Clara (CTO) or Elena (Enterprise Architect) Criteria: All capabilities scoped, skill list defined, domain mapping complete, tool integration designed (or N/A), effort within budget, delivery schedule confirmed. Evidence: Approved solution specification document.