Analyze Consistency

Pre-execution validation: plan vs plan before coding.

Harness discovery

See ../nextstage-harness/references/harness-discovery.md. Load rules from {harness_root}/rules/*.md. Read architecture-rules.md first. Legacy: .cursor/rules/*.mdc only if {harness_root} is absent.

When to use

• After Gate 2 (scope_confirmed)
• User asks "analyze requirements" or "check consistency"
• After manual requirements.md edits

Prerequisites

• {product_root}/docs/versions/{version_san}/requirements.md exists
• Create version directory if missing before writing report