/nw-rigor

name: nw-rigor
description: "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."
user-invocable: false
argument-hint: '[profile] - Optional: lean, standard, thorough, exhaustive, custom, inherit. Omit for interactive selection.'

NW-RIGOR: Quality Profile Selection

**Wave**: CROSS_WAVE | **Agent**: Main Instance (self) | **Command**: `/nw-rigor [profile]`

Overview

Interactive command to select a quality-vs-token-consumption profile. Persists choice to either `~/.nwave/global-config.json` (global scope) or `.nwave/des-config.json` (project scope) under the `rigor` key. All wave commands read this config to adjust agent models, review policy, TDD phases, and mutation testing.

You (the main Claude instance) run this directly. No subagent delegation.

**Note on TDD phase canons (dual-canon, ADR-025, 2026-05-07)**: the canonical TDD cycle is **3-phase v5** (`RED, GREEN, COMMIT`) as described in `nw-tdd-methodology`. The **legacy 5-phase v4** (`PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT`) is preserved for backward-compat audit-log replay of pre-2026-05-07 commits. The `.nwave/des-config.json` `tdd_phases` field accepts BOTH canons: writers of new logs may emit v5; the validator + schema (`step-tdd-cycle-schema.json`) dispatch on `schema_version` (`"5.0"` → canonical, anything else → legacy). The profile table below shows both canons side-by-side: pick v5 for new features, keep v4 only when extending a feature whose audit log was started under the legacy canon.

Profile Mappings (Single Source of Truth)

| Setting | lean | standard [recommended] | thorough | exhaustive | inherit | |--------------------|---------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------| | agent_model | haiku | sonnet | opus | opus | inherit | | reviewer_model | skip | haiku | sonnet | opus | haiku | | review_enabled | false | true | true | true | true | | double_review | false | false | true | true | false | | tdd_phases (v5 canonical, ADR-025) | [RED, GREEN] | [RED, GREEN, COMMIT] | [RED, GREEN, COMMIT] | [RED, GREEN, COMMIT] | [RED, GREEN, COMMIT] | | tdd_phases (v4 legacy, audit-replay) | [RED_UNIT, GREEN] | [PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT] | [PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT] | [PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT] | [PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT] | | refactor_pass | false | true | true | true | true | | mutation_enabled | false | false | false | true | false |

Behavior Flow

Mode Detection

• No argument -> Mode 1 (Interactive Selection)
• Argument is a preset name (lean, standard, thorough, exhaustive, inherit) -> Mode 2 (Quick Switch)
• Argument is `custom` -> Mode 3 (Custom Builder)

Mode 1: Interactive Selection (no argument)

Step 1: Welcome

Read `.nwave/des-config.json`. If missing or `.nwave/` directory absent -> error: "No nWave config directory foun