spec-archive

Archive FRs or milestone groups with a diff approval gate.

6|Updated Mar 19, 2026

Search Tags:#audit #archival #milestones #diff #git-mv #tracker #frs

Ready to run

npx skills add https://github.com/nesquikm/dev-process-toolkit --skill spec-archive-nesquikm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-archive
Source: https://github.com/nesquikm/dev-process-toolkit/tree/main/plugins/dev-process-toolkit/skills/spec-archive
Command: npx skills add https://github.com/nesquikm/dev-process-toolkit --skill spec-archive-nesquikm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive FRs and milestones with an auditable, reviewer-approved workflow that moves files to archive directories and updates metadata.

Core Features & Use Cases

Single-FR archival: move specs/frs/<name> to specs/frs/archive/<name>, flip status to archived, set archived_at, and rewrite traceability links.
Milestone-group archival: batch-archive all active FRs for M<N> and optional plan file, all in one atomic commit.
Explicit approval gate: render a diff preview and require user confirmation prior to any file moves or metadata changes.

Quick Start

Use /spec-archive with a ULID, tracker ID/URL, or M<N> to begin archiving.

Frequently Asked Questions about spec-archive

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

FAQPage Schema

How do I archive feature requirements with an auditable approval gate?▼

To archive feature requirements with an auditable approval gate, use the archival command with a ULID, tracker ID, or milestone group to render a diff preview that requires explicit user confirmation before moving files or updating metadata.

How does milestone group archival work for multiple active FRs?▼

Milestone group archival batch-archives all active FRs for a specified M<N> group and optional plan file into specs/frs/archive/ directories within a single atomic commit, ensuring traceability links are rewritten consistently.

Can I archive a single feature requirement using a tracker URL?▼

Yes, you can archive a single feature requirement by providing a tracker URL, tracker ID, or ULID to move the file to specs/frs/archive/, flip status to archived, set archived_at, and rewrite traceability references.

What happens to traceability links when I move FR files to an archive directory?▼

When moving FR files to an archive directory, resolver logic and traceability rewrites automatically update references to keep links consistent, ensuring no broken connections across your specifications.

Does the archival workflow execute git mv commands without user confirmation?▼

No, the archival workflow enforces an explicit approval step by rendering a diff preview and requiring user confirmation prior to executing any git mv commands, frontmatter updates, or releaseLock calls.

When should I avoid batch-archiving milestones and plan files together?▼

You should avoid batch-archiving milestones and plan files together when individual FRs within the M<N> group still require active development, as the process targets all active FRs in one atomic commit.