Executive Summary
Status: STALE_DOCS_FOUND
Stale files: 12
Key findings:
- Most stale:
petry-projects/TalkTerm/docs/ecc-for-bmad.md — 129 days without a commit (owner not determinable from available data)
- Largest cluster:
petry-projects/google-app-scripts/docs/ — 8 files all last touched 2026-03-28 (127 days stale), suggesting a bulk-generated doc set that was never maintained
- Secondary cluster:
petry-projects/broodly/docs/ — 3 directory-level doc trees (architecture, api, adr) all stale at 126 days
Action required: Review each stale doc tree with the owning team and either refresh, archive, or redirect to the authoritative source within the current sprint.
Stale Files by Repo
petry-projects/TalkTerm
| File |
Last Updated |
Days Stale |
docs/ecc-for-bmad.md |
2026-03-26 |
129 |
petry-projects/google-app-scripts
| File |
Last Updated |
Days Stale |
docs/source-tree-analysis.md |
2026-03-28 |
127 |
docs/project-scan-report.json |
2026-03-28 |
127 |
docs/project-overview.md |
2026-03-28 |
127 |
docs/index.md |
2026-03-28 |
127 |
docs/development-guide.md |
2026-03-28 |
127 |
docs/deployment-guide.md |
2026-03-28 |
127 |
docs/component-inventory.md |
2026-03-28 |
127 |
docs/architecture.md |
2026-03-28 |
127 |
petry-projects/broodly
| File |
Last Updated |
Days Stale |
docs/architecture |
2026-03-29 |
126 |
docs/api |
2026-03-29 |
126 |
docs/adr |
2026-03-29 |
126 |
Recommendations
-
petry-projects/google-app-scripts/docs/ — team unknown [LOW]
Eight files all stale at 127 days, likely generated in a single doc-generation pass and never revisited. The presence of project-scan-report.json suggests automated output. Suggested action: archive or delete the generated artifacts (project-scan-report.json, source-tree-analysis.md) and refresh the hand-authored guides (development-guide.md, deployment-guide.md, architecture.md) against the current codebase. If the repo is no longer actively developed, add a repo-level deprecation notice and redirect to the current authoritative source.
-
petry-projects/broodly/docs/ — team unknown [LOW]
Three doc directories (architecture, api, adr) stale at 126 days. ADRs are append-only by convention, so staleness there may be acceptable; flag for a quick triage pass. The api and architecture directories should be refreshed or confirmed still accurate before the next onboarding or external integration. Urgency rises if broodly has active consumers.
-
petry-projects/TalkTerm/docs/ecc-for-bmad.md — team unknown [LOW]
Single file, 129 days stale. Narrow scope — refresh or archive depending on whether ECC integration with BMAD is still in scope. If the feature shipped or was abandoned, convert the file to a brief record of the decision and close it out.
Executive Summary
Status: STALE_DOCS_FOUND
Stale files: 12
Key findings:
petry-projects/TalkTerm/docs/ecc-for-bmad.md— 129 days without a commit (owner not determinable from available data)petry-projects/google-app-scripts/docs/— 8 files all last touched 2026-03-28 (127 days stale), suggesting a bulk-generated doc set that was never maintainedpetry-projects/broodly/docs/— 3 directory-level doc trees (architecture, api, adr) all stale at 126 daysAction required: Review each stale doc tree with the owning team and either refresh, archive, or redirect to the authoritative source within the current sprint.
Stale Files by Repo
petry-projects/TalkTermdocs/ecc-for-bmad.mdpetry-projects/google-app-scriptsdocs/source-tree-analysis.mddocs/project-scan-report.jsondocs/project-overview.mddocs/index.mddocs/development-guide.mddocs/deployment-guide.mddocs/component-inventory.mddocs/architecture.mdpetry-projects/broodlydocs/architecturedocs/apidocs/adrRecommendations
petry-projects/google-app-scripts/docs/— team unknown [LOW]Eight files all stale at 127 days, likely generated in a single doc-generation pass and never revisited. The presence of
project-scan-report.jsonsuggests automated output. Suggested action: archive or delete the generated artifacts (project-scan-report.json,source-tree-analysis.md) and refresh the hand-authored guides (development-guide.md,deployment-guide.md,architecture.md) against the current codebase. If the repo is no longer actively developed, add a repo-level deprecation notice and redirect to the current authoritative source.petry-projects/broodly/docs/— team unknown [LOW]Three doc directories (architecture, api, adr) stale at 126 days. ADRs are append-only by convention, so staleness there may be acceptable; flag for a quick triage pass. The
apiandarchitecturedirectories should be refreshed or confirmed still accurate before the next onboarding or external integration. Urgency rises ifbroodlyhas active consumers.petry-projects/TalkTerm/docs/ecc-for-bmad.md— team unknown [LOW]Single file, 129 days stale. Narrow scope — refresh or archive depending on whether ECC integration with BMAD is still in scope. If the feature shipped or was abandoned, convert the file to a brief record of the decision and close it out.