skills.rest
alexandremendoncaalvaro
alexandremendoncaalvaroCOMMUNITY
Explore all skills by this author →
Website𝕏@xambitoGitHub

ad-archive

Remove completed planning artifacts from the working tree while preserving Git history.

728|16|Updated Mar 9, 2026
Search Tags:#git#workflow#archive#specs#prds#adr-management#plan-documents
One-click install
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-archive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ad-archive
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-archive
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the repository lean by removing completed plan artifacts from the working tree while preserving their historical record in Git. This reduces cognitive load during development and ensures a clean, focused workspace.

Core Features & Use Cases

  • Hard-delete completed tasks (Status: done), shipped specs, superseded PRDs, and deprecated ADRs, with their content retained in Git history for auditability.
  • Enforces repository discipline by forbidding in-tree archives and changelogs in narrative documents; requires explicit absorption proof for accepted ADRs before removal.

Quick Start

Run the ad-archive workflow to hard-delete completed artifacts from the working tree while preserving their history in Git.

Frequently Asked Questions about ad-archive

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

FAQPage Schema
How do I remove completed specs and PRDs from the working tree while preserving Git history?▼

You can hard-delete completed planning artifacts using a single atomic git rm operation, removing them from the working tree while retaining their full content in Git history for auditability.

What's the best way to archive deprecated ADRs without keeping them in the repository directory?▼

The workflow hard-deletes deprecated and superseded ADRs from the working tree via git rm, ensuring no in-tree archive directories are created while preserving the records in Git history.

When can I remove accepted ADRs from the working tree?▼

Accepted ADRs require explicit absorption proof before removal, ensuring their decisions are documented elsewhere before they are hard-deleted from the working tree via Git.

Does this Git workflow support archiving tasks marked as done and shipped specs?▼

Yes, the workflow targets tasks with Status: done and specs with Status: shipped, removing them from the working tree while enforcing repository discipline by forbidding CHANGELOG.md files.

Why should I avoid keeping an archive directory in my Git repository?▼

Keeping an in-tree archive directory increases cognitive load during development; the workflow enforces no archive directories by hard-deleting completed artifacts directly via git rm to maintain a lean repository.

Can I use a single Git command to clean up multiple completed plan documents?▼

Yes, the workflow performs all removals of completed tasks, specs, PRDs, and ADRs through a single atomic git rm operation, preserving their history without leaving residual files.

Related Skills

Explore More Software Engineering Skills→
spencerbeggsspencerbeggs

design-archive

Archive outdated design docs by updating frontmatter and cross-references.

Community
Advanced
SatoryKonoSatoryKono
1

documentation-audit

Audit BioETL documentation against code and ADRs for v5.22+ gaps.

Community
Advanced
hankh95hankh95
1

release

Bump semantic versions, tag git repositories, and update CHANGELOG files.

Community
Intermediate
mattothomasmattothomas

careful

Require explicit confirmation before executing destructive shell and deployment commands.

Community
Intermediate