nacl-ba-context

Persist system context diagrams with stakeholders and data flows in Neo4j.

23|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-ba-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nacl-ba-context
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-ba-context
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-ba-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define system boundaries and automation scope directly in a Neo4j graph to ensure clear context, stakeholders, external entities, and data flows are modeled with traceability across BA activities.

Core Features & Use Cases

  • Interactive, phase-driven workflow to capture SystemContext, ExternalEntities, and DataFlows within Neo4j.
  • Graph-backed persistence using dedicated node types (SystemContext, Stakeholder, ExternalEntity, DataFlow) with MERGE semantics for idempotent updates.
  • Generates artifacts and diagrams from graph data to support system-context governance and stakeholder alignment.

Quick Start

Begin Phase 1 by answering the system scope questions to create the SystemContext in Neo4j.

Frequently Asked Questions about nacl-ba-context

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

FAQPage Schema
How do I define system boundaries and context in a Neo4j graph?

To define system boundaries in a Neo4j graph, use an interactive four-phase workflow to capture scope, stakeholders, external entities, and data flows. This creates dedicated graph nodes that ensure clear context and traceability across business analysis activities.

What is a graph-backed system context diagram and how does it work?

A graph-backed system context diagram models scope, stakeholders, external entities, and data flows as interconnected nodes in Neo4j. It uses MERGE semantics for idempotent updates, ensuring consistent traceability and enabling the generation of artifacts and diagrams for stakeholder alignment.

Do I need a Neo4j backend to model system context and data flows?

Yes, modeling system context and data flows requires a Neo4j graph backend and graph-query utilities. The system updates SystemContext, Stakeholder, ExternalEntity, and DataFlow nodes and relationships directly within the graph database.

How do I start creating a system context diagram for business analysis?

Begin creating a system context diagram by starting Phase 1 and answering system scope questions. This initial input creates the SystemContext node in Neo4j, which sets the foundation for subsequent phases capturing stakeholders, external entities, and data flows.

What is the best way to persist stakeholder and external entity data in a graph database?

The best way to persist stakeholder and external entity data is using dedicated node types with MERGE semantics for idempotent updates. This approach ensures repeated modeling operations do not create duplicate nodes, maintaining clean graph data.

Can I generate diagrams from system context data stored in Neo4j?

Yes, you can generate artifacts and diagrams directly from the system context data stored in Neo4j. These generated visualizations support system-context governance and facilitate stakeholder alignment by representing the persisted graph relationships.