---
name: verify-docs-current
version: "1.0.0"
description: "Verify documentation accuracy against current code"
category: "validation"
context_budget_estimate: "20K tokens"
typical_context_usage: "10%"
prerequisites: []
outputs:
  - "Verification report with accuracy status"
  - "List of outdated line references"
  - "Link validation results"
next_commands: []
related_agents: ["context-engineer"]
examples:
  - command: "/verify-docs-current src/services/payment.py"
    description: "Check documentation for payment service"
  - command: "/verify-docs-current src/api/routes.py"
    description: "Verify API routes documentation"
exit_criteria:
  - "All affected workflows checked"
  - "Line number accuracy calculated"
  - "Links validated"
  - "Status reported (HEALTHY/NEEDS UPDATE/STALE)"
---

# Verify Documentation Currency

**Purpose:** Validate that documentation matches current code

**Syntax:** `/verify-docs-current [file_path]`

**Example:**
```bash
/verify-docs-current src/services/payment.py
```

---

## What This Command Does

1. Look up modified file in CODE_TO_WORKFLOW_MAP.md
2. Find all workflows that document this file
3. For each workflow:
   - Extract [Line XXX] references
   - Read actual code at those lines
   - Verify function/logic still exists (±10 lines tolerance)
4. Check all markdown links resolve
5. Generate accuracy report

---

## Output Format

```
VERIFICATION REPORT

File: [path/to/file]
Affected Workflows: X

[workflow_1.md]:
  ✅ Line XXX (function_name) - Accurate
  ⚠️ Line YYY (other_func) - Shifted to line ZZZ
  ❌ Line AAA (deleted_func) - NOT FOUND

Links: X/Y valid (Z%)
Overall: HEALTHY / NEEDS UPDATE / STALE
```

---

## Actions Based on Result

| Status | Action Required |
|--------|-----------------|
| HEALTHY | No action needed |
| NEEDS UPDATE | Update line numbers |
| STALE | Re-document workflow section |

---

## When to Run

- After ANY code modification
- Before deploying
- Monthly as maintenance check

---

## k0ntext CLI Commands

This command integrates with the following k0ntext CLI commands:

| Command | When to Use |
|---------|-------------|
| `k0ntext drift-detect` | AI-powered drift detection across all documentation |
| `k0ntext fact-check` | Validate documentation accuracy for quality assurance |
| `k0ntext search <query>` | Find related documentation before verification |

### Command Examples

```bash
# Detect documentation drift using AI
k0ntext drift-detect

# Fact-check specific documentation
k0ntext fact-check

# Search for related files
k0ntext search "authentication flow"
```

### Workflow Integration

When verifying documentation:
1. **Before verification:** Run `k0ntext drift-detect` to identify potential issues
2. **During verification:** Use search to find related documentation
3. **After verification:** Run `k0ntext fact-check` for additional validation
4. **For updates:** Use `k0ntext sync` to propagate changes across tools