spectre-validate

validate

Post-implementation requirement validation. Verify the built work against scope docs and tasks.json slices, dispatch parallel validators per area, and produce one actionable gap-remediation document. Validation only — never fix.

Core principle (load-bearing)

Definition ≠ Connection ≠ Reachability. A requirement is only delivered if all three hold:

1. Defined — code exists in a file.
2. Connected — it is imported/called by other code.
3. Reachable — a user action can trigger the code path.

Level 1 without 2/3 is dead code that happens to match the description — not complete. Always trace past "X exists" → "X is called by Z at file:line" → "Z fires when the user does W."

Inputs

• $ARGUMENTS — explicit feature name/root or descendant artifact, scope docs, an explicit plan or fix/bug report, and/or tasks.json to validate against (paths, or "use thread context"), plus optional execution_state.md focus evidence, an immutable BASE_SHA/HEAD_SHA/DIFF_SHA256 candidate tuple, and --orchestrated when a parent workflow owns remediation and the next step. Requirement context is REQUIRED. If absent, ask for a scope, plan, fix/bug report, task detail JSON path, or "use thread context" — then wait.
• Treat the supplied plan, fix/bug report, or other explicit source as authoritative. Otherwise use task acceptance slices, scope docs, then usable thread context. Read the authoritative source in full. For tasks.json, extract validation slices from phases[] (parent title/description plus child acceptance criteria/context); do not use execute.md as the validation source except to locate the JSON path.

Working Set (late-bound — read at run-time, never inline)

• Reuse a managed FEATURE_ROOT only when explicit/current-thread evidence ties it to this work (physical directory wins; never branch/recency/lifecycle/scans); distinct work ignores ambient roots. Otherwise, including on collision, standalone MUST first load and follow Skill(spectre-feature-root) through DONE; orchestrated calls escalate. Keep writes beneath it and pass it unchanged.
• Repair stale feature/root metadata in artifacts this workflow touches.
• VALIDATION_REPORT = {FEATURE_ROOT}/validation/validation_gaps.md; create its parent directory.
• Read the actual code, diff, and explicitly supplied requirement artifacts just-in-time.