harness:archive

Archive completed feature specs and verify documentation consistency with the codebase.

3|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/huangbaixun/harness-engineering --skill harness-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness:archive
Source: https://github.com/huangbaixun/harness-engineering/tree/main/skills/archive
Command: npx skills add https://github.com/huangbaixun/harness-engineering --skill harness-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete or inconsistent handoff documentation after work is marked complete, keeping archived specs and architecture notes aligned with the codebase.

Core Features & Use Cases

  • Completion archiving: Moves completed feature docs into docs/archive/ using git mv and prepends completion metadata (timestamp, session id, feature id) while updating docs/features.json.
  • Documentation consistency check: Compares documented architecture vs actual src/ structure, validates CLAUDE.md rules for redundancy/obsolescence, and verifies ADRs with status "Adopted" are still in use.
  • Architecture health quick check: Flags dependency direction violations, oversized files (>300 lines), and recently-added files without tests, then packages findings into an actionable report.

Use case: After harness verification marks a feature as completed, run archiving to ensure docs/specs or docs/plans artifacts are preserved with traceable history and that the documentation matches current implementation.

Quick Start

Ask your AI agent to run harness:archive at the end of a completed feature to produce an archiving report and sync documentation with the latest code.

Frequently Asked Questions about harness:archive

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

FAQPage Schema
How do I archive completed feature specs and sync documentation with the codebase?

To archive completed feature specs, use git mv to move feature docs into docs/archive/, prepend completion metadata, update docs/features.json, and run a documentation consistency check to sync architecture notes with the src/ structure.

What is architecture drift and how do I validate it against adopted ADRs?

Architecture drift occurs when documented architecture diverges from the actual codebase. Validate it by comparing documentation against src/ structure and verifying that ADRs with an Adopted status remain actively in use within the project.

When should I run a documentation consistency check for completion handoff artifacts?

Run a documentation consistency check during feature completion, end-of-sprint cleanup, major refactors, or when enough completed features accumulate and archiving is prompted to ensure handoff artifacts match the codebase.

How do I verify CLAUDE.md rules and check for oversized files without tests?

Verify CLAUDE.md rules by validating them for redundancy or obsolescence. Check for oversized files by running a lightweight architecture scan that flags files over 300 lines and recently-added files without tests.

Does the archiving process require reading docs/features.json and docs/architecture.md?

Yes, the archiving process requires reading docs/features.json and docs/architecture.md to validate completion handoff artifacts, update feature tracking, and ensure architecture documentation stays aligned with the codebase.