intent-extraction · supabase_json
Build Bezel intent-extraction idea-001
intent-extraction artifact · for Build Bezel · phase idea-001 · status draft
target users
- Founder with a product idea
- Operator with a workflow pain
- Domain expert with partial requirements
- Business owner with a PRD or existing software concept
- Internal Dreamborn team dogfooding Bezel to build Bezel
Agent Handoff
Start Here
intent-extraction artifact · for Build Bezel · phase idea-001 · status draft
Completion Evidence
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
Artifact Shape
- phase: idea-001
- artifact: intent-extraction
- stated goal: Create Dreamborn Build, powered by Bezel, as a guided product studio for people who want real production software built.
- implied goal: Give founders, operators, and domain experts a trustworthy way to move from messy idea or PRD to AI-first product design, plan, and build without losing context or being forced into a traditional SaaS-shaped workflow.
- target users: 5 items
- desired outcomes: 5 items
- canonical question: What outcome are you trying to create, and what assumptions are baked into the way you described it?
- assumptions to challenge: 5 items
Structured Payload
Machine-readable source fields
phase
idea-001
artifact
intent-extraction
stated goal
Create Dreamborn Build, powered by Bezel, as a guided product studio for people who want real production software built.
implied goal
Give founders, operators, and domain experts a trustworthy way to move from messy idea or PRD to AI-first product design, plan, and build without losing context or being forced into a traditional SaaS-shaped workflow.
target users
- Founder with a product idea
- Operator with a workflow pain
- Domain expert with partial requirements
- Business owner with a PRD or existing software concept
- Internal Dreamborn team dogfooding Bezel to build Bezel
desired outcomes
- Extract the real goal behind any input maturity level
- Challenge over-specified PRDs and legacy SaaS assumptions
- Suggest AI-first ways to accomplish the same business outcome
- Guide users through serious design and planning before production build
- Save every step and make resume state obvious
canonical question
What outcome are you trying to create, and what assumptions are baked into the way you described it?
assumptions to challenge
- The customer knows what product shape they need
- A PRD should directly become a build plan
- More screens means more value
- AI should be added to an existing SaaS workflow instead of changing the workflow itself
- Planning is a lightweight prelude instead of a critical production phase