Orchestrate full-stack TDD from business analysis to release
NaCl is a graph-first software-delivery framework for Claude Code and Codex, storing analysis and evidence in Neo4j.
2.27.0Add to Favorites
Why it matters
NaCl automates the entire software development lifecycle-from capturing business requirements in a Neo4j graph through TDD development, code review, QA, and production release-ensuring every requirement is traceable and every use case is atomically committed with strict quality gates.
Outcomes
What it gets done
Extract business processes, entities, and rules into a queryable Neo4j graph for impact analysis and traceability
Generate backend and frontend code using test-driven development with atomic commits per use case
Run two-level QA with local static analysis during development and E2E Playwright tests on staging
Orchestrate planning, development, review, testing, and deployment with evidence-blocking gates that halt on missing verification
Install
Add it to your toolbox
Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/itsalt-nacl | bash After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.
Reports
Agent outcome reports
No reports yet
Steps
Steps in the chain
Overview
NaCl is a graph-first software-delivery framework for Claude Code and Codex that stores business analysis, system specifications, and delivery evidence in a per-project Neo4j knowledge graph. It runs 59 root skills across business-analysis, system-analysis, and TeamLead layers, gating closure on verification evidence rather than accepting missing evidence as explanation. Use it when a team wants analysis and delivery work tracked in one queryable, evidence-gated graph instead of scattered documents. Install through one Claude or Codex channel per machine to avoid duplicate skills shadowing each other.
What it does
NaCl is a graph-first software-delivery framework for Claude Code and Codex. Business analysis, system specifications, delivery evidence, and traceability live in a per-project Neo4j knowledge graph instead of a disconnected pile of documents, so impact analysis and traceability become queryable graph operations rather than manual document searches. The framework ships 59 root skills organized by layer: nacl-ba-* (14, business analysis - processes, entities, roles, rules, glossary, validation), nacl-sa-* (10, system analysis - architecture, domain model, use cases, UI, roles, validation), nacl-tl-* (26, TeamLead - planning, TDD, review, QA, deployment, release, recovery), plus 6 core utilities and 3 deterministic Markdown-to-graph migration skills. Since 2.8.0, NaCl treats missing verification evidence as a blocking gate rather than explanatory prose: closure refuses terminal states in {UNVERIFIED, BLOCKED, FAILED, NOT_RUN}, with only signed project exceptions or a bounded emergency procedure able to bypass it. It is MIT licensed, copyright ITSalt 2026.
When to use - and when NOT to
Use NaCl when a team wants business analysis, system analysis, and delivery work to write into a shared, queryable graph with atomic delivery - each use case developed, tested, reviewed, and shipped as one bounded unit - and two-level QA, local code verification before staging end-to-end verification. Choose the Codex Desktop Skills-only card once it is published for a UI-only install, Claude Code Desktop's marketplace plugin, or Claude Code CLI's repository-backed compatibility channel - but choose only one Claude channel per machine, since a dual install causes duplicate skills to shadow one another (the 2.24.0 SessionStart check warns about this). Do NOT expect NaCl to provide a managed graph or public MCP service: each project gets its own Neo4j 5 Community container, and a developer with access to a Neo4j server is treated as able to access every project database hosted there - project_scope is routing and provenance, not an authorization control, so access to another server must be granted separately.
Inputs and outputs
Input is business-analysis and system-analysis work driven through the layer skills, plus existing BA/SA Markdown documents that nacl-migrate can convert into the graph using deterministic parsing with adapters for supported layouts - it does not ask an LLM to invent graph facts. Output is the populated Neo4j knowledge graph, nodes and relationships for processes, entities, roles, rules, and use cases, rendered Markdown and Mermaid artifacts via nacl-render, and verification evidence gating each closure. A project's graph can be moved to another machine through a one-shot encrypted export/import handover, separate from plugin installation, preserving the per-project graph boundary.
Integrations
nacl-init → nacl-ba → nacl-sa → nacl-tl → nacl-verify
The ten Codex public conductors are nacl-ba, nacl-diagnose, nacl-fix, nacl-goal, nacl-init, nacl-migrate, nacl-publish, nacl-sa, nacl-tl, and nacl-verify, routing to an internal skill catalog rather than exposing implementation leaves directly. Claude packaging routes work to seven cognitive profiles: strategist (Opus, architecture/validation/deep review), analyst (Sonnet, domain modelling), developer (Sonnet, TDD code generation), verifier (Sonnet, testing and contract verification), operator (Sonnet, Git/CI/CD/publishing/migration), scout (Haiku, fast lookups), and diagnostician (Opus, diagnose-and-spec for bounded fixes). Optional integrations are Docmost, which publishes analysis and specification artifacts via nacl-publish, and YouGile, an optional project-management board - neither replaces the Neo4j graph as the analysis source of truth. A local NaCl Analyst Tool web application shows graph synchronization state with Regenerate, Sync, and Analyze actions, and a single daemon can serve multiple initialized projects. Requirements are Codex Desktop or Claude Code, Docker and Docker Compose for a local graph or access to a separately operated VPS for a remote one, Node.js 20+ for the Codex Skills-only bootstrap, and Git 2.30+ with Node.js 18+ for repository-backed development.
Who it's for
Teams running structured software delivery through Claude Code or Codex who want business analysis, system specifications, and delivery evidence tracked in one queryable graph with atomic, evidence-gated delivery, rather than scattered across separate documents - particularly teams that need traceability between requirements, use cases, and shipped code.
Source README
NaCl
NaCl is a graph-first software-delivery framework for Claude Code and Codex. Business analysis, system specifications, delivery evidence, and traceability live in a Neo4j knowledge graph instead of a disconnected document pile.
Choose the runtime channel
| Runtime | Ordinary installation | Status |
|---|---|---|
| Codex Desktop | One official NaCl Skills-only card from Plugins | Bootstrap-first bundle is being prepared; the official listing is not published yet |
| Claude Code Desktop | NaCl marketplace plugin | Supported by the current 2.24.0 package |
| Claude Code CLI | Repository-backed Claude skills | Supported compatibility channel |
After publication, the normal Codex path is one UI installation of the
Skills-only card. Its ten public conductors include nacl-init; packaged
scripts then create or connect the selected project's Neo4j Community stack
and project-local MCP configuration. GitHub remains a source, release, audit,
and support channel, not a mandatory second installation. The existing Git
marketplace/full-plugin and symlink layouts remain development and
compatibility channels. See Codex installation.
Install in Codex Desktop
When the official listing is published, open Plugins, select the verified NaCl Skills-only card, install it once, grant only the permissions shown by Codex, and open a new task in the project you want to initialize. Do not use a saved package path from another computer.
The official card is not published yet. The immutable Git/full-plugin release remains the verified pre-publication compatibility channel. Follow the Codex installation guide for the exact current availability and do not install a similarly named third-party card.
Initialize the first Codex project
In a new Codex task opened at the intended project root, invoke nacl-init.
It first performs a read-only prerequisite check and presents the exact files,
Docker resources, downloads, ports, secret references, and
.codex/config.toml changes.
Denial must leave the project unchanged.
After explicit confirmation, the bundled scripts create or connect the
per-project graph, install the pinned checksum-verified neo4j-mcp, and merge
the project's mcp_servers entry in .codex/config.toml without overwriting
unrelated servers. The current task then stops: open a new task in the same
project so Codex can discover the newly created project MCP. Initialization
is VERIFIED only after MCP
handshake, graph/schema health, a named read, a separately confirmed write
canary, and read-back succeed.
The package-level nacl_installation_doctor belongs only to the Git/full-plugin
compatibility channel; it is not a prerequisite for the official Skills-only
journey. See the Quick Start.
Graph model
Each project gets its own Neo4j 5 Community container and durable volumes. /nacl-init can create it locally, connect to a project container on a reachable VPS, or register an existing connection. Local Docker remains the default.
The server is the current authorization boundary: a developer who has access
to a Neo4j server is treated as able to access every project database hosted
there. project_scope selects and records the logical project; it is routing
and provenance, not an authorization control. Access to another server must be
granted separately. NaCl does not provide a managed graph or public MCP
service.
Key concepts
- Graph-first analysis. Processes, entities, roles, rules, and use cases are Neo4j nodes and relationships, so impact analysis and traceability are queryable.
- Configurable language. An explicit
--lang=enor--lang=ruwins, thenproject.langinconfig.yaml, then the layer default. BA and SA default to Russian; TL defaults to English. - Atomic delivery. Each use case is developed, tested, reviewed, and shipped as one bounded unit.
- Two-level QA. Local code verification precedes staging E2E verification.
- Config-driven operation.
config.yamlcontrols Git strategy, graph connection, project identity, and optional integrations.
Release foundation and strict mode
The 2.10.0 goal-protocol foundation added nacl-goal, the GOAL_PROOF wire format, the wave, fix, validate, and reopened-drain aliases, structured refusals, and a permissions denylist. See the goal command guide.
Since 2.8.0, NaCl has used evidence-blocking gates instead of treating missing evidence as explanatory prose. Closure refuses terminal states in {UNVERIFIED, BLOCKED, FAILED, NOT_RUN}. Removed skip flags cannot bypass this rule; the retained --skip-e2e has explicit scope. Older projects should start with project-gap-closure.md and use only signed exceptions or the bounded emergency procedure.
What's inside the framework
Root skills follow nacl-{layer}-{action}:
| Category | Prefix | Count | Responsibility |
|---|---|---|---|
| Business analysis | nacl-ba-* |
14 | Processes, entities, roles, rules, glossary, and validation |
| System analysis | nacl-sa-* |
10 | Architecture, domain model, use cases, UI, roles, and validation |
| TeamLead | nacl-tl-* |
26 | Planning, TDD, review, QA, deployment, release, and recovery |
| Utilities | nacl-* |
6 | Core helpers, rendering, publishing, initialization, goals, and postmortems |
| Migration | nacl-migrate-* |
3 | Deterministic Markdown-to-graph migration |
| Total | 59 | Root Claude/repository inventory |
The host packages intentionally expose different surfaces: Claude Desktop has 53 invocable skills, while Codex has 10 public conductors over a generated 60-skill internal catalog.
Workflow
The ten Codex public skills are nacl-ba, nacl-diagnose, nacl-fix, nacl-goal, nacl-init, nacl-migrate, nacl-publish, nacl-sa, nacl-tl, and nacl-verify. They route work to the internal skill catalog rather than exposing implementation leaves as the primary UI.
nacl-init → nacl-ba → nacl-sa → nacl-tl → nacl-verify
Strict mode is evidence-blocking: BLOCKED, FAILED, NOT_RUN, and UNVERIFIED halt closure. The only sanctioned exceptions are signed project exceptions and the bounded emergency process described in the strict-mode references.
Claude Code 2.24.0
The current Claude package remains fully supported. Claude Code Desktop installs the marketplace plugin from the app UI or Claude plugin commands; Claude Code CLI can use the repository-backed compatibility channel. Choose one Claude channel per machine so duplicate skills do not shadow one another. The 2.24.0 SessionStart check warns about a dual install.
Claude Desktop ships 53 invocable skills and seven agent profiles. Repository-backed Claude Code retains the complete 59 root skills. The /goal wrapper and repository-only migration/postmortem utilities remain outside the Desktop bundle where their host assumptions do not apply.
Optional integrations
- Docmost publishes analysis and specification artifacts with
nacl-publish. - YouGile supplies an optional project-management board and task integration.
Neither integration replaces the Neo4j graph as the analysis source of truth.
Architecture and packages
NaCl keeps host-specific packaging separate from methodology:
- root
nacl-*sources andplugin/build the Claude package; plugins/nacl/is the generated Git/full-plugin compatibility bundle;- the dedicated Skills-only builder produces the self-contained public upload tree from Codex sources without a package-level MCP binding;
plugins/nacl/resources/package-index.jsonremains the full-plugin Codex inventory contract;graph-infra/is copied per project by initialization;docs/contains the shared operational contract.
See Architecture, Configuration, and Workflows.
Agent architecture
Claude packaging routes work to six cognitive profiles and one diagnostic sub-agent:
| Agent | Model | Responsibility |
|---|---|---|
| strategist | Opus | Architecture, validation, and deep review |
| analyst | Sonnet | Domain modelling and structured content |
| developer | Sonnet | TDD code generation and fixes |
| verifier | Sonnet | Testing and contract verification |
| operator | Sonnet | Git, CI/CD, publishing, and migration orchestration |
| scout | Haiku | Fast lookups and status queries |
| diagnostician | Opus | Diagnose-and-spec phase of bounded fixes |
The Codex package does not promise Claude model identities; its public conductors preserve the same responsibility boundaries. See Agent Architecture.
Migration from Markdown
Existing BA/SA Markdown can be converted into the graph through the public nacl-migrate conductor. The underlying migration uses deterministic parsing with adapters for supported document layouts; it does not ask an LLM to invent graph facts. See Migration.
Graph handover
Moving a project graph to another machine is a one-shot encrypted export/import operation. It is separate from plugin installation and preserves the per-project graph boundary. See Handover.
NaCl Analyst Tool
The Analyst Tool is a local web application for boards in graph-infra/boards/. It shows graph synchronization state and provides Regenerate, Sync, and Analyze actions through itsalt-pinch. The old standalone excalidraw and excalidraw-room containers are no longer required.
A single daemon can serve multiple initialized projects registered in the NaCl project registry; the UI project selector changes the active project without restarting the daemon. See Analyst Tool and its multi-project setup.
Project structure
NaCl/
.claude/agents/ Claude cognitive profiles
nacl-ba-*/ 14 BA root skills
nacl-sa-*/ 10 SA root skills
nacl-tl-*/ 26 TL root skills
nacl-migrate-*/ 3 deterministic migration skills
nacl-core/ shared graph and language helpers
nacl-render/ Markdown and Mermaid rendering
nacl-publish/ Docmost publishing
nacl-init/ per-project initialization
graph-infra/ Neo4j template copied per project
plugin/ generated Claude Desktop artifact
.claude-plugin/ Claude marketplace manifest
plugins/nacl/ generated Codex Git/full-plugin compatibility artifact
analyst-tool/ local board and graph UI
docs/ shared documentation
Inventory
The repository contains 59 root NaCl skills. The public Skills-only bundle exposes 10 self-contained conductors and carries their required internal workflow closure. The Git/full-plugin compatibility package contains the generated 60-skill catalog and 25 package MCP tools; those package tools are not a prerequisite or advertised runtime surface of the official Skills-only journey. See Skills Reference.
Requirements
- Codex Desktop or Claude Code;
- Docker and Docker Compose for a local graph;
- access to a separately operated VPS when using a remote graph;
- Node.js 20+ for the Codex Skills-only project bootstrap;
- Git 2.30+ and Node.js 18+ for repository-backed development and tooling.
The ordinary Codex plugin install itself is a UI operation. A user should not need a source checkout, terminal command, local marketplace folder, or machine-specific path.
Documentation
| Document | Purpose |
|---|---|
| Quick Start | Installation choice, dry run, and first project |
| Codex plugin | Public surface, permissions, and limits |
| Graph Setup | Local and VPS Neo4j modes |
| Skills Guide | Choose the correct public conductor |
| Skills Reference | Exact public and internal inventory |
| Configuration | config.yaml, routing, and secrets |
| Migration | Deterministic Markdown-to-graph migration |
| Handover | Encrypted graph transfer between machines |
Skills in this collection
- nacl-ba: Route NaCl business analysis across context, processes, entities, roles, rules, workflows, validation, sync, and handoff. Use for graph-first BA work. - SKILL.md
- nacl-diagnose: Diagnose NaCl project health, drift, status, reconciliation, or next work using read-only evidence and actionable closed outcomes. - SKILL.md
- nacl-fix: Diagnose and repair a bounded NaCl defect with spec-first classification, a regression test, verification, and honest status propagation. - SKILL.md
- nacl-goal: Plan or conduct a bounded NaCl objective with explicit checks and closed statuses. Use for multi-step goals and resumable orchestration. - SKILL.md
- nacl-init: Inspect or initialize a NaCl project with a per-project Neo4j Community graph and project-local MCP. Use for first setup, bootstrap, and repair planning. - SKILL.md
- nacl-migrate: Plan or execute confirmed NaCl methodology migrations for legacy, BA, or SA artifacts with backups, validation, and read-back. - SKILL.md
- nacl-publish: Render, package, ship, release, deploy, or publish NaCl outputs with explicit external-write authorization and verified evidence. - SKILL.md
- nacl-sa: Route NaCl system analysis across architecture, domains, roles, use cases, UI, features, validation, and finalization. Use for graph-first SA work. - SKILL.md
- nacl-tl: Route NaCl team-lead work across intake, planning, development, review, QA, status, release, and deployment. Use for graph-aware delivery work. - SKILL.md
- nacl-verify: Verify NaCl code, tests, QA, synchronization, review evidence, or stubs without converting missing runtime proof into success. - SKILL.md
- nacl-ba-full: Coordinate complete NaCl BA graph creation through phased Codex orchestration with explicit handoff contracts and user confirmation gates. Use when creating a full BA graph, complete business analy... - SKILL.md
- nacl-core: Shared NaCl conventions for Codex-adapted skills: graph configuration, Neo4j tool assumptions, schema locations, ID conventions, Excalidraw board conventions, confirmation gates, and verification v... - SKILL.md
- nacl-goal: Prepare and validate NaCl
/goalaliases, GOAL_PROOF checks, structured refusals, and preview output for compatibility with/nacl-goal. Covers the autonomy-by-defaultintake(single-PR) and `c... - SKILL.md - nacl-init: Initialize or refresh a NaCl project for Codex by creating project configuration, graph infrastructure files, project registry entries, and optional Codex-readable guidance. Use when setting up a n... - SKILL.md
- nacl-migrate-sa: Migrate old-methodology SA Markdown into the NaCl graph with deterministic parsers, SA-internal edges, and BA-to-SA handoff links. Use when importing architecture, domain, role, use case, interface... - SKILL.md
- nacl-migrate: Orchestrate one-time migration from old Markdown BA/SA artifacts into the graph-based NaCl methodology. Use when migrating a project to the graph, importing old-methodology docs, comparing rendered... - SKILL.md
- nacl-publish: Publish NaCl graph-derived Markdown and board artifacts to external documentation targets. Use when publishing graph docs, syncing Docmost pages, generating or linking boards, previewing publish sc... - SKILL.md
- nacl-sa-architect: Decompose a NaCl system into modules, context-map dependencies, and NFRs in the SA graph. Use when the user asks to design architecture, define bounded contexts, add a module, create a system overv... - SKILL.md
- nacl-sa-full: Coordinate complete NaCl SA graph specification through phased Codex orchestration with explicit handoff contracts and user confirmation gates. Use when creating a full SA specification from BA gra... - SKILL.md
- nacl-sa-validate: Validate NaCl SA graph consistency, connectivity, requirements, form-domain traceability, UC-form coverage, cross-module rules, feature requests, staleness closure, decision provenance, screen stat... - SKILL.md
- nacl-tl-conductor: Coordinate NaCl TL batch workflow from intake scope through planning, development, verification, and delivery gates using explicit Codex orchestration contracts. Use when coordinating graph-aware b... - SKILL.md
- nacl-tl-core: Shared NaCl TeamLead references for Codex-adapted TL skills: task contracts, bug-fix classification, TDD workflow, documentation synchronization, changelog format, review rules, and stub tracking.... - SKILL.md
- nacl-tl-fix: Repair NaCl TL defects with spec-first analysis, strict RED-first regression testing, documentation synchronization before code when behavior contracts changed, graph-aware UC discovery, validation... - SKILL.md
- nacl-tl-full: Coordinate NaCl TL full lifecycle execution from graph-backed waves and tasks through development, review, verification, and final reporting with explicit Codex contracts. Use when running the full... - SKILL.md
- nacl-tl-intake: Triage and decompose user requests with graph-aware classification into features, bugs, and tasks. Use when a request contains multiple changes, unclear work type, graph context is needed, or when... - SKILL.md
- nacl-tl-next: Recommend the next actionable NaCl TL task using graph Task/Wave data with file fallback. Use when asking what to work on next, filtering by phase or wave, listing candidates, or when the user says... - SKILL.md
- nacl-tl-plan: Create NaCl TL implementation plans from graph SA specifications, including waves, backend and frontend tasks, technical tasks, API contracts, and TL tracking files. Use when planning implementatio... - SKILL.md
- nacl-tl-release: Coordinate NaCl release readiness, verification evidence, production deploy checks, changelog, and release reporting. Use when preparing or executing a release, promoting staging to production, or... - SKILL.md
- nacl-tl-reopened: Process reopened NaCl TL items from an issue tracker or manual description, reproduce the failure, route repair through spec-first fixing, verify review and stub gates, handle shipping gates, and r... - SKILL.md
- nacl-tl-review: Review NaCl TL implementation against task specs, API contracts, tests, stubs, and quality checklists. Use when reviewing backend, frontend, or full UC/TECH implementation, requesting changes, appr... - SKILL.md
- nacl-tl-ship: Commit, push, create pull requests, and update delivery metadata for NaCl TL work after required checks pass. Use when shipping code, creating a PR, pushing a feature branch, finishing development,... - SKILL.md
- nacl-ba-analyze: Анализ Excalidraw-доски бизнес-процесса: полнота, diff со snapshot, сравнение с Neo4j-графом. Используй когда пользователь просит: проанализировать доску, проверить доску, найти проблемы на доске,... - SKILL.md
- nacl-ba-context: Define system boundaries in Neo4j graph: scope, stakeholders, external entities, data flows.- all data stored as graph nodes and edges. Use when: define system scope with graph, system context diag... - SKILL.md
- nacl-ba-entities: Catalog business entities in Neo4j: stereotypes, attributes, states, CRUD matrix.Use when: model entities with graph, create entity catalog, or the user says "/nacl-ba-entities". - SKILL.md
- nacl-ba-from-board: Orchestrator skill: unified BA-board workflow combining import_doc + analyze + sync. Creates boards, imports client documents, analyzes completeness, syncs to Neo4j graph. Invocation: /nacl-ba-from... - SKILL.md
- nacl-ba-full: Full BA model creation in Neo4j via 10-phase orchestration. Chains all nacl-ba-* skills sequentially with user confirmation gates.Use when: create complete BA model with graph, full business analys... - SKILL.md
- nacl-ba-glossary: Build ubiquitous language glossary in Neo4j: terms, definitions, synonyms, links.Use when: create glossary with graph, define terms, or the user says "/nacl-ba-glossary". - SKILL.md
- nacl-ba-handoff: Generate BA→SA handoff package from Neo4j: traceability matrix, automation scope, module suggestions, coverage stats. Creates cross-layer edges after user confirmation.Use when: prepare BA→SA hando... - SKILL.md
- nacl-ba-import-doc: Parse a client document (DOCX/PDF/XLSX/text) and place extracted business-process elements onto an Excalidraw board with swimlanes, confidence colors, and customData. Invocation: /nacl-ba-import-do... - SKILL.md
- nacl-ba-process: Build business process map in Neo4j: process groups, processes, links, roles.- all data stored as graph nodes and edges. Use when: map processes with graph, create process map, or the user says "/n... - SKILL.md
- nacl-ba-roles: Identify and describe business roles in Neo4j: departments, responsibilities, role-process matrix.Use when: define roles with graph, build role matrix, or the user says "/nacl-ba-roles". - SKILL.md
- nacl-ba-rules: Catalog business rules in Neo4j: constraints, calculations, invariants, authorization.Use when: extract business rules with graph, classify rules, or the user says "/nacl-ba-rules". - SKILL.md
- nacl-ba-sync: Синхронизация Excalidraw-доски с Neo4j графом: элементы доски становятся узлами и рёбрами. Используй когда пользователь просит: синхронизировать доску с графом, пушнуть доску в Neo4j, создать узлы... - SKILL.md
- nacl-ba-validate: Validate BA model consistency via Cypher: L1-L8 internal checks, XL1-XL5 cross-validation with SA layer. Read-only, no writes.Use when: validate BA model, check consistency, or the user says "/nacl... - SKILL.md
- nacl-ba-workflow: Build activity diagrams for business processes in Neo4j: workflow steps, performers, documents, decisions. 3-swimlane decomposition.Use when: decompose process into steps with graph, or the user sa... - SKILL.md
- nacl-core: Shared references, templates, and utilities for all nacl-* skills. Not directly invocable - provides Neo4j connection conventions, schema references, ID format rules, and Excalidraw standards. - SKILL.md
- nacl-goal: Safety-first wrapper around Anthropic's /goal command. Resolves a high-level NaCl alias into a deterministic GOAL_PROOF completion condition that the transcript-only evaluator can actually verify.... - SKILL.md
- nacl-init: Initialize a new project with CLAUDE.md containing development rules, skill routing, bug fix protocol, and documentation discipline. Use when: new project, initialize project, setup project, create... - SKILL.md
- nacl-migrate-ba: Migrate an OLD-methodology BA layer from Markdown to Neo4j. Parses docs/00-context, docs/01-business-processes, docs/02-business-entities, docs/03-business-roles, docs/04-business-rules, docs/99-me... - SKILL.md
- nacl-migrate-sa: Migrate an OLD-methodology SA layer from Markdown to Neo4j. Parses docs/10-architecture (or 00-architecture), docs/12-domain (or 02-domain), docs/13-roles (or 03-roles), docs/14-usecases (or 04-use... - SKILL.md
- nacl-migrate: Orchestrator: migrate an OLD-methodology project (Markdown BA/SA docs) into the graph-based nacl-* methodology. Chains nacl-init, nacl-migrate-ba, nacl-ba-validate, nacl-migrate-sa, nacl-sa-validat... - SKILL.md
- nacl-postmortem: Post-mortem of a project built end-to-end via nacl-* skills: for each post-"done" bug, find which skill gate let it through. Produces docs/retrospectives/-postmortem.md. Use when: a finish... - SKILL.md
- nacl-publish: Публикация графа в Docmost и генерация Excalidraw-бордов. Используй когда пользователь просит: опубликовать граф, синхронизировать с Docmost, сгенерировать борды, nacl-publish, graph publish. - SKILL.md
- nacl-render: Convert Neo4j graph data into Markdown documents with Mermaid diagrams. Use when: render graph, generate docs, or the user says "/nacl-render md". Excalidraw board rendering moved to analyst-tool -... - SKILL.md
- nacl-sa-architect: Декомпозиция системы на модули (Bounded Contexts), построение Context Map и определение NFR. Читает BA-данные из Neo4j графа, записывает Module/Requirement узлы в граф. Используй когда пользователь... - SKILL.md
- nacl-sa-domain: Domain Model through Neo4j graph: DomainEntity, DomainAttribute, Enumeration, relationships. Modes: IMPORT_BA (import from BA layer), CREATE (new entity), MODIFY (change entity), FULL (full module... - SKILL.md
- nacl-sa-feature: Incremental feature specification via Neo4j graph. Impact analysis through Cypher traversal, selective SA skill invocation, FeatureRequest artifact.Use when: add feature with graph, new functionali... - SKILL.md
- nacl-sa-finalize: Finalize specification via Neo4j: statistics, glossary, ADR, traceability matrix, readiness assessment. All computed from graph queries.Use when: finalize spec with graph, generate statistics, or t... - SKILL.md
- nacl-sa-flags: Backfill validation-exemption properties on SA-layer nodes (has_ui, system_only, shared, internal, field_category). Pure validator metadata; no domain logic, no new nodes/edges. Designed for projec... - SKILL.md
- nacl-sa-full: Full SA specification in Neo4j via 10-phase orchestration. Chains all nacl-sa-* skills with user confirmation gates.Use when: create complete SA spec with graph, or the user says "/nacl-sa-full". - SKILL.md
- nacl-sa-roles: System roles and permission matrix through Neo4j graph: SystemRole, HAS_PERMISSION, MAPPED_TO. Modes: IMPORT_BA (import BusinessRole from BA layer), CREATE (new role), MODIFY (change role), FULL (f... - SKILL.md
- nacl-sa-uc: Реестр Use Cases из BA automation scope + детализация UC (Activity, формы, требования)
- behavior slices (graph-native сценарии приёмки Given/When/Then)
- domain errors (транспортно-независимая так... - SKILL.md
- nacl-sa-ui: UI architecture through Neo4j graph: navigation, components, form-domain mapping verification, deterministic screen state machines (Screen/ScreenState/ScreenEvent/Transition/ScreenEffect). Use when... - SKILL.md
- nacl-sa-validate: Validate specification consistency through Neo4j Cypher queries. Internal validation (L1-L13): data consistency, model connectivity, requirement completeness, form-domain traceability, UC-form vali... - SKILL.md
- nacl-tl-conductor: Graph-aware batch process manager: intake to staging. Delegates planning to nacl-tl-plan, dev to nacl-tl-full.Use when: batch workflow with graph, orchestrate graph intake, or the user says "/nacl-... - SKILL.md
- nacl-tl-deliver: Delivery orchestrator: push feature branch, wait for CI, verify on staging, health check. Chains nacl-tl-ship, nacl-tl-verify, and nacl-tl-deploy into a single continuous pipeline. Use when: delive... - SKILL.md
- nacl-tl-deploy: Monitor CI/CD deployment (GitHub Actions), run health checks, update YouGile. Deployment is triggered by git push (nacl-tl-ship), this skill monitors the result. Use when: deploy, check deploy stat... - SKILL.md
- nacl-tl-dev-be: Backend TDD development from task specifications. Use when: develop backend, implement BE feature, run backend TDD cycle, write backend code for UC, or the user says "/nacl-tl-dev-be UC###". - SKILL.md
- nacl-tl-dev-fe: Frontend TDD development from task specifications. Use when: develop frontend, implement UI, create UI components, build pages, write frontend code for UC, or the user says "/nacl-tl-dev-fe UC###".... - SKILL.md
- nacl-tl-dev: Infrastructure and TECH task development using TDD workflow. Use when: develop TECH task, setup infrastructure, configure Docker, setup CI/CD, database migrations, or the user says "/nacl-tl-dev TE... - SKILL.md
- nacl-tl-diagnose: Project health diagnostic - analyzes git history, documentation drift, code health, and regression patterns. Produces DIAGNOSTIC-REPORT.md. Use when: everything is broken, need to understand what's... - SKILL.md
- nacl-tl-docs: Documentation updates for approved tasks. Use when: update documentation, write docs, finalize task, complete task, mark done, or the user says "/nacl-tl-docs UC###". - SKILL.md
- nacl-tl-fix: Spec-first bug fixing with automatic documentation sync. Auto-detects affected UC/TECH from problem description. Classifies fix level (L0/L1/L2/L3), updates docs BEFORE code. Use when: fix bug, res... - SKILL.md
- nacl-tl-full: Graph-aware full lifecycle orchestrator. Reads waves/tasks from Neo4j, updates phase status in graph. Delegates to standard dev skills.Use when: run full dev workflow with graph, or the user says "... - SKILL.md
- nacl-tl-hotfix: Emergency hotfix to main: stash/cherry-pick changes, create hotfix branch from main, validate, open PR with auto-merge, restore source branch. Use when: critical production bug, urgent fix to main,... - SKILL.md
- nacl-tl-intake: Graph-aware request triage: queries Neo4j to disambiguate features vs bugs. Routes features to nacl-sa-feature, bugs to nacl-tl-fix, tasks to nacl-tl-dev.Use when: triage with graph context, batch... - SKILL.md
- nacl-tl-next: Graph-aware next task recommendation with SA context enrichment. Reads Task/Wave from Neo4j, enriches with UC entity/form names.Use when: next task with graph, what to work on, or the user says "/n... - SKILL.md
- nacl-tl-plan: Graph-based development planning from SA specifications in Neo4j. One Cypher query per UC instead of reading ~70 markdown files. Creates paired BE+FE tasks, TECH tasks, api-contracts, and execution... - SKILL.md
- nacl-tl-qa: E2E QA testing for UC tasks using MCP Playwright. Acts as a real user: navigates pages, fills forms, clicks buttons, verifies results. Takes screenshots of each step. Use when: test UC, run QA, E2E... - SKILL.md
- nacl-tl-reconcile: Emergency documentation-code reconciliation. Brings all docs in sync with current code state. Uses nacl-tl-diagnose report, fixes docs via SA skills, validates result. Use when: massive drift, docs... - SKILL.md
- nacl-tl-regression-test: Writes a test authored by a separate sub-agent (test-author isolation seam). Two modes: bug-fix - writes a test that FAILS on broken (un-fixed) code. feature-dev - writes a test that FAILS... - SKILL.md
- nacl-tl-release: Full release pipeline: merge verified PRs to main, wait for production CI, health check, version bump, git tag, changelog, GitHub release, YouGile notification. Use when: create release, bump versi... - SKILL.md
- nacl-tl-reopened: Process tasks from YouGile Reopened column (failed verification/QA). Reads tester feedback from task chat, diagnoses root cause, fixes via /nacl-tl-fix, ships via /nacl-tl-ship, closes the verifica... - SKILL.md
- nacl-tl-review: Code review for completed tasks (BE, FE, or TECH). Use when: review code, code review, check implementation, verify task, approve development, or the user says "/nacl-tl-review UC### --be" or "/nac... - SKILL.md
- nacl-tl-ship: Commit, push, create PR, and update YouGile after development. Reads git strategy from config.yaml (direct vs feature-branch). Posts commit summary to YouGile task chat. Use when: ship code, commit... - SKILL.md
- nacl-tl-status: Graph-aware project status with SA coverage metrics. Reads Task/Wave nodes from Neo4j, falls back to status.json.Use when: project status with graph, check progress with SA coverage, or the user sa... - SKILL.md
- nacl-tl-stubs: Scans codebase for stubs, mocks, and placeholder code. Maintains stub-registry.json with severity tracking. Use when: scan for stubs, check stubs, verify no placeholders, run stub check, stub repor... - SKILL.md
- nacl-tl-sync: Verifies BE/FE synchronization for a UC task. Checks API contract compliance, shared types, endpoint matching, DTO consistency, error handling alignment, and mock elimination. Use when: verify sync... - SKILL.md
- nacl-tl-verify-code: Static code analysis to verify implementation correctness. Traces data flow: DB → service → route → hook → component → UI. Returns PASS / PASS_NEEDS_E2E / UNVERIFIED / NO_INFRA / RUNNER_BROKEN / BL... - SKILL.md
- nacl-tl-verify: Verification orchestrator: code analysis + E2E testing + YouGile reporting. Runs /nacl-tl-verify-code first (cheap, catches 60%+ issues), then /nacl-tl-qa if needed. Posts verification reports to Y... - SKILL.md
- nacl-core: Shared references, templates, and utilities for all nacl-* skills. Not directly invocable - provides Neo4j connection conventions, schema references, ID format rules, and Excalidraw standards. - SKILL.md
- ba-analyze: Анализ Excalidraw-доски бизнес-процесса: полнота, diff со snapshot, сравнение с Neo4j-графом. Используй когда пользователь просит: проанализировать доску, проверить доску, найти проблемы на доске,... - SKILL.md
- ba-context: Define system boundaries in Neo4j graph: scope, stakeholders, external entities, data flows.- all data stored as graph nodes and edges. Use when: define system scope with graph, system context diag... - SKILL.md
- ba-entities: Catalog business entities in Neo4j: stereotypes, attributes, states, CRUD matrix.Use when: model entities with graph, create entity catalog, or the user says "/nacl:ba-entities". - SKILL.md
- ba-from-board: Orchestrator skill: unified BA-board workflow combining import_doc + analyze + sync. Creates boards, imports client documents, analyzes completeness, syncs to Neo4j graph. Invocation: /nacl:ba-from... - SKILL.md
- ba-full: Full BA model creation in Neo4j via 10-phase orchestration. Chains all nacl-ba-* skills sequentially with user confirmation gates.Use when: create complete BA model with graph, full business analys... - SKILL.md
- ba-glossary: Build ubiquitous language glossary in Neo4j: terms, definitions, synonyms, links.Use when: create glossary with graph, define terms, or the user says "/nacl:ba-glossary". - SKILL.md
- ba-handoff: Generate BA→SA handoff package from Neo4j: traceability matrix, automation scope, module suggestions, coverage stats. Creates cross-layer edges after user confirmation.Use when: prepare BA→SA hando... - SKILL.md
- ba-import-doc: Parse a client document (DOCX/PDF/XLSX/text) and place extracted business-process elements onto an Excalidraw board with swimlanes, confidence colors, and customData. Invocation: /nacl:ba-import-do... - SKILL.md
- ba-process: Build business process map in Neo4j: process groups, processes, links, roles.- all data stored as graph nodes and edges. Use when: map processes with graph, create process map, or the user says "/n... - SKILL.md
- ba-roles: Identify and describe business roles in Neo4j: departments, responsibilities, role-process matrix.Use when: define roles with graph, build role matrix, or the user says "/nacl:ba-roles". - SKILL.md
- ba-rules: Catalog business rules in Neo4j: constraints, calculations, invariants, authorization.Use when: extract business rules with graph, classify rules, or the user says "/nacl:ba-rules". - SKILL.md
- ba-sync: Синхронизация Excalidraw-доски с Neo4j графом: элементы доски становятся узлами и рёбрами. Используй когда пользователь просит: синхронизировать доску с графом, пушнуть доску в Neo4j, создать узлы... - SKILL.md
- ba-validate: Validate BA model consistency via Cypher: L1-L8 internal checks, XL1-XL5 cross-validation with SA layer. Read-only, no writes.Use when: validate BA model, check consistency, or the user says "/nacl... - SKILL.md
- ba-workflow: Build activity diagrams for business processes in Neo4j: workflow steps, performers, documents, decisions. 3-swimlane decomposition.Use when: decompose process into steps with graph, or the user sa... - SKILL.md
- init: Initialize a new project with CLAUDE.md containing development rules, skill routing, bug fix protocol, and documentation discipline. Use when: new project, initialize project, setup project, create... - SKILL.md
- publish: Публикация графа в Docmost и генерация Excalidraw-бордов. Используй когда пользователь просит: опубликовать граф, синхронизировать с Docmost, сгенерировать борды, nacl-publish, graph publish. - SKILL.md
- render: Convert Neo4j graph data into Markdown documents with Mermaid diagrams. Use when: render graph, generate docs, or the user says "/nacl:render md". Excalidraw board rendering moved to analyst-tool -... - SKILL.md
- sa-architect: Декомпозиция системы на модули (Bounded Contexts), построение Context Map и определение NFR. Читает BA-данные из Neo4j графа, записывает Module/Requirement узлы в граф. Используй когда пользователь... - SKILL.md
- sa-domain: Domain Model through Neo4j graph: DomainEntity, DomainAttribute, Enumeration, relationships. Modes: IMPORT_BA (import from BA layer), CREATE (new entity), MODIFY (change entity), FULL (full module... - SKILL.md
- sa-feature: Incremental feature specification via Neo4j graph. Impact analysis through Cypher traversal, selective SA skill invocation, FeatureRequest artifact.Use when: add feature with graph, new functionali... - SKILL.md
- sa-finalize: Finalize specification via Neo4j: statistics, glossary, ADR, traceability matrix, readiness assessment. All computed from graph queries.Use when: finalize spec with graph, generate statistics, or t... - SKILL.md
- sa-flags: Backfill validation-exemption properties on SA-layer nodes (has_ui, system_only, shared, internal, field_category). Pure validator metadata; no domain logic, no new nodes/edges. Designed for projec... - SKILL.md
- sa-full: Full SA specification in Neo4j via 10-phase orchestration. Chains all nacl-sa-* skills with user confirmation gates.Use when: create complete SA spec with graph, or the user says "/nacl:sa-full". - SKILL.md
- sa-roles: System roles and permission matrix through Neo4j graph: SystemRole, HAS_PERMISSION, MAPPED_TO. Modes: IMPORT_BA (import BusinessRole from BA layer), CREATE (new role), MODIFY (change role), FULL (f... - SKILL.md
- sa-uc: Реестр Use Cases из BA automation scope + детализация UC (Activity, формы, требования)
- behavior slices (graph-native сценарии приёмки Given/When/Then)
- domain errors (транспортно-независимая так... - SKILL.md
- sa-ui: UI architecture through Neo4j graph: navigation, components, form-domain mapping verification, deterministic screen state machines (Screen/ScreenState/ScreenEvent/Transition/ScreenEffect). Use when... - SKILL.md
- sa-validate: Validate specification consistency through Neo4j Cyphe...
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.