How to manage high-level roadmaps?

[ccll]

grill-with-docs is great for discussing a specific problem in detail, and to-prd can put the discussion into a spec, but I found that they tend to forget high-level goals in the PRD.

For example if I start a large and vague topic with grill, it will explore many aspects and guide me gradually to focus on a more and more specific issue in this large topic, leave many other choices open for 'later exploration', but when the discussion becomes a PRD, the PRD says nothing about the other open possibilities and choices and what we should explore later, they are lost.

I want to store the large and high-level discussion to something like a ROADMAP, not a PRD, and later I may explore this ROADMAP, generate more PRDs from it, until the ROADMAP's goal is achieved.

How should I do it? Do we need /roadmap skill? or should grill-with-docs records high-level things into a ROADMAP.md like CONTEXT.md when it found some idea is high-level enough?

[SyedAsimAliSE]

I created two skills to solve this exact scenario :

/roadmap :
Captures the full breadth of a grilling session into a living ROADMAP document.

&
/roadmap-area :
Skill explores individual open areas later and generates PRDs from them.

If you want to try these I can paste the gist here.

[ccll]

Thanks! I created my own version of /roadmap with the help of coding agent and it works, but I still want to know if Matt's skills would include a canonical solution to this problem.

[SyedAsimAliSE]

nice, may be you can refer your agent to Matt's skills and ask it to provide you the solution according to his skills set.

[dexhunter]

I still want to know if Matt's skills would include a canonical solution to this problem.

The repo now includes /wayfinder for planning work that spans multiple sessions. Its map keeps the high-level destination and the possibilities you haven't explored yet.

Questions you can already state become decision tickets. Less-defined, in-scope possibilities stay in Not yet specified, then become tickets as earlier decisions clarify them. Decisions so far links to the resolved tickets, while Out of scope records what you've deliberately excluded.

Start with /wayfinder and a bounded goal, then invoke it with the same map's URL to continue, normally one decision per session. Once the map is clear, the documented handoff is /to-spec followed by /to-tickets. That gives you the persistent planning context you were missing, with a separate spec when you're ready to build.