clarify-roadmap

Clarify Roadmap

This skill encodes a deep conversational clarification loop to run before roadmap research and generation, when the user provides a high-level project vision that needs structured decomposition. It is instructional -- the calling command drives the loop using its own AskUserQuestion tool. This skill does not spawn subagents.

When to invoke

Apply this checklist to the raw input. If any item is missing or unclear, invoke the loop:

• Vision -- what does the finished product/system look like? What problem does it solve?
• Target users -- who are the primary users? What are their key pain points?
• Constraints -- budget, timeline, team size, regulatory requirements, platform requirements, existing commitments
• Success metrics -- how will the user measure success? (adoption, revenue, performance, user satisfaction, etc.)
• Technical preferences -- preferred stack, hosting, existing infrastructure to integrate with
• Scope boundary -- what is explicitly out of scope for this roadmap?
• Phasing priorities -- what needs to ship first? Are there hard deadlines for any phase?
• Risk tolerance -- appetite for new/unproven tech vs. battle-tested? Tolerance for shipping incrementally vs. all-at-once?

If all eight are present, skip this skill and proceed directly to research. Running the loop on an already-clear input is a cost, not a benefit.

Opt-out signals the caller must honor:

• --skip-clarify anywhere in the arguments
• config.phases.roadmap_clarify === false in .soloflow/config.json or config/defaults.yaml

Anti-pattern

"The user already knows what they want."

A roadmap shapes months of work. The checklist is the judge, not your intuition. Cheap to run, expensive to skip.

Scope-decomposition gate (runs first)

If the input spans multiple independent products (e.g., "build a marketplace AND a separate analytics dashboard AND a mobile companion app"), stop immediately. Do NOT begin clarification on the whole thing.