Skill Claude CodeCodex
Project kickoff — deep codebase + external research producing an evidence-backed kickoff doc, gap analysis, and MVP path before scoping. Use to start a fresh feature/project from an unclear problem, when the user wants research/options/an MVP recommendation before committing to scope or a plan. Do not trigger once…
Skill Claude CodeCodex
Use when the user invokes /learn or asks to remember, save, or capture a pattern, decision, gotcha, procedure, or feature dossier from this session for later re-use ("please remember", "what did we learn?"). Captures durable project knowledge as a canonical user-level record. Do NOT trigger for simple personal…
Skill Claude CodeCodex
Internal semantic classifier for spectre-plan. Use only from Plan with a bounded routing input; never for planning, artifacts, telemetry, or user gates.
Skill Claude CodeCodex
Orchestrate durable XS–XL planning after confirmed Scope, with adaptive artifacts, review, tasks, telemetry, and explicit pre-code approval. Do not use for scoping, bug diagnosis, read-only work, or execution of approved artifacts.
Skill Claude CodeCodex
Review plan.md for correctness, then simplify without repeated research. Use after createplan and before createtasks; do not review tasks/code or change scope.
Skill Claude CodeCodex
Create one self-contained HTML prototype to resolve ambiguity, validate flows, or render UX before planning. Use for prototype/mockup/preview requests and UX Stage 1→2; not for production code, multi-file apps, scope, or planning.
Skill Claude CodeCodex
Run one acceptance-proof pass over completed work and publish reviewed user-facing evidence. Use from spectre-execute or standalone for acceptance evidence, screenshots/video/logs, or an HTML proof artifact. Do NOT use for implementation checks, repairs, unit tests, planning, or code review.
Skill Claude CodeCodex
Find and remove confirmed-safe dead code and artifacts from a scoped working set — orphaned imports/exports, unused code, commented-out blocks, debug/temp logging, duplication, AI slop — while surfacing uncertain items for manual review. Use for dead-code/artifact cleanup only, standalone or as the prune phase inside…
Skill Claude CodeCodex
👻 | Safe guided git rebase — backup ref, auto-resolve conflicts, and either run affected post-rebase checks or hand advisory verification ownership to an orchestrating parent. Use to rebase the current branch onto a target (e.g. origin/main), especially when conflicts or post-rebase verification are expected. Do NOT…
Skill Claude CodeCodex
Research a codebase to answer a question — fan out read-only agents (finder/analyst/patterns, web-research for 3rd-party), then synthesize evidence-backed findings into a saved research doc with file:line citations. Use when the user asks "how does X work", "where does Y live", "investigate/research Z before…
Skill Claude CodeCodex
Scope a feature or improvement into explicit IN / OUT / ANTI-SCOPE boundaries before planning or code — grounds a hypothesis in repo reality, resolves blocking questions, and writes scope.md. Trigger for new or fuzzy work or re-scoping. Do NOT trigger for technical design/research (spectre-plan) or standalone bug…
Skill Claude CodeCodex
Turn completed branch work into a reviewer-ready PR: clean, rebase, observe one advisory full suite, repair/route failures, and open via spectre-createpr. Use when asked to ship finished work. Proof is optional. Do NOT use for implementation, main/master pushes, releases, or autonomous request-to-PR delivery.
Skill Claude CodeCodex
Light pre-commit cleanup pass — diff sanity, log/dead-code hygiene on changed files, strict affected lint, run related/affected tests, then conventional-commit. Use when wrapping up uncommitted or just-finished work before check-in ("sweep", "clean up and commit", "tidy this diff"), standalone or as the final phase of…
Skill Claude CodeCodex
Review tasks.json for correct, complete, executable translation of its reviewed plan before execute.md is finalized. Use for comprehensive task-graph review or explicit re-review. Do not review plan quality, finished code, index formatting, or change scope.
Skill Claude CodeCodex
Execute implementation via strict red/green/refactor — derive behavioral Test Opportunities, write a happy/failure baseline plus risk-justified cases, confirm RED before production code, then ship minimal GREEN code. Trigger for TDD, failing-test-first, or RED-GREEN-REFACTOR execution; not test auditing/planning (use…
Skill Claude CodeCodex
Triage a working set into risk tiers (P0–P3) and add risk-appropriate behavioral tests — thorough coverage where bugs hurt users (auth/payment/security/PII), light or none on low-risk code — fixing lint and committing per passing batch. Trigger after a feature is built or when asked to add/strengthen tests for recent…
Skill Claude CodeCodex
Codex-only Spectre uninstall workflow. Use when the user wants to uninstall the native spectre@spectre Codex plugin; cleans expired workflow data and removes managed Spectre custom agents before native plugin removal while preserving marketplace registration and project knowledge.
Skill Claude CodeCodex
Define exactly how a feature behaves — user flows, screens, components, states, copy, and accessibility — producing a definitive ux.md spec for implementation. Two stages: align on user flows, then write the detailed spec. Trigger after scope/PRD when a feature needs a behavioral/UX spec before planning or building…
Skill Claude CodeCodex
Validate that completed implementation actually delivers the scope/tasks requirements — chunks the work into areas, dispatches parallel @spectreanalyst validators that trace each requirement from user action to render, and writes one actionable validationgaps.md ranking what's Delivered / Partial / Dead Code /…
Plugin Claude Code
Contract-driven agentic coding workflow. spectre guides you through Scope, Plan, Execute, Clean, Test, Rebase, and Learn flows.
Agent
Explains HOW specific code works — traces data flow, call paths, and key logic, returning a cited implementation analysis. Use to understand existing behavior before planning or fixing. Do not use to locate files (use finder), critique quality, or recommend changes (use reviewer).
Agent
Implement or refactor code for an already-scoped task — writes/edits files, runs verification, returns a Completion Report. Use to build assigned features/refactors. Do not use for scoping, planning, design, review, or test authoring.
Agent
Locate files, directories, and components relevant to a feature or task and return grouped paths. Use to map where code lives before analysis or planning; do not use to explain how code works (use analyst) or to find reusable patterns (use patterns). Returns grouped file paths with search terms used, never…
Agent
Find existing in-repo implementations, usage examples, and conventions to model new work on, returning 2-5 cited code examples with a recommended best fit. Use to discover reusable patterns before writing similar code; do not use to locate files only (use finder), explain a single code path (use analyst), or…