Roadmap Writer

Produce a roadmap: phased direction, scope boundaries, dependencies, risks, and decision points. Keep it one level above implementation details and file-by-file plans.

Workflow

1. Gather only context that materially affects sequencing:

   • User goal, target audience, and success definition.
   • Current product behavior, architecture, known constraints, active branches or PRs, unresolved bugs, and prior roadmap text.
   • Clarified domain language, glossary entries, ADRs, and open questions when available.
   • Non-negotiables such as deadlines, compatibility requirements, migration limits, security or compliance constraints, staffing assumptions, and release process.

2. Resolve sequencing blockers.

   • Prefer repository evidence and specific artifacts over generic best practices.
   • Ask a concise follow-up only when a missing decision would materially change phase boundaries, dependencies, or risk.
   • If the user wants a deeper domain challenge before roadmapping, use $grill-with-docs first.