master-plan

What problem does it solve? Large initiatives that span multiple work streams are hard to coordinate: single plans become unwieldy, dependencies between work streams get lost, and parallel contributors make conflicting assumptions about shared interfaces. This Skill manages MasterPlans — living coordination documents that decompose an initiative into independently implementable child ExecPlans with explicit dependency modeling. ## Core Features & Use Cases - Initiative Decomposition: Breaks large efforts into two to seven child ExecPlans grouped by functional concern, with hard, soft, and integration dependencies modeled explicitly. - Six Operating Modes: create, implement, status, update, discuss, and review — covering the full lifecycle from planning through execution to retrospective. - Provenance & ADR Integration: Records which model authored, revised, or reviewed each plan via append-only frontmatter entries, and promotes durable cross-plan decisions into Architecture Decision Records. - Use Case: You need to add a Kafka consumer pipeline spanning a data model, consumer logic, and an API endpoint. Run create mode to generate a MasterPlan in docs/masterplans/ plus self-contained child ExecPlans in docs/plans/, then implement them in dependency order with git trailers tracking every commit. ## Quick Start Ask the agent to create a master plan for your initiative, for example: create a master plan for adding a Kafka consumer pipeline with separate plans for the data model, consumer, and API endpoint.