/spectre-execute

name: "spectre-execute"
description: "Execute tasks/plans with checks/reviews/proof. Use after planning/resume. Not for planning, unplanned fixes, or pruning."
user-invocable: true

execute

Preserve parallelism, authority, gates, repair.

Inputs

• `$ARGUMENTS`: path; `--origin plan|fix`; `--preflight-plan <xs|light|standard|comprehensive>`; wave hints; `--orchestrated`; orchestrated-only `--finalization-owner parent`. Default owner: `self`.
• `--review-profile final-only`, valid only with `--orchestrated --finalization-owner parent`; it defers intermediate review and requires the orchestrating caller to invoke `Skill(spectre-code_review)` exactly once; caller owns sequencing, never semantic review.
• `structured`: execute index + resolvable `tasks.json`; malformed structured input escalates, never becomes a plan.
• `fix-source`: bug-report path/root or identifying content—not `--origin`—selects `fix`; load `references/fix-source.md`, not Plan preparation.
• `plan-direct`: explicit readable plan, including paths, Plan handoff markers, and legacy `Execution Mode: direct` headers. The explicit supplied plan wins over ambient task artifacts and enters this preparation contract.
• No path: use existing same-run source evidence first, then a plan at the confirmed root, then structured-only fallback. No-path selected plans receive this preparation before dispatch. Never infer from branch/recency.
• `--preflight-plan <depth>` remains a preparation-depth hint, not authorization, classification, or task-graph switch; a depth hint must not create authority pause. `Execution Mode: direct` is a legacy coordination hint. No selected readable plan needs a completeness/header ceremony.

Working Set

• 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.
• Keep the invocation checkout.
• Structured detail precedence: declared `Tasks JSON` → adjacent `tasks.json` → sibling `.tasks.json`; else escalate. Read whole; detail targeted slices.
• Structured/plan-direct read `references/telemetry.md`, start/resume local event run with origin, follow primary/worker authority. Local workflow store is the sole lifecycle/progress authority; plans/tasks immutable. Summaries retain origin/shape/category/elapsed/aggregate tokens; Plan-direct emits events. Telemetry failure degrades observation, never delivery authority.
• `SCOPE_DOCS`: manifest paths or scope/UX/research cited by the plan.
• On first selected readable-plan use/resume, read `references/plan-direct.md` for preparation state. On the first verification failure, review finding, E2E gap, or proof failure, read `references/repair-policy.md`.
• Maintain compact verification ledger by HEAD, check id, changed/dependency surface, result, attribution, disposition; controls reruns. Never persist raw output or per-wave evidence/checkpoint/report files.

Outputs + DONE

• Commit implementation batches/canonical artifacts. Task/plan immutable; Execute evidence/state local/uncommitted.
• `self`: one final comprehensive review; proof ends `PASS`.
• `parent`: `IMPLEMENTATION_READY` + `ACCEPTANCE_PENDING` manifest; no final review, proof, or acceptance claim. With `--review-profile final-only`, every phase records `final-only` and the parent receives `FINAL_REVIEW_PENDING`.
• DONE: selected work/adaptations `done|skipped`; current affected verification; each phase `final-only` or reviewed once for recorded compounding risk; every finding dispositioned; no safe authorized work or stale/uncovered final surface; self final review + end-only proof when applicable; no primary-authored planned work; structured telemetry complete or honestly `degraded`.

Method / guardrails

• **Plan preparation.** For selected readable plans, resolve root, plan, Scope, depth/state before run creation. Reuse applicable `task_context.md` assessment by plan/authority hashes; after scope-safe byte-only review edits, rebind if topology/uncertainty is unchanged; reroute only if absent/materially invalidated. Missing assessment dispatches `Skill(spectre-plan-route)` to a fresh child agent for one classification. Hash-bound observed size, never depth, decides Plan Review: XS/S record `review:not-required:<size>` and skip; M+ reuse a closed correctness+simplification chain only with external-attempt/recorded-failure+fallback provenance, completed route/reports, finalized plan hash/disposition, and protected files unchanged; reject route-only/interrupted/`NOT DONE`; else resume hash-valid or user-decided partial correctness or dispatch `${PLUGIN_ROOT}/skills/spectre-execute/references/plan-review.md --auto-apply scope-safe --orchestrated` once to fresh child. Review-worthy risk reclassifies M+; no hidden XS/S exception. Mechanical repairs stay local; semantic corrections use child. Scope/explicit-design changes remain withheld; scope-safe result proceeds without a second user gate. ATOMIC/DIRECT use the bounded local workstream/Active Wave pattern. For STRUCTURED, pass finalized plan path/hash, closed review evidence, and assessment depth; STRUCTURED dispatches a fresh child with `${PLUGIN_ROOT}/skills/spectre-execute/references/create-tasks.md --orchestrated` (L → standard, XL → comprehensive). No automatic task review; when a user explicitly requests a task-graph audit, load `${PLUGIN_ROOT}/skills/spectre-execute/references/task-review.md`. Select only a validated pair bound to finalized plan and closed review chain. For all preparation children, consume child DONE inside the same Execute run before proceeding.

2. **Resolve and resume.** Persistent execution authority: on initial entry and every continuation/resume, including after compaction, reload