current_state

Document the as-is state across eight BABOK 6.1 elements with root cause analysis.

40|15|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/chaussky/ainalyst --skill current-state-chaussky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: current_state
Source: https://github.com/chaussky/ainalyst/tree/main/skills/current_state
Command: npx skills add https://github.com/chaussky/ainalyst --skill current-state-chaussky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Skill provides a structured approach to analyze the current state (as-is) across the 8 elements defined in BABOK 6.1, producing a clear description of the current state and the business needs that justify change, along with a traceable path to future states.

Core Features & Use Cases

  • Scope and contract the analysis with a defined 6.1 scope (scope_current_state)
  • Iterative data capture for each element (capture_current_state_element)
  • Root Cause Analysis to identify underlying drivers (run_root_cause_analysis)
  • Formalize and register Business Needs (define_business_needs)
  • Completeness check to ensure all relevant elements are captured (check_current_state_completeness)
  • Finalize and save a readable 6.1 report (save_current_state)

Quick Start

Initiate scope_current_state, capture all 8 elements, run RCA as needed, define business needs, check completeness, and save the final 6.1 report.

Frequently Asked Questions about current_state

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

FAQPage Schema
How do I document the as-is state for business analysis projects?

To document the as-is state, you iteratively capture data across 8 current-state elements within a BABOK-aligned framework, producing a structured report that defines scope and formalizes business needs.

What is current state analysis used for in BABOK methodologies?

Current state analysis is used to identify root causes, formalize business needs, and establish traceability. It provides a clear baseline description of existing operations to justify and drive effective change planning.

How do I run a root cause analysis and link it to business needs?

You run root cause analysis after capturing current-state elements to identify underlying drivers. These drivers are then formalized and registered as business needs, ensuring traceability from the RCA directly to the justification for change.

Does this approach require predefined scope before capturing current state elements?

Yes, you must first scope and contract the analysis using a defined scope parameter. This ensures structured data capture remains focused across the 8 current-state elements before running completeness checks and saving the final report.

What's the best way to ensure completeness when analyzing the as-is state?

The best way to ensure completeness is to run a dedicated completeness check after iteratively capturing all 8 current-state elements. This verifies that all relevant structural data points are documented before finalizing the report.

Can I use this structured approach for scope definition and RCA across different BA projects?

Yes, this approach applies to BA projects requiring scope definition, root cause analysis (RCA), and formalizing business needs. It satisfies structured data capture and traceability requirements within a standardized BABOK-aligned framework.