What problem does it solve? Hand-maintained status text in issues, docs, and artifacts silently goes stale: completion declarations, counts, and copied summaries become false as soon as the underlying facts change, and duplicate issues get opened because stale local state was trusted. ## Core Features & Use Cases - Three-layer placement rules: Separates rules (CLAUDE.md, checks), state (issues, milestones, labels, PRs), and durable records (artifacts, docs/) so each fact lives where it stays true. - Stale-content prohibitions: Bans completion declarations, censuses, enumerations, checkboxes, and copied issue summaries from persistent documents; distinguishes event dates from expiring 'current state' claims. - Four-line issue body format: Structures every issue as why / closing condition / expectations or order (when present) / where to look. - Pre-issue duplicate check: Requires comparing open issues, PR merged fields, merge commit titles, and origin/main code after running git fetch before creating an issue. - Use Case: Before opening a GitHub issue or writing a status update into a design doc, apply these rules so the text remains true next month and no duplicate issue number is burned. ## Quick Start Review my draft issue body and this documentation paragraph, and rewrite them so nothing in them will silently go stale.
