nw-execute

# NW-EXECUTE: Atomic Task Execution **Wave**: EXECUTION_WAVE | **Agent**: Dispatched agent (specified by caller) ## Overview Dispatch a single roadmap step to an agent. Orchestrator extracts step context from roadmap so agent never loads the full roadmap. ## Syntax ``` /nw-execute @{agent} "{feature-id}" "{step-id}" ``` ## Context Files Required - `docs/feature/{feature-id}/deliver/roadmap.json` — Orchestrator reads once, extracts step context - `docs/feature/{feature-id}/deliver/execution-log.json` — Agent appends only (never reads) ## Rigor Profile Integration Before dispatching the agent, read rigor config from `.nwave/des-config.json` (key: `rigor`). If absent, use standard defaults. - **`agent_model`**: Pass as `model` parameter to Agent tool. If `"inherit"`, omit `model` (inherits from session). - **`tdd_phases`**: If `["RED_UNIT", "GREEN"]` (lean), modify the TDD_PHASES section in the DES template to only include those 2 phases. Remove PREPARE/RED_ACCEPTANCE/COMMIT instructions. - **`refactor_pass`**: If `false`, skip COMMIT phase refactoring instructions. ## Dispatcher Workflow 1. **Parse Parameters** — Extract agent name, feature ID, and step ID from invocation. Gate: all three parameters present and non-empty. 2. **Load Rigor Profile** — Read `.nwave/des-config.json` key `rigor` (default: standard if absent). Gate: config loaded or default applied. 3. **Validate Context Files** — Confirm `docs/feature/{feature-id}/deliver/roadmap.json` and `execution-log...