HE Doc Gardening
Run this skill periodically to keep docs accurate and aligned with shipped behavior.
Frequency
- •Weekly by default
- •Also after large releases or high-review-noise periods
Scan Targets
Launch parallel subagents to scan each target area concurrently:
- •Repeated review findings and regressions
- •Stale or contradictory docs
- •Dead links or outdated references
- •High-churn or complexity hotspots
- •Flaky test patterns
- •Stale generated context in
docs/generated/(checklast_updatedtimestamps)
Each subagent scans one area and returns a list of drift findings with priority. The main thread consolidates and queues fix-up work.
Outputs
- •Update
docs/plans/tech-debt-tracker.md - •Update
docs/QUALITY_SCORE.mdtrend notes - •Refresh stale generated context files in
docs/generated/ - •Create one or more doc-fix specs and plans:
- •
docs/specs/<slug>.md - •
docs/plans/active/<slug>.md
- •
Keep each doc-fix plan small and independently shippable.
Record drift findings with explicit priority.
Doc-Gardening Rule
- •Doc-gardening work should not block feature delivery unless a critical invariant is broken.
- •Critical invariant violations must be escalated and prioritized immediately.
Exit Gate
- •Drift findings are documented
- •Cleanup initiatives are queued as normal slug-based specs/plans
- •Docs commit gate passes
Transition Options
Present 2-3 explicit next-step options with a recommended default. Use request_user_input (Codex) or AskUserQuestion (Claude Code) in Plan mode; otherwise ask in chat. Wait for user selection before proceeding.
At least one option must be Next step: he-intake for a cleanup initiative slug.