nw-finalize

# NW-FINALIZE: Feature Completion and Archive **Wave**: CROSS_WAVE **Agent**: @nw-platform-architect (default) or specified agent ## Overview Finalize a completed feature: verify all steps done|create evolution document|migrate lasting artifacts to permanent directories|clean up temporary workspace. Agent gathers project data|analyzes execution history|writes summaries|migrates|cleans up. `docs/feature/{feature-id}/` is a **temporary workspace** — it exists during active nWave waves (DISCUSS through DELIVER). At finalize, artifacts with lasting value migrate to permanent directories; the rest is discarded. ## Usage ``` /nw-finalize @{agent} "{feature-id}" ``` ## Context Files Required - docs/feature/{feature-id}/deliver/roadmap.json - Original project plan - docs/feature/{feature-id}/deliver/execution-log.json - Step execution history ## Pre-Dispatch Gate: All Steps Complete Before dispatching, verify all steps are done — prevents archiving incomplete features. 1. **Parse execution log** — Read `docs/feature/{feature-id}/deliver/execution-log.json`. Gate: file readable. 2. **Verify completeness** — Check every step has status `DONE`. Gate: all steps DONE. 3. **Block or proceed** — If any step is not DONE, list incomplete steps with current status and halt. If all DONE, proceed to dispatch. Gate: zero incomplete steps before dispatch. ## Phases ### Phase A — Evolution Document 1. **Gather source data** — Read `execution-log.json`, `roadmap.json`, and all `*/wave-...