What problem does it solve? Planning a feature that spans many backend apps and frontend modules often produces fragmented plans with conflicting assumptions about shared interfaces. This Skill fans a requirements document or Jira ticket out to per-domain planners and reconciles their outputs into one conflict-free, ordered execution plan. ## Core Features & Use Cases - Domain Decomposition: Maps requirements to a registry of domains (booking, payments, attribution, auth, etc.) with a hard cap of 8, producing a brief per domain with input/output contracts. - Parallel Domain Planning: Launches one planner agent per domain, each producing an execution plan with file-level changes, risk ratings, migrations, tests, and explicit assumptions about other domains. - Merge Reconciliation: Builds an integration matrix across domains, labels conflicts (C-01, C-02...), resolves them, and emits a unified plan with cross-domain execution ordering and an integration test checklist. - Use Case: Given a Jira ticket like RGDEV-205 for checkout discounts, the pipeline identifies Booking, Attribution, and Payments domains, plans each in parallel, resolves the discount-field ownership conflict, and outputs a sequenced unified plan. ## Quick Start Ask the assistant to run /domain-planning on a Jira ticket key, a requirements document path, or a plain feature description to generate a unified multi-domain implementation plan.
