# Speck Recheck

> Detects engagement drift. Use before project work in new or stale sessions, after ownership changes, or on recheck.

- Skill: `telum-ai/speck-recheck` (Agent Skill)
- Install (CLI): `npx skillmds@latest add telum-ai/speck-recheck`
- Raw SKILL.md: https://api.skillmd.com/api/skills/telum-ai/speck-recheck/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: telum-ai (https://skillmd.com/u/telum-ai)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/telum-ai/speck-recheck

---


# speck-recheck

Engagement-gap drift detector. Run before project work when session continuity or current truth is not established.

Input: `$ARGUMENTS`.

## When to run (mandatory)

- >14 days since latest truth artifact `verified` stamp
- New agent / no session continuity; fresh artifacts and a named Next action do not waive this trigger
- User requests audit, "make ship-ready", "is this still working"
- `project-state.md` Next action unknown or empty
- `.speck/.v8-reprove-needed` exists OR `staleness-check.sh` reports `V8_STALE` (stamp `< speck 8`) → `V8_REPROVE.P1`; route `/speck-migrate` before other drift work

Recommended: major dependency updates; multiple parallel branches merged since last validation.

## Prerequisites

- Speck project (`specs/projects/<id>/`)
- Git repository

## 1. Locate project

Find project dir. Play level from `.speck/project.json`. Required checks: `project-state.md`, truth artifacts per play level, `product-contract.md`, `evidence-contract.md`.

## 2. Parallel drift detection

Run in parallel where host supports subagents; else sequential:

```bash
bash .speck/scripts/staleness-check.sh
bash .speck/scripts/check-replace-markers.sh specs/projects/<id>/
bash .speck/scripts/banned-language-lint.sh
bash .speck/scripts/profile-drift-check.sh          # when PROFILE integrated
bash .speck/scripts/settings-drift-check.sh         # when .claude/settings.json exists
bash .speck/scripts/asset-drift-check.sh            # when UI/brand assets exist
bash .speck/scripts/validation/validators/validate-schema-drift.sh   # DB-backed
# For each DEC-NNNN superseded since the last verified recheck:
bash .speck/scripts/validation/validators/compute-cascade.sh --dec DEC-NNNN --strict
bash .speck/scripts/validation/validators/compute-eval-signals.sh --strict
bash .speck/scripts/market-staleness-check.sh       # when product-contract.md exists
bash .speck/scripts/market-reconcile-check.sh
bash .speck/scripts/validation/validators/validate-gate-liveness.sh specs/projects/<id>/evidence-contract.md
bash .speck/scripts/validation/validators/validate-project-analysis.sh --gate specs/projects/<id>
python3 .speck/scripts/graph/speck_graph.py build specs/projects/<id> && python3 .speck/scripts/graph/speck_graph.py check specs/projects/<id>
grep -rln "\[NEEDS USER REVIEW\]" specs/projects/<id>/
```

Subagent scans (when available):
- Spec-vs-code reconciliation (product-contract / PRD / architecture assertions vs code)
- Third-party integration risk (auth model, ToS, data residency) — vendor docs via Context7 / official docs JIT
- Constitution principle compliance

Each check returns: FRESH | STALE | DRIFTED | MISSING with evidence.

### REPLACE_BEFORE_SHIP markers

Token present → artifact incomplete; cannot support readiness above IMPL-GREEN.
- Referenced by active UX-RC+ claim → P0
- Otherwise → P1
- Remediation: `/speck-migrate`

### Graph drift codes

`DANGLING_REF.P1`, `DUP_ID.P1`, `UNMAPPED_PROMISE.P1`, `PHANTOM_PROMISE.P1`, `DEP_CYCLE.P1`. `GRAPH_CAP` / `GRAPH_UNMIGRATED.P3` advisory.

### Analysis gate codes

`UNANALYZED_CORPUS.P1`, `ANALYSIS_STALE.P1`, `ANALYSIS_CRITICAL_OPEN.P1`, `PROMISE_UNCOVERED.P1`, `ANALYSIS_DECORRELATION_UNVERIFIED.P2`, `ANALYSIS_COVERAGE_UNCOMPUTED.P2`, `ANALYSIS_GRANDFATHERED.P2`.

Grandfather marker: surface uncollapsed every recheck; one `/analyze --level project` spends it (`check-epic-prereqs.sh` prints `rm` command).

### Mutation codes (`GUARD_*`)

From `mutate-guard.sh` → `SPECK_MUTATION_VERDICT=<code>`:

| Code | Meaning |
|------|---------|
| `GUARD_MUTATION_PROVEN` | Not a finding; carry as evidence |
| `GUARD_MUTATION_GREEN.P2` | Mutation happened; suite missed it — honest, non-blocking |
| `GUARD_MUTATION_UNOBSERVABLE.P2` | Subject needs `--applier`; test could not see mutation |
| `GUARD_UNMUTATED.P2` | Nothing measured; AC not discharged |
| `GUARD_UNMUTATED_HARNESS.P2` | Harness could not run probe |

### Observation codes (`OBSERVATION_*`)

From `observe-guard.sh` → `SPECK_OBSERVATION_VERDICT=<code>`:

| Code | Meaning |
|------|---------|
| `OBSERVATION_EXPOSED` | Not a finding; instrument shown able to display thing |
| `OBSERVATION_UNEXPOSED.P2` | Green licenses only waiting — non-blocking |
| `OBSERVATION_UNEXPOSED_BLOCKING.P1` | Green licenses accumulating/irreversible act — run does not count |
| `OBSERVATION_NOT_GREEN.P1` | Observation failed; cancelled CI ≠ pass |
| `OBSERVATION_UNMEASURED.P2` | Nothing measured; destructive invocation refused |

## 3. Persona LARP cold-start

**consumer_product / b2b_saas / internal_tool**: per persona in `personas/<id>.md`, cold-start app (clean storage), execute LARP script, capture evidence vs product-contract magic moments. Use `/speck-larp`.

**infra_service / backend_api**: run integration/stress scenarios from evidence-contract Option B.

Any failure → P0 drift.

## 4. Synthesize drift report

Per finding: severity (P0–P3), type code, location, evidence, recommended fix.

Finding types include: SPEC_VS_CODE, TRUTH_STALE, TEMPLATE_DRIFT.P1/P2, LARP_FAIL, INTEGRATION_RISK, PRINCIPLE_VIOLATION, BANNED_LANGUAGE, PROFILE_DRIFT.P1/P2/P3, SETTINGS_DRIFT.P0, SCHEMA_DRIFT.P0, CASCADE_STALE.P1, MARKET_DRIFT.P1/P2, WEDGE_DRIFT.P1/P2, GATE_WIRING_DRIFT.P1, V8_REPROVE.P1, plus GUARD_* and OBSERVATION_* above.

## 5. Update project-state.md

Invoke `/project-state`. Populate blocking issues (P0/P1), truth staleness, `[NEEDS USER REVIEW]` appendix, REPLACE marker appendix. Next action: resolve drift before feature work.

## 6. Decision gate

| Finding | Action |
|---------|--------|
| `V8_REPROVE.P1` | BLOCK feature work → `/speck-migrate` first |
| P0 drift | BLOCK feature work; surface remediations; recommend `/speck-audit`; refuse `/story-implement`, `/epic-plan` |
| `MARKET_DRIFT.P1` / `WEDGE_DRIFT.P1` | Do not block implement; BLOCK COMMERCIAL-RC/SHIP-RC and spec-derived marketing copy until `/speck-frontier-scan --product` or `/adjust --level project` |
| Analysis P1 codes | Do not block in-flight story; BLOCK next `/epic-specify` until `/analyze --level project` clears |
| `ANALYSIS_GRANDFATHERED.P2` | Never block; surface loudly every recheck |
| P1–P3 only | Surface; user proceeds at discretion |
| No drift | Before re-stamp: run `observe-guard.sh --licenses accumulating` on observation-based findings; `OBSERVATION_UNEXPOSED_BLOCKING.P1` → hold those artifacts; re-stamp rest. Otherwise re-stamp all truth artifacts with fresh `verified` date |

## 7. Write report

Path: `specs/projects/<PROJECT_ID>/project-recheck-report-<YYYYMMDD>.md`. Template in skill references.

```bash
bash .speck/scripts/stamp-truth.sh specs/projects/<PROJECT_ID>/project-recheck-report-<YYYYMMDD>.md
```

Report summary per skill template. Always write dated report even if green.

## NEVER / ALWAYS

- NEVER skip persona LARP cold-start (when product type requires it)
- NEVER replace a mandatory recheck with file inspection; a blocked required command is a P3 finding, not recheck completion
- NEVER claim "no drift" without running staleness-check, banned-language-lint, check-replace-markers, and applicable drift scripts listed in §2
- NEVER mark artifact fresh while `REPLACE_BEFORE_SHIP:` or `[NEEDS USER REVIEW]` remain
- NEVER let OBSERVATION close P0 or re-stamp without checking what green licenses
- NEVER treat cancelled/skipped CI as pass (`OBSERVATION_NOT_GREEN.P1`)
- NEVER report `ANALYSIS_COVERAGE_UNCOMPUTED.P2` as coverage pass
- NEVER collapse `ANALYSIS_GRANDFATHERED.P2` across sessions
- NEVER hand-write `*[market-verified …]*` stamp (only `stamp-market.sh`)
- ALWAYS write dated report
- ALWAYS update `project-state.md` regardless of verdict
- ALWAYS route `/speck-migrate` when a compatibility marker or V8_STALE finding is present
- BLOCK feature work on P0

## Integration

Reads: truth artifacts, personas, staleness/replace-marker scripts.
Invokes: `/speck-larp`, `/project-state`.
Writes: dated recheck report; re-stamps truth artifacts on green.

## Host portability

Subagent parallelization (speck-scanner, speck-auditor) preferred on Claude; Cursor/Codex run core scripts sequentially in main context. Evidence requirements identical across hosts.