nacl-migrate

Orchestrate legacy Markdown BA/SA document migration into graph-based NaCl methodology.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the migration of legacy Markdown BA/SA documents into the graph-based NaCl methodology, ensuring traceability and a clean transition.

Core Features & Use Cases

  • Orchestrates the multi-phase migration workflow by delegating to nacl-init, nacl-migrate-ba, nacl-ba-validate, nacl-migrate-sa, nacl-sa-validate, nacl-tl-diagnose, and nacl-render with explicit gating between phases.
  • Generates MIGRATION-REPORT.md aggregating phase results and writes essential config artifacts (config.yaml, .mcp.json) and graph infra as needed.
  • Supports dry-run, resume-from, and phase-skipping options to tailor migrations for complex projects.

Quick Start

Invoke /nacl-migrate from the project root to begin migrating your old Markdown BA/SA docs into the NaCl graph, with optional flags for dry-run or selective phases.

Frequently Asked Questions about nacl-migrate

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

FAQPage Schema
How do I migrate legacy Markdown BA/SA documents to a graph-based methodology?

To migrate legacy Markdown BA/SA documents to a graph-based methodology, this skill orchestrates a multi-phase workflow that converts old artifacts into graph models while ensuring traceability and generating a MIGRATION-REPORT.md.

What is the process for converting old BA/SA artifacts into NaCl graph models?

Converting old BA/SA artifacts into NaCl graph models involves gated phases that delegate to specialized skills for initialization, migration, validation, and rendering, requiring explicit user confirmations between each phase.

Can I run a dry-run or skip phases during a BA/SA document migration?

Yes, you can run a dry-run or skip phases during a BA/SA document migration. The orchestration supports dry-run, resume-from, and phase-skipping options to tailor migrations for complex projects.

Does migrating legacy BA/SA docs to the NaCl graph require manual validation?

Migrating legacy BA/SA docs to the NaCl graph enforces manual validation by delegating to dedicated validation skills and requiring explicit user confirmations to gate progression between migration phases.

What configuration files are generated when migrating BA/SA docs to a graph structure?

Migrating BA/SA docs to a graph structure generates essential configuration artifacts including config.yaml, .mcp.json, graph infrastructure, and a MIGRATION-REPORT.md that aggregates the results of all migration phases.