chain-done

Validate and cascade DONE status for analysis chains from REVIEW.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill chain-done-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chain-done
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/chain-done
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill chain-done-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill completes the analysis chain by performing pre-flight validations, cascading DONE status, moving Planned Changes to AS IS, enabling system-agent mode=done, and providing cross-chain reporting when translating from REVIEW to DONE.

Core Features & Use Cases

  • Pre-flight checks before marking a chain as DONE.
  • T7 cascade logic to propagate DONE across dependent tasks.
  • Move Planned Changes to AS IS to reflect final state.
  • Cross-chain coordination and system-agent mode=done workflows.
  • Use when translating a chain from REVIEW to DONE to ensure traceability.

Quick Start

Run the /chain-done command with a four-digit chain number to finalize the analysis chain.

Frequently Asked Questions about chain-done

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

FAQPage Schema
How do I automate cross-chain workflow finalization when translating chains from REVIEW to DONE?

Cross-chain workflow finalization is automated by performing pre-flight validations, cascading DONE status, and moving Planned Changes to AS IS. This ensures traceability and validates completion criteria before enabling system-agent mode=done.

What pre-flight checks are required before marking an analysis chain as DONE?

Pre-flight checks for marking an analysis chain as DONE involve validating completion criteria and enforcing SSOT-guided steps. These validations confirm that all cross-chain coordination requirements are met before the cascade logic propagates the final status.

How does T7 cascade logic propagate DONE status across dependent tasks?

T7 cascade logic propagates DONE status by automatically finalizing dependent tasks across cross-chain steps once pre-flight validations pass. This coordinates the transition from REVIEW to DONE and enables system-agent mode=done across the workflow.

Can I finalize an analysis chain without providing a four-digit chain number?

Finalizing an analysis chain requires a four-digit chain number as input. The Skill enforces this strict input format to accurately target the specific chain, apply pre-flight checks, and execute the cascading DONE status transition.

When should I move Planned Changes to AS IS during chain finalization?

Planned Changes should be moved to AS IS during chain finalization to reflect the final system state. This occurs automatically after pre-flight validations succeed and the workflow transitions from REVIEW to DONE.

Does system-agent mode=done require cross-chain coordination to execute properly?

System-agent mode=done requires cross-chain coordination to execute properly, ensuring all dependent steps are validated and aligned. The finalization process enforces SSOT-guided steps to guarantee traceability before the mode is activated.