Skip to main content
ClaudeWave
Skill542 estrellas del repoactualizado 2d ago

nw-buddy-command-catalog

The nw-buddy-command-catalog is a reference guide mapping all nWave slash commands to their corresponding agents, waves, and use cases. It documents discovery through delivery workflows, routing commands for feature initiation, DELIVER phase granular controls, and cross-wave utilities like research and documentation. Use this catalog to help users select the appropriate command based on their current product development stage and specific need.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/nWave-ai/nWave /tmp/nw-buddy-command-catalog && cp -r /tmp/nw-buddy-command-catalog/nWave/skills/nw-buddy-command-catalog ~/.claude/skills/nw-buddy-command-catalog
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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` |
nw-ab-critique-dimensionsSkill

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

nw-abr-critique-dimensionsSkill

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

nw-ad-critique-dimensionsSkill

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof

nw-agent-creation-workflowSkill

Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement

nw-agent-testingSkill

5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance

nw-architectural-styles-tradeoffsSkill

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

nw-architecture-patternsSkill

Comprehensive architecture patterns, methodologies, quality frameworks, and evaluation methods for solution architects. Load when designing system architecture or selecting patterns.

nw-at-completeness-checkSkill

Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.