nw-roadmap

Generates a structured roadmap.json with phases, acceptance criteria, and TDD steps from a goal.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-roadmap
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-roadmap
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams plan and communicate a structured, phased roadmap for a feature goal, including acceptance criteria and test-driven development steps, before starting implementation.

Core Features & Use Cases

  • Generate a pre-scaffolded roadmap skeleton for a feature.
  • Derive a feature-id from the goal and organize phased steps, acceptance criteria, and TDD guidance.
  • Use during upfront planning to align stakeholders and drive implementation.

Quick Start

Run the nw-roadmap tool with an agent and a goal to generate docs/feature/{feature-id}/deliver/roadmap.json.

Frequently Asked Questions about nw-roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a structured feature roadmap with acceptance criteria before implementation?

To generate a structured feature roadmap, provide a high-level goal to produce a roadmap.json containing phased milestones, acceptance criteria, and TDD steps. This automates upfront planning during project scoping to align stakeholders before implementation begins.

What is the best way to plan phased milestones using test-driven development steps?

Planning phased milestones with TDD steps is best handled by generating a structured roadmap skeleton from a feature goal. This process derives a feature-id and organizes the corresponding test-driven development guidance and acceptance criteria into a validated JSON format.

How do I scaffold a roadmap.json file for a new software feature?

You scaffold a roadmap.json file by running the roadmap generation tool with a high-level goal and an agent. It creates a deterministic skeleton under docs/feature/{feature-id}/deliver/ and uses agent-driven content filling to populate the phased steps.

Does roadmap planning require dependencies or specific components to generate feature delivery steps?

Roadmap planning for feature delivery requires no external dependencies or specific components. It operates independently to validate your structured steps against the roadmap schema, ensuring the generated milestones and acceptance criteria meet the required format.

Can I use this approach for upfront architecture discussions and project scoping?

Yes, you can use this approach for upfront architecture discussions and project scoping. It produces a pre-scaffolded roadmap skeleton with phased milestones and TDD guidance specifically to drive alignment and implementation planning during early project phases.

Why does feature roadmap planning need validation against a roadmap schema?

Feature roadmap planning needs validation against a roadmap schema to ensure deterministic skeleton generation and structural integrity. This validation guarantees that the agent-driven content filling produces correctly formatted milestones and acceptance criteria for the feature delivery process.