nacl-ba-handoff

Generate a BA-to-SA handoff package from a Neo4j graph.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BA→SA handoff generation from a Neo4j BA subgraph to produce a traceability matrix, automation scope, module suggestions, and coverage stats, enabling seamless cross-layer handoffs after user confirmation.

Core Features & Use Cases

  • Generates a four-section traceability matrix mapping BA steps to SA use cases, domain entities, system roles, and requirements.
  • Computes and presents an automation scope for automated steps, with candidate UC suggestions and priorities.
  • Proposes SA modules linked to ProcessGroups and creates handoff edges (AUTOMATES_AS, REALIZED_AS, MAPPED_TO, IMPLEMENTED_BY) after user confirmation.
  • Produces Phase 1–4 artifacts: Traceability Matrix, Automation Scope, Module Suggestions, and Coverage Stats to guide SA-planning.

Quick Start

Invoke the /nacl-ba-handoff command to generate a BA→SA handoff package from the Neo4j graph after user confirmation.

Frequently Asked Questions about nacl-ba-handoff

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

FAQPage Schema
How do I generate a BA to SA traceability matrix from a Neo4j graph?

Generate a BA to SA traceability matrix by mapping BA steps from your Neo4j graph to SA use cases, domain entities, system roles, and rules. This produces a structured traceability matrix artifact to guide SA-planning.

What is a BA to SA handoff package and what artifacts does it include?

A BA to SA handoff package is a set of Phase 1-4 artifacts including a traceability matrix, automation scope, module suggestions, and coverage stats. It maps BA steps to SA elements to enable seamless cross-layer handoffs.

How do I validate BA coverage and surface uncovered elements before SA planning?

Validate BA coverage by analyzing the Neo4j BA subgraph to compute coverage stats and surface uncovered elements. The process highlights gaps in BA step mapping to SA use cases, entities, roles, and rules.

Can I write traceability edges like AUTOMATES_AS and REALIZED_AS directly to Neo4j?

Yes, you can write handoff edges like AUTOMATES_AS, REALIZED_AS, MAPPED_TO, and IMPLEMENTED_BY directly to Neo4j. The system proposes these traceability relationships and commits them after user confirmation.

How do I compute automation scope and suggest use cases for automated BA steps?

Compute automation scope by identifying automated BA steps within the Neo4j graph and generating candidate use case suggestions with priorities. This creates an automation scope artifact for SA-planning.

What do I need to prepare before generating a BA to SA handoff from Neo4j?

You need a populated Neo4j graph containing BA subgraph data with mapped ProcessGroups, steps, and related elements. The Skill requires no additional dependencies to process the graph and produce handoff artifacts.