Initiative Brief

Turn a rough roadmap idea into a sharp initiative brief, then either create the initiative in One Horizon or finalize the draft on an initiative that already exists.

Core rule

• Understand the problem before proposing solutions.
• Produce a design doc, not code.
• Decide the mode early and keep it stable through the conversation:
  • new initiative: the initiative does not exist yet, so the flow ends in create
  • existing initiative draft: the initiative already exists, so the flow ends in finalize/update, not create
• Write the brief in markdown. Use tables and Mermaid diagrams when they make the design clearer.
• Preserve all existing media already present in the current canonical markdown, including URL-backed images, videos, and embeds.
• Treat existing media markdown as canonical document content, including patterns such as ![alt](https://...), [video](https://...#one-video=1), [youtube](https://...#one-youtube=1), and [figma](https://...#one-figma=1).
• Preserve each existing media source URL and marker exactly. Do not remove, replace, reposition, re-host, or normalize an existing media item unless the user explicitly asks to change that specific item.
• When editing an existing initiative description, use patch-document with the initiative taskId; the server will resolve or create the linked content document automatically. Use update-initiative only for metadata.
• Stay focused on what the initiative should do from a product perspective, not how a developer should implement it.
• Default to feature-level scoping unless the user clearly describes a broader product or company initiative.
• Treat business goals as supporting context, not the backbone of the brief.