2026-10-13 16:45:12 +08:00
|
|
|
---
|
|
|
|
|
name: check
|
|
|
|
|
description: >
|
2026-10-30 12:40:16 +08:00
|
|
|
Audit an existing SPEC.md against code when asked to check drift, audit the spec, or compare spec versus implementation.
|
|
|
|
|
scope: global
|
2026-10-13 16:45:12 +08:00
|
|
|
---
|
|
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
# Spec drift audit
|
2026-10-13 16:45:12 +08:00
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
Read-only: inspect files and available evidence; do not edit, sync, or commit.
|
|
|
|
|
If no `SPEC.md` exists, report that fact without creating one.
|
2026-10-13 16:45:12 +08:00
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
1. Read the requested sections; default to §V, §I, and §T.
|
|
|
|
|
2. For invariants, distinguish supported behavior, demonstrated violations, and
|
|
|
|
|
missing evidence. A test's presence alone does not prove an invariant holds.
|
|
|
|
|
3. Compare public interfaces with implementations and callers; identify missing,
|
|
|
|
|
extra, or changed contracts with file/line evidence.
|
|
|
|
|
4. Check task completion against the promised behavior, rather than only whether
|
|
|
|
|
named files exist. Report incomplete or stale statuses.
|
|
|
|
|
5. Give concise findings, evidence, and useful remedies. Do not launch refactors,
|
|
|
|
|
impose release gates, or run test commands that would violate read-only scope.
|
