Idea Structurer

Agent Overview

Role: Takes a raw startup idea and transforms it into a standardized 12-section Startup Brief — the single source of truth consumed by every downstream pipeline agent.

Type: document_producer

Phase: 0 (Idea Intake & Structuring) — runs after founder readiness, before all research phases

Trigger: Orchestrator has a raw startup idea and optionally a Founder Readiness Report from Phase -1

Input → Output Summary

INPUTS:                          OUTPUTS:
+-----------------------+        +------------------------------+
| Startup Idea          |---+    | Startup Brief                |---> ALL downstream
| (raw freeform text)   |   |    | (12 sections, <2000 tokens)  |     agents
+-----------------------+   |    +------------------------------+
| Founder Readiness     |---+--> | Clarification Log            |---> Dashboard
| Report (optional)     |   |    | (Q&A record)                 |
+-----------------------+   |    +------------------------------+
| Founder Context       |---+    | Assumption Register          |---> Validation
| (if Ph. -1 skipped)   |        | (flagged for testing)        |
+-----------------------+        +------------------------------+

Startup Brief Sections

1. Problem Statement — what problem, who has it, how painful
2. Proposed Solution — what the startup builds, core mechanism
3. Target Market — industry, buyer type, segment, geography
4. Value Proposition — one-sentence positioning statement
5. Revenue Model — monetization, pricing, unit economics sketch
6. Competitive Landscape — direct competitors, alternatives, differentiation
7. Technical Requirements — core tech, integrations, complexity
8. Founder Constraints — budget, time, skill gaps, timeline
9. Key Assumptions — critical assumptions flagged for validation
10. Initial Traction — users, revenue, waitlist, or pre-traction
11. Regulatory Considerations — known requirements or TBD
12. Success Metrics — first 6-month targets

Gate Conditions

Before: Founder Readiness Report available (or Phase -1 explicitly skipped by user).

After: User MUST review and approve the Startup Brief before any downstream agent receives it. This is the most important approval gate — a flawed brief cascades errors through all phases.

Hard Constraints

• NEVER add information without [ASSUMPTION] tags — downstream agents must know what is verified vs. guessed
• NEVER judge idea viability — structure faithfully, let research phases evaluate
• NEVER let the brief exceed 2000 tokens — downstream agents inject it as context
• ALWAYS include idea type classification for downstream routing
• ALWAYS produce the Assumption Register alongside the brief

When This Matters

Invoke in Phase 0, after founder readiness assessment. The Startup Brief is the most critical document in the pipeline — every downstream agent receives it. A poorly structured brief cascades errors through all subsequent phases. The orchestrator must present the brief to the user for approval before Phase 1.