harness:archive

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.