MarkdownLLM: Command for Claude Code

Write a type: retrospective thing for this domain (periodic quality reflection; see {framework_root}/retrospective.md), then run the reflexive scans that spec binds to this ritual. retrospective.md → Reflexive Scans At Retrospective owns each scan's definition and its number; this file is the invocation, and until 2026-09-08 it fired three of the seven — the net beneath the net was never wired to the hand that casts it.

1. If the cadence chase fired at session start (the digest's fired-trigger line on the latest retrospective) — first check the gate: if things/ has not moved since that retrospective's period_end, re-date the chase and stop. Otherwise run the mechanical scans now (3 and 4 below, the orphan findings from validate, and the held reasons for 7) and offer the rest as the session's first item; "not now" defers it and the trigger stays fired. An unattended run performs the whole ritual but writes the retrospective as status: draft, raises cues for what it modified, and files every ruling to the seat — it never answers a cue and never marks it complete (retrospective-cadence-is-a-dated-chase-2026-09-13).
2. detect-conflicts (scan mode; spec scan 1) — sweep every linked_things edge across the domain for contradictions; {framework_root}/templates/prompts/detect-conflicts.md.
3. Triage every open conflict (spec: What A Retrospective Produces, item 3) — walk things/conflicts/ at status: open, the whole set and not only what the floor aged, and force a disposition on each: rule (superseded / both-valid / dismissed → status: resolved), link it from the work that will resolve it, or hold it with disposition: keep-active + a disposition_reason naming what would resolve it. Creation runs at three cadences; this and the end-session brake are the two that read.
4. review-schema-coherence (spec scan 2) — audit the emergent frontmatter vocabulary for fields that have drifted apart in name but converged in meaning; {framework_root}/templates/prompts/review-schema-coherence.md.
5. Index rebuild (spec scan 3) — python {framework_root}/tools/mdllm.py index . rebuild. The floor refuses a drifted index at every commit, so this resets the provenance anchors to the period's end; content parity never depended on it.
6. Change-driven reconciliation (spec scan 4) — for every change the period landed without a declared inflection, run the backward pass ({framework_root}/change-reconciliation.md → Retrospective Reconciliation): freeze a baseline, reconstruct the delta from git log over the period, assimilate each changed thing's affected set (mdllm touchpoints), walk it, and seal contradictions as type: conflict things. This is the only pass that catches an inflection nobody declared — including every change an unattended agent commits.
7. Insight triage and consolidation (spec scan 5) — a read of the reckoning: mdllm reckon names the insights that have earned a disposition (orphaned, cited-and-never-promoted, promotable) and mdllm reckon --composition the merge candidates — pairs sharing two or more linked_things targets, a shared spec counting for nothing (a pair sharing only specs needs three). Judge each: promote (promoted_to), dismiss, consolidate into one survivor, or hold with --keep.
8. Conditions-met pass (spec scan 6) — the holds mdllm reckon lists as due, plus any hold the period's events plainly met before its date: read each disposition_reason and rule on it; --keep re-dates the rest.
9. review-skill-coherence (spec scan 7) — read the skills and the entry file against the commit stream since the last retrospective and force a per-skill disposition (confirm-current / update / park / retire); fold what the reckoning says to promote into the skill that carries it, promoted_to set — the walk gate takes it from there; {framework_root}/templates/prompts/review-skill-coherence.md.