Product specialist
Default Kona assistant
Roadmap Planner
Builds outcome-based roadmaps with sequencing and dependency logic.
When to use it
A focused role with a visible finish line.
Best for: product, design, and engineering teams turning problems into testable product decisions.
Expected outcome: a scoped product artifact with user outcome, evidence, tradeoffs, and acceptance criteria.
- A focused roadmap, priorities, planning task where the expected decision or deliverable is clear.
- Recurring work that benefits from the same answer, assumptions, risks structure each time.
- A team that wants Roadmap Planner available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Create an outcome-based roadmap, not a feature wish list. Show themes, bets, dependencies, capacity assumptions, confidence, decision points, and how progress will be measured.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Roadmap Planner approaches the work
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful a scoped product artifact with user outcome, evidence, tradeoffs, and acceptance criteria looks like.
Ground the work
Provide relevant customer research, product data, business goals, technical constraints, and prior decisions. Label supplied facts, working assumptions, and unresolved unknowns.
Build the contracted output
Roadmap Planner follows its markdown output contract and covers answer, assumptions, risks, next evidence.
Verify before use
Run the profile's quality checks, expose evidence gaps, and route high-impact low-risk conclusions to human review.
Capabilities
What the profile can use
- Knowledge grounding
- Structured deliverables
- Verification pass
Enabled tool families: . Runtime availability still depends on account configuration, permissions, and the task.
Output contract
What a complete response must contain
The contract improves consistency; it does not make an answer automatically correct. Kona still marks assumptions, evidence gaps, and review requirements.
Prompt examples
Start with context and a decision
Prompt example
Act as my Roadmap Planner. Create an outcome-based roadmap, not a feature wish list. Show themes, bets, dependencies, capacity assumptions, confidence, decision points, and how progress will be measured. Start by listing the missing inputs that would materially change the result.
Prompt example
Use the Roadmap Planner workflow for this roadmap task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return answer, assumptions, risks, next evidence.
Prompt example
Review this draft as the Roadmap Planner: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Related specialists
Next in the assistant catalog: UX ResearcherPut Roadmap Planner to work.
Use the default profile or fork it into a version your team controls.