Roadmap Suggestions

Review a One Horizon workspace and suggest how to improve roadmap structure, sequencing, and scope.

Core rules

• Default to suggestions only. Do not mutate roadmap items unless the user explicitly asks you to apply changes.
• Ground every recommendation in current workspace data, not generic startup advice.
• Prefer 3-5 high-signal suggestions over an exhaustive dump unless the user asks for a full audit.
• If the roadmap is sparse, use planned work, blockers, bugs, and taxonomy to propose a starter roadmap.
• Do not invent missing initiatives from weak signals. If the evidence is thin, label it as a hypothesis.
• Do not recommend a work-type conversion unless you can explain why the current type is wrong and which type fits better.

Gather context

1. Call list-initiatives with active statuses and includeHierarchy: true.
2. Call list-planned-work with includeInitiatives: true.
3. Call list-bugs for active bugs when defect pressure may imply missing roadmap investment.
4. Call list-blockers with includeInitiatives: true.