spectre-capture
Capture durable project decisions, accepted corrections, verified reusable patterns or gotchas, disproved guidance, and changed…
Create a repository-grounded aligned draft after confirmed Scope, present its concise alignment brief, and hand it to Execute preflight. Do not use for scoping, bug diagnosis, read-only work, or execution of approved artifacts.
$ npx -y skills add joenandez/spectre --skill spectre-plan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/spectre-planContext preview
The summary Claude sees to decide when to auto-load this skill.
Create a repository-grounded aligned draft after confirmed Scope, present its concise alignment brief, and hand it to Execute preflight. Do not use for scoping, bug diagnosis, read-only work, or execution of approved artifacts.
name: "spectre-plan" description: "Create a repository-grounded aligned draft after confirmed Scope, present its concise alignment brief, and hand it to Execute preflight. Do not use for scoping, bug diagnosis, read-only work, or execution of approved artifacts." user-invocable: true disable-model-invocation: true
Turn confirmed Scope into the smallest draft and handoff. `spectre-plan-route` classifies; primary owns plan. Scope remains immutable.
Every route writes `specs/plan.md` and `task_context.md` with Scope/authority-bound `## Minimum Solution Selection`; no review/task/index/task-review artifacts.
DONE when `task_context.md` binds initial/observed routing to draft/authority hashes; Scope is unchanged; `plan.completed` records draft; handoff gives alignment/Trade-offs; telemetry is `complete|degraded`, or authority/scope stops it.
Child skill DONE is internal: resume the next Plan step in this turn. Only Plan's own handoff or escalation ends it.
1. Unresolved journeys/states/copy/accessibility route to `spectre-ux`; load-bearing interaction/layout validation routes to `spectre-prototype`. 2. Scan once; invoke `Skill(spectre-plan-route)` in `initial` mode. Never print its record; its DONE and limits end at the record. In the same response, run `node "${PLUGIN_ROOT}/hooks/scripts/workflow-cli.mjs" plan start` with root/scope hash, record, size/route, reasons, design/probe flags, boundaries; retain `PLAN_RUN_ID` for `plan.started`. Report size/rationale in one progress line beside that call; continue to step 3. 3. Gather proportional evidence: XS/S local except probe; M ≤2 relevant `@spectre_finder`, `@spectre_analyst`, or `@spectre_patterns`; L/XL necessary dimensions. Live external captures belong to Execute, never Plan's evidence dispatch. Dispatch no dimension cited by path, knowledge ID/revision, or thread decision; `evidence: SUFFICIENT` with uncertainty below HIGH and full citation gathers locally at any size. The fresh evidence-only challenger is wave-independent: M triggers it for durable state, identity, public contract, migration, dependency, or workflow/lifecycle; L/XL always, with the wave or alone. Primary persists accepted evidence/IDs/revisions in `task_context.md`. `@spectre_web_research` only decides external API/framework. Refine knowledge search after affected files are known; load a work body only for a stated question, never reload an unchanged revision, and pass workers compact findings with provenance. 4. Read `references/minimum-solution.md` after initial classification. From accepted evidence, select incumbent-first and persist `## Minimum Solution Selection` in `task_context.md`, bound to Scope/authority/accepted evidence. XS/S decide locally; primary applies the canonical simpler-wins result. 5. Invoke `Skill(spectre-plan-route)` in `observed` mode with completed selection before drafting; never print its record, and continue to step 6 in the same response. Plan automatically uses the observed route with no paid rerun or user tier gate unless Scope, explicit design, or authority conflicts. 6. Draft once by loading `${PLUGIN_ROOT}/skills/spectre-plan/references/create-plan.md` with the observed route-mapped depth: XS → `light --no-review --execution structured`; S inherits it; M/L → `standard --no-review --execution structured`; XL → `comprehensive --no-review --execution structured`. Never review/task here. XS uses `light`, not `xs`, so no `Execution Mode: direct`. 7. Validate Routing Observations and owned concepts conform to selected record; emit `plan.reclassified` with plan hash, records, regret. Append observed record to `task_context.md` with draft raw-byte hash plus Scope/authority hash; emit unchanged `plan.completed` artifact hashes/counts/planning elapsed. Telemetry failure is degraded and never blocks handoff. 8. From `specs/plan.md` derive requested outcome, approach, material decisions, Scope/anti-scope boundaries, credible risks, verification intent, and ordering/shared-contract constraints. Immediately before Execute show Trade-offs verbatim (`None` allowed): Execute accepts them; feedback revises the draft. On Scope change, selected-design conflict, missing irreversible decision, or unavailable authority, withhold the handoff. Otherwise return exactly one copy-ready fenced command: `$spectre:spectre-execute <repo-relative plan.md> --origin plan --preflight-plan <xs|light|standard|comprehensive>`. observed XS → xs; S → l
SPECTRE is an Agentic Engineering workflow for Claude Code and Codex designed to help you do ONE THING more, faster, and with higher quality.
Capture durable project decisions, accepted corrections, verified reusable patterns or gotchas, disproved guidance, and changed…
Run final adversarial review through a pinned high-effort opposing runtime with one native fallback. Use at the final boundary to…
Generate a grounded draft pull request from the actual diff and open it via gh. Use when wrapping up a branch or writing a PR…
Assess and repair a project's Spectre knowledge, work history, tags, and retrieval quality through primary-led decisions,…
Execute tasks/plans with checks/reviews/proof. Use after planning/resume. Not for planning, unplanned fixes, or pruning.
Internal initializer for a missing Spectre feature root. Invoke only from a standalone workflow with no confirmed managed root.…