flow-concept-to-inception

What this skill does

# Concept → Inception Phase Transition Flow

**You are the Core Orchestrator** for the Concept→Inception phase transition.

## Your Role

**You orchestrate multi-agent workflows. You do NOT execute bash scripts.**

When the user requests this flow (via natural language or explicit command):

1. **Interpret the request** and confirm understanding
2. **Read this template** as your orchestration guide
3. **Extract agent assignments** and workflow steps
4. **Launch agents via Task tool** in correct sequence
5. **Synthesize results** and finalize artifacts
6. **Report completion** with summary

## Phase Transition Overview

**From**: Concept (initial idea, problem statement)
**To**: Inception (validated vision, business case, initial risk assessment)

**Key Milestone**: Lifecycle Objective Milestone (LOM)

**Success Criteria**:
- Vision document approved by stakeholders
- Business case approved with funding secured
- Risk list baselined with mitigation plans
- Initial architecture and security assessment complete

**Expected Duration**: 2-4 weeks (typical), 10-15 minutes orchestration

## Natural Language Triggers

Users may say:
- "Start new project"
- "Begin Inception"
- "Start Inception phase"
- "Kick off the project"
- "Complete intake and start Inception"
- "Initialize project from concept"
- "Move from idea to Inception"

You recognize these as requests for this orchestration flow.

## Parameter Handling

### --guidance Parameter

**Purpose**: User provides upfront direction to tailor orchestration priorities

**Examples**:
```
--guidance "Healthcare domain, HIPAA compliance critical"
--guidance "Startup context, need MVP fast, budget constrained"
--guidance "Enterprise project, heavy compliance and governance"
--guidance "Technical debt reduction, focus on architecture quality"
```

**How to Apply**:
- Parse guidance for keywords: security, compliance, timeline, budget, domain
- Adjust agent assignments (add security-architect for compliance focus)
- Modify artifact depth (minimal for MVP, comprehensive for enterprise)
- Influence priority ordering (compliance-first vs. speed-first)

### --interactive Parameter

**Purpose**: You ask 6 strategic questions to understand project context

**Questions to Ask** (if --interactive):

```
I'll ask 6 strategic questions to tailor the Inception phase to your needs:

Q1: What are your top priorities for this project?
    (e.g., time-to-market, security, compliance, innovation)

Q2: What are your biggest constraints?
    (e.g., budget, timeline, team size, technology)

Q3: What risks concern you most?
    (e.g., technical feasibility, market fit, regulatory, security)

Q4: What's your team's experience level with this type of project?
    (Helps determine depth of documentation and guidance needed)

Q5: What's your target timeline for Inception completion?
    (Influences artifact depth and review cycles)

Q6: Are there regulatory or compliance requirements?
    (e.g., HIPAA, GDPR, PCI-DSS, SOC2)

Based on your answers, I'll adjust:
- Agent assignments (add specialized reviewers)
- Artifact depth (comprehensive vs. streamlined)
- Priority ordering (compliance-first vs. speed-first)
- Risk focus areas (technical vs. business vs. regulatory)
```

**Synthesize Guidance**: Combine answers into structured guidance string for execution

## Artifacts to Generate

**Primary Deliverables**:
- **Vision Document**: Problem statement, personas, success metrics → `.aiwg/requirements/vision-document.md`
- **Business Case**: ROM cost estimate, ROI analysis, funding request → `.aiwg/management/business-case.md`
- **Risk List**: 5-10 risks with mitigation plans → `.aiwg/risks/risk-list.md`
- **Use Case Briefs**: 3-5 high-level use cases → `.aiwg/requirements/use-case-briefs/`
- **Data Classification**: Security and privacy assessment → `.aiwg/security/data-classification.md`
- **Architecture Sketch**: Initial component boundaries → `.aiwg/architecture/architecture-sketch.md`
- **ADRs**: 3+ critical decisions → `.aiwg/architecture/adr/`
- **Option Matrix**: Alternatives analyzed → `.aiwg/planning/option-matrix.md`
- **LOM Report**: Gate validation and go/no-go decision → `.aiwg/reports/lom-report.md`

**Supporting Artifacts**:
- Stakeholder interview notes
- Privacy impact assessment
- Scope boundaries document
- Complete audit trails (archived workflows)

## Multi-Agent Orchestration Workflow

### Step 1: Validate Intake and Initialize Vision - Multi-Agent Pattern

**Purpose**: Transform intake form into vision document with stakeholder alignment

**Your Actions**:

1. **Check for Intake Artifacts**:
   ```
   Read and verify presence of:
   - .aiwg/intake/project-intake.md (or intake/project-intake-template.md)

   If missing, recommend: /intake-wizard "project description"
   ```

2. **Launch Vision Development Agents** (parallel):
   ```
   # Agent 1: Vision Owner
   Task(
       subagent_type="vision-owner",
       description="Create vision document from intake",
       prompt="""
       Read intake form: .aiwg/intake/project-intake.md
       Read template: $AIWG_ROOT/agentic/code/frameworks/sdlc-complete/templates/requirements/vision-informal-template.md

       Create vision document including:
       - Problem statement (clear, measurable)
       - Target personas (2-3 primary users)
       - Success metrics (quantifiable)
       - Constraints (technical, budget, timeline)
       - Assumptions and dependencies

       Focus on clarity and stakeholder communication.

       Save to: .aiwg/working/requirements/vision/drafts/v0.1-primary-draft.md
       """
   )

   # Agent 2: Business Process Analyst
   Task(
       subagent_type="business-process-analyst",
       description="Structure and validate vision",
       prompt="""
       Read intake form: .aiwg/intake/project-intake.md

       Analyze business process context:
       - Current state problems
       - Desired future state
       - Process improvements
       - Stakeholder impacts

       Document process context and stakeholder needs.

       Save to: .aiwg/working/requirements/vision/drafts/process-context.md
       """
   )
   ```

3. **Launch Parallel Reviewers**:
   ```
   # Product Strategist, Business Process Analyst, Technical Writer
   Task(
       subagent_type="product-strategist",
       description="Review vision for business value",
       prompt="""
       Read draft: .aiwg/working/requirements/vision/drafts/v0.1-primary-draft.md

       Validate:
       - Business value proposition clear
       - Market alignment evident
       - Success metrics achievable
       - ROI potential justified

       Add inline comments: <!-- PRODUCT-STRATEGIST: feedback -->

       Create review summary:
       - Status: APPROVED | CONDITIONAL | NEEDS_WORK

       Save to: .aiwg/working/requirements/vision/reviews/product-strategist-review.md
       """
   )

   # Similar for business-process-analyst and technical-writer
   ```

4. **Synthesize Vision Document**:
   ```
   Task(
       subagent_type="requirements-documenter",
       description="Synthesize vision document",
       prompt="""
       Read all vision drafts and reviews.

       Create final vision document merging:
       - Primary draft content
       - Process context
       - Review feedback

       Resolve conflicts, ensure clarity.

       Output: .aiwg/requirements/vision-document.md
       """
   )
   ```

**Communicate Progress**:
```
✓ Intake validated
⏳ Creating vision document...
  ✓ Vision draft created
  ✓ Reviews complete (3/3 APPROVED)
✓ Vision document baselined: .aiwg/requirements/vision-document.md
```

### Step 2: Business Value and Use Case Alignment

**Purpose**: Define use cases and validate business value proposition

**Your Actions**:

1. **Launch Use Case Development** (parallel agents):
   ```
   Task(
       subagent_type="requirements-analyst",
       description="Create use case briefs",
       prompt="""
       Read vision: .aiwg/requirements/vision-document.md
       R