跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

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 graph context or for compatibility with `/nacl-sa-full`.

ITSalt · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add ITSalt/NaCl --skill nacl-sa-full

技能说明


name: nacl-sa-full description: | 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 graph context or for compatibility with /nacl-sa-full.

NaCl SA Full For Codex

Packaged Gateway Binding

Read the packaged gateway binding and use only its sa-resource sequence. Module, FeatureRequest, and UseCase scalar mutations require the exact SA approval, live lease/fence, revision CAS, read-back, and release. Any required relationship or additional SA surface returns the mapped blocking gap code.

Coordinate full SA graph specification work without assuming a separate isolated runner. SA artifacts remain Russian where the NaCl methodology requires Russian.

Read ../references/orchestration-model.md, ../references/migration-rules.md, ../references/verification-vocabulary.md, and ../nacl-core/SKILL.md before executing this skill.

Goal Boundary

This skill is not safe to wrap in /goal because SA completion contains mandatory phase-confirmation and handoff judgment gates. Use this skill interactively, then use a goal-wrapped verification alias only after the gate is complete.

Reference ../nacl-goal/SKILL.md, ../references/goal-codex-contract.md, ../../nacl-goal/refusal-catalog.md, and ../../docs/guides/goal-command.md. The refusal code is REFUSE_HUMAN_GATE_SA_PHASE_CONFIRMATION. Do not provide bypass flags. If autonomous execution is requested, report Status: BLOCKED or Status: NOT_RUN.

Contract

Inputs consumed:

  • confirmed BA graph context or user-provided system facts;
  • existing SA graph records when graph access is available;
  • SA graph schema and query references when file access is available;
  • downstream phase reports using the closed verification vocabulary.

Outputs produced:

  • phased SA progress report using only the closed vocabulary;
  • graph change requests or graph updates when graph tooling is available and confirmed;
  • reviewed downstream output summaries for each phase;
  • TL handoff readiness report.

Downstream consumers:

  • human user;
  • TL planning workflow;
  • publishing workflow;
  • graph query or visualization workflows.

Orchestration Rules

  • Use the shared Codex orchestration procedure from ../references/orchestration-model.md.
  • Each phase handoff must state inputs consumed, expected graph output, allowed verification status, downstream consumer, and handling for VERIFIED, FAILED, PARTIALLY_VERIFIED, BLOCKED, NOT_RUN, and UNVERIFIED.
  • Run, invoke, or simulate downstream procedures only when the current Codex environment supports the needed tools.
  • Collect and inspect downstream output before changing progress state or opening the next phase gate.
  • Stop after each phase and ask the user whether to proceed to the next phase.
  • Do not write graph data, modify files, publish, start TL planning, or move to the next major phase without explicit user confirmation.

Workflow

Phase 0: Resume And Scope

Check config.yaml, schema availability, and graph tool availability when file or graph access exists. Detect existing SA graph state for Module, DomainEntity, SystemRole, UseCase, Component, ValidationReport, and FinalizationReport.

Report detected state with closed vocabulary. Stop and ask the user to confirm the starting phase.

Phase 1: Architecture

Coordinate module decomposition, inter-module relationships, and non-functional requirements.

Contract:

  • Inputs: BA handoff when available, ProcessGroup, BusinessProcess, automated WorkflowStep, BusinessEntity, BusinessRole, BusinessRule, user facts, constraints, and current graph state.
  • Expected output: Module, module relationship, and non-functional Requirement records, SUGGESTS handoff edges, or a graph-ready change plan.
  • Downstream consumer: domain structure phase.
  • Gate: review module decomposition and context map before Phase 2.

Phase 2: Domain Structure

For each confirmed module, use the nacl-sa-domain procedure when available. Process modules sequentially unless available tooling supports a safer scoped handoff.

Contract:

  • Inputs: confirmed module, BA entities when available, module scope, and business terminology.
  • Expected output: DomainEntity, DomainAttribute, Enumeration, EnumValue, REALIZED_AS, TYPED_AS, and relationship records or a graph-ready change plan.
  • Downstream consumer: roles, use cases, forms, and requirements.
  • Gate: review each module's domain structure before the next module or Phase 3.

Phase 3: Roles

Coordinate system roles, permissions, and BA role mapping when BA graph context exists.

Contract:

  • Inputs: confirmed modules, domain structure, BA roles, and user facts.
  • Expected output: SystemRole records and permission or mapping relationships including MAPPED_TO and HAS_PERMISSION {crud}, or a graph-ready change plan.
  • Downstream consumer: use case registry.
  • Gate: review role and permission coverage before Phase 4.

Phase 4: Use Case Stories

Coordinate use case registry creation with user stories, acceptance criteria, priorities, modules, and actors.

Contract:

  • Inputs: confirmed modules, roles, BA automation candidates, and user facts.
  • Expected output: UseCase records and actor or module relationships or a graph-ready change plan. BA automation candidates are WorkflowStep records marked stereotype='Автоматизируется' and missing AUTOMATES_AS.
  • Downstream consumer: use case detail phase.
  • Gate: review use case registry and priority selection before Phase 5.

Phase 5: Use Case Detail

For each primary use case, coordinate detailed activity flow, forms, field mapping, requirements, and dependencies. Secondary use cases are detailed only when the user confirms that scope.

Contract:

阅读完整来源 ↗