Create Brief

Purpose

Transform a vague product idea into a structured, one-page Product Brief. This is the first artifact in the planning chain. Every subsequent artifact depends on this one. The brief is the single source of truth for scope — it constrains what follows: PRD, roadmap, design system decisions, and architecture. A well-written brief saves weeks of misalignment by making implicit assumptions explicit before any design or engineering work begins.

The brief is not a commitment. It is a hypothesis — a shared understanding of what we are building, for whom, and why. It will evolve as we learn, but it must be captured in writing before we spend resources on execution.

Agent Protocol

Trigger

Exact user phrases: "I want to build", "new app idea", "create a brief", "product brief", "help me define", "help me figure out what I am building", "start a project".

Input Context

Before activating, verify:

• master-orchestrator has routed here, OR user has directly asked for a brief.
• No existing brief in docs/ (if one exists, ask: "A brief already exists at {path}. Review or replace?")
• User has at least one sentence describing their idea.