ba-planning

Plans Business Analysis activities following BABOK Planning and Monitoring knowledge area.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill ba-planning-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ba-planning
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/ba-planning
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill ba-planning-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

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.

Frequently Asked Questions about ba-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Business Analysis Plan with BABOK?▼

Define the BA approach (planned versus adaptive) with justification, map planned activities to BABOK knowledge areas, list deliverables with acceptance criteria, and document stakeholder engagement and governance. This Skill guides each step and produces a ba-planning.md artifact from a template.

When should I use a planned versus adaptive BA approach?▼

Use a planned approach when the business domain is well known, requirements are stable, and late changes are costly. Use an adaptive approach when the domain is new, requirements are emergent, and stakeholders are highly available. Hybrid approaches combine upfront strategy with just-in-time specification.

What is a stakeholder engagement approach in business analysis?▼

It is a plan mapping each stakeholder's role, influence, interest, and availability to specific engagement techniques and frequency. High-influence, high-interest stakeholders are managed closely with regular involvement, while low-interest groups receive periodic updates.

Does BABOK require following knowledge areas in a fixed order?▼

No. BABOK is non-sequential; the six knowledge areas activate based on project needs. After planning, a routing table directs you to elicitation, strategy analysis, requirements analysis, requirements lifecycle, or solution evaluation depending on context.

When should I skip formal BA planning?▼

Skip it for very small projects with fully known scope where formal planning is disproportionate overhead, or when a BA Plan is already approved and only progress tracking needs updating. In those cases go directly to elicitation or update ba-progress.md.