/nw-buddy |
nWave concierge — ask any question about methodology, project state, commands, migration, or troubleshooting. Read-only, contextual answers. |
nw-nwave-buddy |
[question] - Example: "What should I do next for rate-limiting?\ |
/nw-bugfix |
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD |
nw-functional-software-crafter, nw-software-crafter, nw-troubleshooter |
[bug-description] - Describe the defect observed |
/nw-continue |
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts. |
|
[feature-id] - Optional: omit to auto-detect from docs/feature/ |
/nw-deliver |
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation. |
nw-functional-software-crafter, nw-platform-architect, nw-software-crafter, nw-software-crafter-reviewer, nw-solution-architect, nw-troubleshooter |
[feature-description] - Example: "Implement user authentication with JWT" |
/nw-design |
Designs system architecture with C4 diagrams and technology selection. Use when defining component boundaries, choosing tech stacks, or creating architecture documents. |
nw-ddd-architect, nw-functional-software-crafter, nw-platform-architect, nw-software-crafter, nw-solution-architect, nw-system-designer |
[component-name] - Optional: --residuality --paradigm=[auto |
/nw-devops |
Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature. |
nw-acceptance-designer, nw-platform-architect |
[deployment-target] - Optional: --environment=[staging |
/nw-diagram |
Generates C4 architecture diagrams (context, container, component) in Mermaid or PlantUML. Use when creating or updating architecture visualizations. |
nw-solution-architect |
[diagram-type] - Optional: --format=[mermaid |
/nw-discover |
Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit. |
nw-product-discoverer, nw-product-owner |
[product-concept] - Optional: --interview-depth=[overview |
/nw-discuss |
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria. |
nw-platform-architect, nw-product-owner, nw-solution-architect |
[feature-name] - Optional: --phase=[jtbd |
/nw-distill |
Creates E2E acceptance tests in Given-When-Then format from requirements and architecture. Use when preparing executable specifications before implementation. |
nw-acceptance-designer, nw-acceptance-designer-reviewer, nw-platform-architect-reviewer, nw-product-owner-reviewer, nw-software-crafter, nw-solution-architect-reviewer |
[story-id] - Optional: --test-framework=[cucumber |
/nw-diverge |
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. |
nw-diverger, nw-diverger-reviewer, nw-product-owner, nw-researcher |
[feature-id] - Optional: --work-type=[new-product |
/nw-document |
Creates evidence-based documentation following DIVIO/Diataxis principles. Use when writing tutorials, how-to guides, reference docs, or explanations. |
nw-documentarist, nw-documentarist-reviewer, nw-researcher, nw-researcher-reviewer |
[topic/component] - Optional: --type=[tutorial |
/nw-execute |
Dispatches one unit of DELIVER work to a specialized agent for TDD execution. Runs a single roadmap.json step through the TDD cycle. |
nw-researcher, nw-software-crafter |
[agent] [feature-id] [step-id] - Example: @nw-software-crafter "auth-upgrade" "01-01" |
/nw-fast-forward |
Fast-forwards through remaining waves end-to-end without stopping for review between waves. |
|
[feature-description] - Optional: --from=[discuss |
/nw-finalize |
Archives a completed feature to docs/evolution/, migrates lasting artifacts to permanent directories, and cleans up the temporary workspace. Use after all implementation steps pass and mutation testing completes. |
nw-acceptance-designer, nw-platform-architect, nw-product-owner, nw-researcher, nw-software-crafter, nw-solution-architect |
[agent] [feature-id] - Example: @platform-architect "auth-upgrade" |
/nw-forge |
Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification. |
nw-agent-builder |
[agent-name] - Optional: --type=[specialist |
/nw-hotspot |
Git change frequency hotspot analysis — find the most-changed files in your codebase |
|
[--top=N] [--since=6m] [--json] [--rank report.md] [--detail file] |
/nw-mikado |
[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking |
nw-software-crafter |
[refactoring-goal] - Optional: --complexity=[simple |
/nw-mutation-test |
Runs feature-scoped mutation testing to validate test suite quality. Use after implementation to verify tests catch real bugs (kill rate >= 80%). |
nw-software-crafter |
[feature-id] - Optional: --threshold=[75 |
/nw-new |
Guided wizard to start a new feature. Asks what you want to build, recommends the right starting wave, and launches it. |
|
[feature-description] - Example: "Add rate limiting to the API gateway" |
/nw-optimize-tests |
Minimizes test count while preserving coverage. Detects byte-identical pairs, parametrize-inflation, language-guarantee tests, AST-shape tests, stale migration nets. Approval gate before any change. |
nw-test-optimizer, nw-test-optimizer-reviewer |
[scope] - Optional: a path (e.g. tests/des/unit/), a feature-id (auto-resolves to tests//), or omit for full unit suite. --reviewer to chain reviewer agent. |
/nw-refactor |
Applies the Refactoring Priority Premise (RPP) levels L1-L6 for systematic code refactoring. Use when improving code quality through structured refactoring passes. |
nw-software-crafter |
[target-class-or-module] - Optional: --level=[1-6] --method=[extract |
/nw-research |
Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing. |
nw-researcher |
[topic] - Optional: --research_depth=[overview |
/nw-review |
Dispatches an expert reviewer agent to critique workflow artifacts. Use when a roadmap, implementation, or step needs quality review before proceeding. |
nw-platform-architect, nw-platform-architect-reviewer, nw-software-crafter, nw-software-crafter-reviewer, nw-solution-architect, nw-solution-architect-reviewer |
[agent] [artifact-type] [artifact-path] - Example: @software-crafter task "roadmap.json" |
/nw-rigor |
Selects a quality-vs-token-consumption profile (lean, standard, thorough, exhaustive, custom, inherit) and persists it globally (~/.nwave/global-config.json) or per-project (.nwave/des-config.json). Use when tuning how much rigor wave commands apply. |
|
[profile] - Optional: lean, standard, thorough, exhaustive, custom, inherit. Omit for interactive selection. |
/nw-roadmap |
Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution. |
nw-product-owner, nw-software-crafter, nw-solution-architect |
[agent] [goal-description] - Example: @solution-architect "Migrate to microservices" |
/nw-root-why |
Root cause analysis and debugging |
nw-troubleshooter |
[problem-description] - Optional: --depth=[3 |
/nw-spike |
Runs a timeboxed spike to validate one core assumption before DESIGN. Use after DISCUSS when the feature involves a new mechanism, performance requirement, or external integration. |
nw-software-crafter, nw-solution-architect |
[feature-description] - Example: "wave-matrix -- derive feature status from pytest + filesystem\ |
