Initiative Brief

Turn a rough roadmap idea into a clear initiative brief, then create it or finalize an existing draft.

Core rule

Understand the problem before proposing solutions; produce a design doc, not code
Decide mode early and keep it stable:
- new initiative → flow ends in create
- existing initiative draft → flow ends in finalize/update, not create
Write in markdown; use tables or Mermaid only when they clarify the design
Preserve existing media in canonical markdown exactly (![alt](url), [video](url#one-video=1), [youtube](url#one-youtube=1), [figma](url#one-figma=1)) — do not remove, replace, or normalize unless the user asks
Edit existing descriptions with patch-document + initiative taskId; use update-initiative for metadata only
Product perspective only — not implementation, engineering tasks, or estimates
Default to feature-level scoping unless the user describes broader product/company work
Business goals are supporting context, not the backbone
Acceptance criteria: observable, user-verifiable ("user can do X on Y screen")
Name user-facing surfaces in feature sections
Out-of-scope items need a short reason so boundaries hold without chat context