What problem does it solve? Starting a Business Analysis initiative without an agreed approach leads to misaligned stakeholder expectations, ad-hoc change handling, and no visibility into which BABOK knowledge areas have been covered. This Skill structures the Business Analysis Planning & Monitoring knowledge area so the BA Plan, stakeholder engagement, and governance are defined before elicitation begins. ## Core Features & Use Cases - BA Plan Development: Choose between planned (upfront) and adaptive (iterative) approaches with documented justification based on domain stability, requirement volatility, and stakeholder availability. - Stakeholder Engagement & Governance: Build a stakeholder engagement matrix with RACI assignments, decision rights, change request thresholds, and sign-off rules. - Multi-KA Progress Tracking: Create a ba-progress.md artifact tracking the state of all six BABOK knowledge areas with routing history and requirement metrics. - Use Case: A business analyst starting a call center analytics project uses this Skill to agree with the sponsor on an adaptive approach, map SME and end-user engagement techniques, define change control thresholds, and initialize the BABOK progress tracker before moving to elicitation. ## Quick Start Ask the assistant to run ba-planning to create the BA Plan, stakeholder engagement approach, and ba-progress.md tracker for your current work package.