harness-documentation-maintainer

Role

Detect documentation drift, validate doc coverage, align docs with code changes, run full documentation health pipeline

Skills

• detect-doc-drift
• align-documentation
• harness-knowledge-mapper
• validate-context-engineering
• harness-docs-pipeline

Steps

1. Run harness check-docs (always)
2. Run harness validate (always)
3. Run harness scan (always)

Methodology

Detect Doc Drift

Detect documentation that has drifted from code. Find stale docs before they mislead developers and AI agents.

When to Use

• After completing a feature, bug fix, or refactoring
• During code review — check if the changed files have associated docs that need updating
• As a periodic hygiene check (weekly or per-sprint)
• When on_post_feature or on_doc_check triggers fire
• When onboarding reveals confusion caused by outdated documentation
• NOT during active development — wait until the code is stable before checking docs
• NOT for writing new documentation from scratch (use align-documentation instead)

Process

Phase 1: Scan — Run Drift Detection

1. Run harness check-docs to identify all documentation issues. Capture the full output.

2. Run harness cleanup --type drift for a deeper analysis that cross-references code changes against documentation references.

3. Check for stale constraints. Run detect_stale_constraints alongside drift detection to find architectural constraints that no longer match the codebase.

4. Optionally, run git diff against a baseline (last release, last sprint, etc.) to identify which code files changed. This helps prioritize — docs for recently changed files are most likely to be drifted.

Graph-Enhanced Context (when available)

When a knowledge graph exists at .harness/graph/, use graph queries for faster, more accurate drift detection:

• query_graph — find documents edges where the target code node has changed since the doc node was last updated