doc-style-sweep

Sorts accumulated work lists in documentation into current statements and closed items.

1|Updated Jan 14, 2024
One-click install
npx skills add https://github.com/Eyhenij/rt-tools --skill doc-style-sweep-eyhenij
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-style-sweep
Source: https://github.com/Eyhenij/rt-tools/tree/main/.claude/skills/doc-style-sweep
Command: npx skills add https://github.com/Eyhenij/rt-tools --skill doc-style-sweep-eyhenij

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-lived documents accumulate mixed content: completed plans, stale statements, and pending work items become indistinguishable, and nobody reads the file whole anymore. This Skill provides a repeatable review pattern for sorting such a document against the actual work queue. ## Core Features & Use Cases - Statement-level triage: Applies a single selection sign — a statement stays only if nobody intends to change it — to both bullet items and prose paragraphs. - Work queue verification: Checks each item against its linked task (e.g., GitHub issues via gh issue list), measuring content coverage before removal so no live detail is lost. - File fate decision: Determines whether the reviewed file stays with a new preamble, moves to an archive, or is deleted, and purges dangling references with a repository-wide grep. - Use Case: A BACKLOG.md has grown to hundreds of lines mixing done and pending work. Run this sweep to transfer live details into task bodies, remove stale statements, and decide the file's fate in one branch. ## Quick Start Review docs/BACKLOG.md using the doc-style-sweep pattern: sort every statement against the work queue, verify task coverage, and tell me the fate of the file.

Frequently Asked Questions about doc-style-sweep

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

FAQPage Schema
How do I clean up a backlog document that mixes done and pending work?

Apply one selection sign: a statement stays only if nobody intends to change it. Everything else is work that belongs in the task queue. Review statements individually, including prose paragraphs, not just bulleted items.

How to verify backlog items against GitHub issues before deleting them?

Export issues with `gh issue list --state all --json number,title,body,state`, then measure how many of each item's significant words appear in the linked task body. Items covered half or less are read by hand and either appended to the task, filed separately, or removed as stale.

Why does counting items without task numbers give wrong results?

Task numbers appear in multiple forms: in section headings, on dedicated ticket lines, and at the end of items. A parser that knows only one form miscounts silently, so any number obtained by parsing must be verified on a manual sample first.

When should a cleaned-up document be archived versus deleted?

If non-task content remains, the file stays with a preamble declaring the new selection sign. If nothing remains and it documented completed work, it moves to an archive directory. If it was purely a work list, it is deleted.

What are common mistakes when reviewing stale planning documents?

Common misses include reviewing only bullet items while work hides in prose, removing items without reading the linked task body, transferring stale statements into tasks as current instructions, and splitting the review into multiple branches when the revert is shared.