nw-buddy-command-catalog

All /nw-* commands — what they do, when to use them, which agent they invoke. For the buddy agent to help users pick the right command.

322 stars

Best use case

nw-buddy-command-catalog is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

All /nw-* commands — what they do, when to use them, which agent they invoke. For the buddy agent to help users pick the right command.

Teams using nw-buddy-command-catalog should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/nw-buddy-command-catalog/SKILL.md --create-dirs "https://raw.githubusercontent.com/nWave-ai/nWave/main/nWave/skills/nw-buddy-command-catalog/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/nw-buddy-command-catalog/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How nw-buddy-command-catalog Compares

Feature / Agentnw-buddy-command-catalogStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

All /nw-* commands — what they do, when to use them, which agent they invoke. For the buddy agent to help users pick the right command.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Command Catalog

## Wave Commands (run in order per feature)

| Command | Wave | Agent | When to Use |
|---------|------|-------|-------------|
| `/nw-discover` | DISCOVER | product-discoverer (Scout) | Validate problem exists, customer interviews, opportunity mapping |
| `/nw-diverge` | DIVERGE | diverger (Flux) | Evaluate multiple solution approaches before committing |
| `/nw-discuss` | DISCUSS | product-owner (Luna) | Define user stories, journeys, acceptance criteria |
| `/nw-design` | DESIGN | system-designer, ddd-architect, solution-architect | Route to the right architect — system (scalability), domain (DDD), or application (components) |
| `/nw-devops` | DEVOPS | platform-architect | CI/CD, infrastructure, observability, deployment strategy |
| `/nw-distill` | DISTILL | acceptance-designer | Create executable acceptance tests (Given-When-Then) |
| `/nw-deliver` | DELIVER | software-crafter | Full implementation: roadmap -> execute -> finalize |

## Routing Commands

| Command | Purpose | When to Use |
|---------|---------|-------------|
| `/nw-new` | Guided wizard for new features | Starting something new — asks what you're building, recommends starting wave |
| `/nw-continue` | Resume in-progress feature | Returning to a feature — detects progress, starts at next wave |
| `/nw-fast-forward` | Run remaining waves without pausing | When you trust the agents to proceed without review between waves |

## DELIVER Inner Loop Commands (manual mode)

| Command | Purpose | When to Use |
|---------|---------|-------------|
| `/nw-execute` | Run single roadmap step | Implementing one step at a time (learning mode) |
| `/nw-roadmap` | Create implementation plan | Planning steps before execution |
| `/nw-review` | Expert review of artifacts | Quality check on roadmap, code, or step output |
| `/nw-mutation-test` | Test suite effectiveness | After implementation — verifies tests catch real bugs |
| `/nw-finalize` | Archive completed feature | After all steps pass — creates evolution document |

## Cross-Wave Commands (any time)

| Command | Agent | When to Use |
|---------|-------|-------------|
| `/nw-research` | researcher (Nova) | Investigate technologies, patterns, decisions needing evidence |
| `/nw-document` | documentarist + researcher | Create DIVIO-compliant documentation (tutorial, how-to, reference, explanation) |
| `/nw-diagram` | solution-architect | Generate C4 architecture diagrams (Mermaid/PlantUML) |
| `/nw-refactor` | software-crafter | Systematic refactoring using RPP levels L1-L6 |
| `/nw-bugfix` | troubleshooter + crafter | Root cause analysis -> regression test -> fix via TDD |
| `/nw-root-why` | troubleshooter | Root cause analysis (5 Whys) without fix |
| `/nw-hotspot` | (self) | Git change frequency analysis — find most-changed files |
| `/nw-rigor` | (self) | Set quality-vs-token profile (lean/standard/thorough/exhaustive) |
| `/nw-forge` | agent-builder (Zeus) | Create new specialized agents |
| `/nw-mikado` | software-crafter | Complex refactoring roadmaps with visual tracking (experimental) |
| `/nw-buddy` | buddy (Guide) | Ask any question about nWave — methodology, commands, project state |

> For the full authoritative command reference, read `docs/reference/commands/index.md`.

## Common User Scenarios -> Command

| User Says | Recommend |
|-----------|-----------|
| "I want to build something new" | `/nw-new` (wizard) or `/nw-discover` (if problem unclear) |
| "I'm not sure which approach to take" | `/nw-diverge` |
| "I need user stories for this feature" | `/nw-discuss` |
| "How should I architect this?" | `/nw-design` |
| "I need to set up CI/CD" | `/nw-devops` |
| "I need acceptance tests" | `/nw-distill` |
| "I'm ready to implement" | `/nw-deliver` |
| "I want to continue my feature" | `/nw-continue` |
| "I need to research X" | `/nw-research` |
| "I need documentation" | `/nw-document` |
| "Something is broken" | `/nw-bugfix` or `/nw-root-why` |
| "My code needs cleanup" | `/nw-refactor` |
| "How good are my tests?" | `/nw-mutation-test` |

Related Skills

nw-test-refactoring-catalog

322
from nWave-ai/nWave

Detailed refactoring mechanics with step-by-step procedures, and test code smell catalog with detection patterns and before/after examples

nw-command-optimization-workflow

322
from nWave-ai/nWave

Step-by-step workflow for converting bloated command files to lean declarative definitions

nw-command-design-patterns

322
from nWave-ai/nWave

Best practices for command definition files - size targets, declarative template, anti-patterns, and canonical examples based on research evidence

nw-buddy

322
from nWave-ai/nWave

nWave concierge — ask any question about methodology, project state, commands, migration, or troubleshooting. Read-only, contextual answers.

nw-buddy-wave-knowledge

322
from nWave-ai/nWave

Wave methodology knowledge for the buddy agent — what each wave does, its inputs and outputs, and how to route questions.

nw-buddy-ssot-knowledge

322
from nWave-ai/nWave

Single Source of Truth detection — where truth lives in an nWave repo and how to avoid contradicting it.

nw-buddy-project-reading

322
from nWave-ai/nWave

How the nWave buddy agent reads a project to answer questions — detection, order of inspection, and citation discipline.

nw-ux-web-patterns

322
from nWave-ai/nWave

Web UI design patterns for product owners. Load when designing web application interfaces, writing web-specific acceptance criteria, or evaluating responsive designs.

nw-ux-tui-patterns

322
from nWave-ai/nWave

Terminal UI and CLI design patterns for product owners. Load when designing command-line tools, interactive terminal applications, or writing CLI-specific acceptance criteria.

nw-ux-principles

322
from nWave-ai/nWave

Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.

nw-ux-emotional-design

322
from nWave-ai/nWave

Emotional design and delight patterns for product owners. Load when designing onboarding flows, empty states, first-run experiences, or evaluating the emotional quality of an interface.

nw-ux-desktop-patterns

322
from nWave-ai/nWave

Desktop application UI patterns for product owners. Load when designing native or cross-platform desktop applications, writing desktop-specific acceptance criteria, or evaluating panel layouts and keyboard workflows.