archive-requirements

Name: archive-requirements
Availability: InStock
Author: nexus-a1

Archive completed requirements into a git-backed knowledge base with a searchable index.

Updated Mar 29, 2026

Search Tags:#workflow #context #requirements #metadata #archive #knowledge-base

Ready to run

npx skills add https://github.com/nexus-a1/claude-skills --skill archive-requirements

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive-requirements
Source: https://github.com/nexus-a1/claude-skills/tree/main/skills/archive-requirements
Command: npx skills add https://github.com/nexus-a1/claude-skills --skill archive-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually archive completed requirements into the team's knowledge base can be error-prone and hard to maintain.

Core Features & Use Cases

Automates archiving of completed requirements into a centralized knowledge base.
Validates work state and context before archival to ensure completeness.
Generates a consolidated, searchable summary for KB integration and future reference.
Use case: after a successful implementation, archive the relevant specs, plans, and tasks for quick retrieval.

Quick Start

Run /archive-requirements JIRA-123 to archive a specific work item, or run /archive-requirements to select from available completed work.

Frequently Asked Questions about archive-requirements

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

FAQPage Schema

How do I archive completed requirements to a knowledge base?▼

Archive completed requirements by validating work state and context before transferring Spec-Driven triplets into a git-backed knowledge base. The process preserves metadata and generates a searchable summary for future reference.

What is the best way to preserve context when moving finished specs to a team archive?▼

Preserve context by using configuration-driven storage to transfer requirements into a git-backed archive. This approach enforces configuration lookups and updates a searchable index with metadata to maintain full historical context.

How do I validate work state before archiving requirements metadata?▼

Validate work state by checking the completion status and context of your requirements before archival. This validation step ensures completeness, verifying that all relevant specs, plans, and tasks are ready for knowledge base integration.

Can I use a git-backed archive for concurrent requirements archiving?▼

Yes, the archiving mechanism uses a git-backed archive to manage concurrency. This ensures that transferring Spec-Driven triplets and updating the searchable index remains consistent even when multiple requirements are archived simultaneously.

How do I search archived requirements metadata after moving them to the KB?▼

Search archived requirements through a searchable index that is automatically updated with metadata during the archival process. This index captures consolidated summaries to enable quick retrieval of past specs, plans, and tasks.