nw-roadmap

Featured

Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution.

AI & Automation 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# NW-ROADMAP: Goal Planning **Wave**: CROSS_WAVE **Agent**: Architect (nw-solution-architect) or domain-appropriate agent ## Overview Dispatches expert agent to fill a pre-scaffolded YAML roadmap skeleton. CLI tools handle structure; agent handles content. Output: `docs/feature/{feature-id}/deliver/roadmap.json` ## Usage ```bash /nw-roadmap @nw-solution-architect "Migrate monolith to microservices" /nw-roadmap @nw-software-crafter "Replace legacy authentication system" /nw-roadmap @nw-product-owner "Implement multi-tenant support" ``` ## Execution Steps You MUST execute these steps in order. Do NOT skip any. 1. **Parse Parameters** — Extract agent name (after @, validated against agent registry), goal description (quoted string), and derive feature-id from goal in kebab-case (e.g., "Migrate to OAuth2" -> "migrate-to-oauth2"). Gate: agent name, goal, and feature-id all resolved. 2. **Scaffold Skeleton** — Run `des.cli.roadmap init` via Bash BEFORE invoking agent. Gate: CLI exits 0; stop and report error on non-zero exit. ```bash PYTHONPATH=~/.claude/lib/python $(command -v python3 || command -v python) -m des.cli.roadmap init \ --project-id {feature-id} \ --goal "{goal-description}" \ --output docs/feature/{feature-id}/deliver/roadmap.json ``` For complex projects add: `--phases 3 --steps "01:3,02:2,03:1"` Do NOT write the file manually. 3. **Invoke Agent** — Invoke the named agent via Task tool to fill skeleton TODO placeholders. Gate: agent completes witho...

Details

Author
nWave-ai
Repository
nWave-ai/nWave
Created
9 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

roadmap

Tracks features across their lifecycle in a live, per-repo roadmap — every RD, plan, and task and the lifecycle stage each is in. Layout-aware: a single plans/00-roadmap.md in flat layout, or a two-tier per-feature + portfolio roadmap under codeops/ in nested layout. Use when the user says "roadmap", "make_roadmap", "update_roadmap", "review_roadmap", "show_roadmap", "archive_roadmap", or "compact_roadmap". Covers six actions: make_roadmap (create + seed rows from disk), update_roadmap (re-infer stages, sync to disk, cascade to the portfolio), review_roadmap (read-only health check for drift/broken links), show_roadmap (read-only status overview — progress, stages, and next steps), archive_roadmap (move a completed feature to the archive), and compact_roadmap (slim a bloated roadmap: strip the legacy Notes log and trim fat cells). Detects the action from the user's phrasing or arguments and branches. The roadmap is the cross-session source of truth at the RD/plan altitude, above any single execution plan.

5 Updated 3 months ago
blendsdk
AI & Automation Listed

roadmap

Use when the user wants outcome-based delivery phases or exit criteria at docs/product/roadmap.md. Drafts or re-sequences the document. Triggers on "build the roadmap", "what are our delivery phases", "phase exit criteria". Requires product.md. Re-authoring is also how an existing roadmap.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not sequencing soundness. Do NOT use for epic breakdown or work paths (tasks), PRD (product), per-work-item technical design (tdd), tasks (tasks), or architecture detail (solution).

2 Updated 3 months ago
carinyaparc
AI & Automation Solid

roadmap

Plan and execute entire application builds. Generates phased delivery roadmaps, then executes them autonomously — phase by phase, committing at milestones, deploying, testing, and continuing until done or stuck. Modes: plan (generate roadmap), start (begin executing), resume (continue from where you left off), status (show progress). Triggers: 'roadmap', 'start building', 'resume the build', 'keep going', 'build the whole thing', 'execute the roadmap', 'what phase are we on'.

1,120 Updated 1 months ago
jezweb