Convert high-level project visions into complete roadmap briefs through guided questioning.
npx skills add https://github.com/kesteva/soloflow --skill clarify-roadmap
Please help me install this Agent Skill. Skill: clarify-roadmap Source: https://github.com/kesteva/soloflow/tree/main/skills/clarify-roadmap Command: npx skills add https://github.com/kesteva/soloflow --skill clarify-roadmap
When you have a high-level project vision but lack structured details, you risk creating vague, misaligned roadmaps that waste time and resources on low-priority work. This Skill eliminates that risk by enforcing a deep conversational clarification loop to capture all critical inputs before roadmap generation.
Invoke the clarify-roadmap skill with your high-level project vision to start the guided clarification loop and generate a complete roadmap brief.
High-intent search queries and answers about installing and using this skill.
To turn a vague project idea into a clear product roadmap, use a guided questioning loop to capture critical inputs like vision, target users, and constraints. This structured clarification process ensures no key detail is missed before generating an actionable plan.
Decomposing a multi-product vision requires a scope-decomposition gate that detects overlapping plans and prompts you to select one product to roadmap first. This prevents confused, misaligned roadmaps by focusing on a single product scope before detailed planning.
You identify scope boundaries and success metrics by enforcing an 8-point checklist during project clarification. This structured approach captures essential inputs including budget constraints, must-launch features, and risk tolerance to define clear project boundaries.
Yes, you can use guided questioning to plan a task management tool for remote freelancers. The conversational loop walks you through clarifying target user pain points and technical preferences to produce a complete, actionable roadmap brief.
Before generating an actionable roadmap brief, you need critical inputs including vision, target users, constraints, success metrics, technical preferences, scope boundaries, phasing priorities, and risk tolerance. Capturing these prevents wasting resources on low-priority work.
You should not use an automated clarification loop if your high-level project vision already contains structured details, complete success metrics, and defined scope boundaries. The loop is specifically designed for unstructured ideas that require decomposition before epic generation.
g5becksGuide iterative dialogue to discover and refine project requirements.
GrinRusDecompose vague roadmap items into small reviewable tasks with verification criteria.
onelee85Aggregate project statistics from version control, issue trackers, and planning documents.
crozzbiteIdentify MVP scope and architectural boundaries through guided questioning.
