cleanup

Audit and reconcile misalignments across docs, specs, phase tables, and code.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ronniepinnell/benchsight --skill cleanup-ronniepinnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/ronniepinnell/benchsight/tree/main/.claude/skills/cleanup
Command: npx skills add https://github.com/ronniepinnell/benchsight --skill cleanup-ronniepinnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

For when docs, specs, phase tables, or code are out of sync. Audit everything. Triaging results.

Core Features & Use Cases

  • Audit & triage: run parallel agents to check doc staleness, phase-table completeness, spec coverage, code-spec drift, and dead references.
  • Triage & fix prompts: present findings with severity and generate actionable fix prompts for validation.
  • Execute & verify: apply fixes and re-run audits to confirm alignment.

Quick Start

Run an end-to-end audit and reconciliation to align docs, specs, phase tables, and code.

Frequently Asked Questions about cleanup

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

FAQPage Schema
How do I fix misalignments between docs, specs, phase tables, and code?

To fix misalignments between docs, specs, phase tables, and code, run an end-to-end audit and reconciliation workflow that identifies drift, triages findings by severity, and generates actionable fix prompts for validation.

What is the best way to audit stale documentation and dead references?

The best way to audit stale documentation and dead references is to run parallel agents that check doc staleness, phase-table completeness, and spec coverage, producing a severity-ranked triage report for targeted reconciliation.

How do I check for spec coverage and code-spec drift automatically?

You can check for spec coverage and code-spec drift automatically by deploying parallel audit agents that scan the project to detect incomplete phase tables and generate fix prompts for execution.

Can I execute and verify documentation fixes after an audit?

Yes, you can execute and verify documentation fixes by applying the generated fix prompts and re-running the comprehensive audits to confirm sustained alignment between specs, docs, and code.

When do I need to run a comprehensive phase-table and spec reconciliation?

You need to run a comprehensive phase-table and spec reconciliation when your project has stale mappings, incomplete phase tables, drift between specs and code, or dead references that require triaging and proposed fixes.