$npx -y skills add shiquda/roadmap-skill --skill roadmap-task-flowCaptures, enriches, tags, and prioritizes roadmap tasks. Use when the user wants to note work quickly, add missing task details, organize a backlog, or reprioritize an existing list of tasks.
| 1 | # Roadmap Task Flow |
| 2 | |
| 3 | Use this skill for backlog-oriented task work. |
| 4 | |
| 5 | ## Scope |
| 6 | |
| 7 | This skill handles: |
| 8 | |
| 9 | - quick task capture |
| 10 | - task detail enrichment |
| 11 | - task listing and backlog review |
| 12 | - task tagging and batch reprioritization |
| 13 | |
| 14 | Keep the unit of work as tasks in a list or backlog. |
| 15 | |
| 16 | This skill does not handle planning graphs or focused task-subset workspaces. Route those requests to `roadmap-planning-views`. |
| 17 | |
| 18 | ## Recommended workflow |
| 19 | |
| 20 | 1. Identify the target project from the conversation or current context. |
| 21 | 2. Prefer curated prompt workflows when they match the request. |
| 22 | 3. Read project or task resources when more context is needed before changing state. |
| 23 | 4. Fall back to direct task and tag tools for precise updates. |
| 24 | 5. Keep task status, priority, and tags aligned with the real plan after making changes. |
| 25 | |
| 26 | ## Prompt-first defaults |
| 27 | |
| 28 | - Use `quick-capture` for fast idea-to-task capture. |
| 29 | - Use `add-task-details` when a task needs richer description, acceptance criteria, or execution detail. |
| 30 | - Use `auto-prioritize` when the user wants the backlog reordered. |
| 31 | - Use `suggest-tasks` when the user asks what to do next. |
| 32 | |
| 33 | ## References |
| 34 | |
| 35 | - Workflow boundaries: [references/workflow-boundaries.md](references/workflow-boundaries.md) |
| 36 | - MCP mapping: [references/mcp-mapping.md](references/mcp-mapping.md) |