nacl-sa-architect

Decompose software systems into modules and bounded contexts from Neo4j BA data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decomposition is essential to manage complexity in large software systems. This Skill reads BA data from a Neo4j graph and assists in decomposing the system into modules (Bounded Contexts), building a Context Map, and identifying non-functional requirements. It helps users generate a coherent SA view of an evolving architecture directly from business artifacts.

Core Features & Use Cases

  • Graph-based decomposition: partition the system into modules and bounded contexts using BA data from the graph.
  • Context Map construction: determine dependencies, data ownership, and interaction patterns across modules.
  • NFR integration: model non-functional requirements and link them to corresponding modules and use cases.
  • SA-ready artifacts: produce Module and Requirement nodes in the graph for downstream SA activities.

Quick Start

Construct a graph-based architecture for a new project by importing BA data from Neo4j and generating modules, a context map, and NFRs in the SA graph.

Frequently Asked Questions about nacl-sa-architect

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

FAQPage Schema
How do I decompose a software system into bounded contexts using a graph database?

Decomposing a software system into bounded contexts involves reading business architecture data from a Neo4j graph and performing Cypher operations to partition the system into distinct modules. This graph-based decomposition identifies boundaries and produces a coherent software architecture view.

What is the best way to build a context map from existing business artifacts?

Building a context map from business artifacts is achieved by ingesting BA data from a Neo4j graph to determine dependencies, data ownership, and interaction patterns across modules. This process constructs a context map that models cross-module dependencies directly within the graph.

Can I integrate non-functional requirements into a graph-based architecture model?

You can integrate non-functional requirements into a graph-based architecture model by linking NFR nodes to corresponding modules and use cases in the Neo4j graph. This NFR integration ensures that architectural constraints are modeled alongside the bounded contexts.

Does architectural decomposition require existing data in the Neo4j graph?

Graph-based architectural decomposition requires existing BA data in the Neo4j graph. The process reads business artifacts from the graph to perform module partitioning and context mapping, relying on read and write Cypher operations against the BA subgraph.

What are the limitations of graph-driven module partitioning for software architecture?

Graph-driven module partitioning is limited by the quality and completeness of the BA data ingested into the Neo4j graph. If business artifacts lack sufficient detail, the context mapping and module decomposition will reflect those gaps, affecting the resulting SA graph accuracy.