$npx -y skills add shiquda/roadmap-skill --skill roadmapIntroduces roadmap-skill and routes roadmap work to the right workflow. Use when the user needs brief context about roadmap-skill, or wants help deciding between backlog task flow, planning views, and the web workspace.
| 1 | # Roadmap Skill |
| 2 | |
| 3 | Use this skill as the lightweight entry point for roadmap-skill. |
| 4 | |
| 5 | ## What roadmap-skill is |
| 6 | |
| 7 | `roadmap-skill` is a local-first roadmap MCP for managing projects, tasks, tags, planning views, and a browser-based workspace. The MCP already contains the detailed tool, prompt, and resource descriptions, so this skill should stay brief and focus on routing. |
| 8 | |
| 9 | ## How to route work |
| 10 | |
| 11 | - Use `roadmap-task-flow` for capturing tasks, enriching task details, tagging work, or reprioritizing a backlog. |
| 12 | - Use `roadmap-planning-views` when the user wants to build a focused graph from a subset of tasks, reason about dependencies, or organize near-term versus later work in a planning workspace. |
| 13 | - Use `roadmap-web-visualization` when the user wants to open or close the local web workspace, or review roadmap state visually in a browser. |
| 14 | |
| 15 | ## Default approach |
| 16 | |
| 17 | 1. Keep the introduction brief. |
| 18 | 2. Identify whether the user is asking for backlog flow, planning views, or the web workspace. |
| 19 | 3. Read the corresponding reference file only when needed. |
| 20 | 4. Let the MCP's own prompt, resource, and tool descriptions carry the implementation detail. |
| 21 | 5. Avoid duplicating detailed MCP docs inside this skill. |
| 22 | |
| 23 | ## References |
| 24 | |
| 25 | - Product overview: [references/overview.md](references/overview.md) |
| 26 | - Routing guide: [references/routing.md](references/routing.md) |