doc-triage

Identifies internal documentation files and archives stale ones.

2|1|Updated Oct 3, 2025

Search Tags:#beads #archiving #triage #code-review #handoffs #internal-docs #doc-triage

Ready to run

npx skills add https://github.com/jamestexas/agents --skill doc-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-triage
Source: https://github.com/jamestexas/agents/tree/main/skills/doc-triage
Command: npx skills add https://github.com/jamestexas/agents --skill doc-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find internal documentation files that aren't meant for external consumers, review them against the actual code, bead real items, and archive stale files.

Core Features & Use Cases

Discover internal docs matching patterns like TODO.md, KNOWN_ISSUES.md, INVESTIGATION_LOG.md, HANDOFF*.md, and _agent_log/** to triage.
Evaluate each item against the codebase to classify as bead, fixed, stale, or context.
Create beads for real items with code citations, and archive non-bead content into a version-controlled archive.
Provide a final report of beads created and files archived.

Quick Start

Run doc-triage on your repository to identify internal docs, bead real items, and archive the rest.

Frequently Asked Questions about doc-triage

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

FAQPage Schema

How do I triage internal documentation files like TODO.md and HANDOFF notes in a long-running project?▼

Triage internal documentation by scanning candidate files like TODO.md and INVESTIGATION_LOG.md, validating items against the codebase, creating actionable beads with citations, and archiving stale content into a git-ignored .archive directory.

What is the best way to clean up stale internal docs and agent logs without losing track of actionable items?▼

Clean up stale internal docs by evaluating each item against the codebase to classify it as a bead, fixed, stale, or context, then archiving non-bead content into a version-controlled .archive directory while creating beads for real items.

Can I automatically archive handoff notes and investigation logs after extracting actionable code tasks?▼

Yes, you can archive handoff notes and investigation logs by scanning files matching patterns like HANDOFF*.md and _agent_log directories, creating beads with code citations for real items, and moving processed files to a git-ignored .archive directory.

How does validating internal documentation against the codebase work when triaging project notes?▼

Validating internal documentation against the codebase works by scanning candidate files, evaluating each item to classify it as bead, fixed, stale, or context, and generating beads with direct citations to source files for actionable items.

What types of internal documentation files are candidates for triage in a repository?▼

Candidate internal documentation files for triage include TODO.md, KNOWN_ISSUES.md, INVESTIGATION_LOG.md, HANDOFF*.md, and files within _agent_log directories, especially in long-running projects with multiple handoffs.

Does triaging internal docs require any special dependencies or components to run?▼

No, triaging internal docs requires no special dependencies or components; it scans the repository directly to identify internal notes, validate items against the codebase, and generate a final report of beads created and files archived.