Docs Health Check — stale files detected 2026-06-28 #981

Executive Summary

Status: STALE_DOCS_FOUND
Stale files: 12

Key findings:

• Most stale file: petry-projects/TalkTerm/docs/ecc-for-bmad.md (94 days, last updated 2026-03-26)
• Largest cluster: petry-projects/google-app-scripts/docs/ — 8 files all stale 92 days, suggesting a bulk doc generation that was never followed up

Action required: Review and refresh or archive stale documentation in google-app-scripts, broodly, and TalkTerm before staleness compounds further.

Stale Files by Repo

petry-projects/TalkTerm

petry-projects/google-app-scripts

petry-projects/broodly

Recommendations

1. petry-projects/google-app-scripts — docs/ [LOW]
   Eight files last touched on the same date (2026-03-28) at 92 days stale indicates a one-time automated scan or doc-gen run that was never maintained. The owning team should determine whether these are living documents or generated artifacts. If generated, add a workflow to regenerate on each merge; if living, assign an owner to review and update. If neither, archive or delete. Urgency: LOW (92 days, approaching the 90-day threshold floor).

2. petry-projects/broodly — docs/architecture, docs/api, docs/adr [LOW]
   Three top-level doc directories stale at 91 days. ADRs are particularly high-value — stale ADRs mislead future contributors about past decisions. The broodly team should verify whether open ADRs have been resolved and update docs/api to reflect the current interface. Urgency: LOW (91 days).

3. petry-projects/TalkTerm — docs/ecc-for-bmad.md [LOW]
   Single file at 94 days, the oldest in this scan. The filename suggests it may be a one-off design note rather than living documentation. Owner should confirm if the ECC feature was shipped or abandoned and either update the doc or move it to an archive/ path. Urgency: LOW (94 days).