spec-enforcelisted

SDD spec enforcement orchestrator. Runs the 20-row execution manifest against the current diff (or full spec on scope=all). Detects forbidden content, REQ-shape violations, status drift, meta-leakage, changelog drift, backlog state, source-anchor truth-check (CQ-SOURCE — always runs). Conditionally invokes spec-enforce-ac (when ACs touched) and spec-enforce-truth (when Implemented or Partial REQs touched or scope=all — Partial included so CQ-SOURCE can validate anchors). Invoked by spec-reviewer on every PR-boundary trigger and by /sdd clean.
nikolanovoselec/codeflare · ★ 24 · Code & Development · score 71

Install: claude install-skill nikolanovoselec/codeflare

# Spec Enforcement (orchestrator) This skill is the spine for SDD spec enforcement. It runs the 20-row execution manifest against `sdd/` and orchestrates the conditional detail skills (`spec-enforce-ac`, `spec-enforce-truth`). ## Inputs - `diff`: git diff against base (PR-boundary triggers) OR full-tree view (scope=all) - `scope`: `all` | `diff` (default `diff`) - `mode`: `interactive` | `auto` | `unleashed` (read from `sdd/spec/config.yml` when nested layout exists, else `sdd/config.yml` on flat layout) - `layout`: `nested` | `flat` (auto-detected via `test -d sdd/spec`) **Layout-awareness.** All file globs in this skill respect the detected layout: - Spec files: `sdd/spec/**/*.md` (nested) OR `sdd/*.md` excluding `README.md` (flat) - Config: `sdd/spec/config.yml` (nested) OR `sdd/config.yml` (flat) - Triage / escalation: `sdd/spec/.review-queue.md` (nested) OR `sdd/.review-needed.md` (flat, legacy) The flat layout is supported during the migration window; `/sdd clean` migrates flat → nested on demand. Both layouts coexist correctly in this skill. ## Execution contract (binding) Every row of the manifest below MUST execute on every run. No cherry-picking; cost is never a valid skip. Manifest written FIRST with all rows `pending`, updated as each rule completes, finalised at run end. Pending rows at finalize emit HIGH `manifest-pending-at-finalize`. Status rows without concrete evidence counts (`ran (N REQs, M findings)`) emit HIGH `manifest-bare-evidence-count`. "skip