specdo-archive

Archive active changes deterministically with verification gates and metadata updates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specdo-archive
Source: https://github.com/MoonCoder-HAPPY/SpecDo/tree/main/specdo-archive
Command: npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Archive active changes deterministically and safely. This skill provides the controlled transition from active to archived state by enforcing prerequisites, validating readiness payloads, and updating archived metadata.

Core Features & Use Cases

  • Deterministic move: moves an active change into specdo/changes/archive with a date prefix.
  • Verification and gating: requires archive_readiness and performs pre-move checks to block unsafe archives.
  • Metadata synchronization: updates change.yaml in the archived path to record status, created date, and sync state.

Quick Start

Provide the change id and let SpecDo Archive perform the move, validation, and metadata update.

Frequently Asked Questions about specdo-archive

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

FAQPage Schema
How do I safely archive active changes in a workflow?

To safely archive active changes, this skill enforces verification gates, validates workspace readiness, and performs a deterministic move to the archive directory with a date prefix. It updates metadata and state only after all prerequisites pass.

What does a verification gate check before archiving a change?

A verification gate checks archive readiness by validating workspace payloads and blocking unsafe moves. It enforces prerequisites to ensure the active change is fully validated before the deterministic archiving process is permitted.

How do I move an active change to an archived state deterministically?

You move an active change to an archived state deterministically by providing the change id. The skill coordinates validation, executes the move with a date prefix, and updates the archived metadata to record status and sync state.

Can I archive a change if the workspace validation fails?

You cannot archive a change if workspace validation fails. The skill blocks unsafe archives by requiring an archive readiness payload, ensuring that all prerequisite checks pass before permitting the move.

What metadata is updated when archiving an active change?

When archiving an active change, the skill updates the change.yaml file in the archived path to record the status, created date, and sync state. This metadata synchronization happens upon successful completion of the move.

When do I need to use a controlled archiving process for change management?

You need a controlled archiving process for change management when transitioning active changes to an archived state. It enforces prerequisites, blocks unsafe moves, and ensures the archived metadata and state are updated safely.