cross-cut-analysis

What problem does it solve?

Cross-chunk parallel work can fail or corrupt shared state when multiple chunks overlap files, implicitly depend on each other, or touch the same domains and resources without explicit coordination.

Core Features & Use Cases

• Boundary-driven risk analysis: Scans all chunk boundary.yaml files (allow, produces, consumes, touches_domains, tooling_deps, depends_on) to find coordination gaps.
• Five risk dimensions: Reports file-overlap conflicts, domain-tag conflicts, implicit produce/consume dependencies, concurrency hazards on shared state channels, and shared tooling requirements.
• Actionable structured output: Produces a YAML cross_cuts report with severity and recommendations, plus an audit event for traceability.

Quick Start

Run /mmp:cross-cut-analysis to generate a YAML cross-cut report for the current set of chunks and see which findings require serialization before dispatch.