Spectre is a battle-tested 6 stage agentic engineering workflow for building complex, production-ready features. You stay in the loop for the decisions that matter. Your agents handle the the rest. One command to start building - /spectre:scope
This repository also configures its own agents. See what spectre tells them →
Skill Claude Code
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: directly coordinate cleanup, rebase, one advisory full suite, repair/route failures, and 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 Code
Light pre-commit cleanup pass — diff sanity, log/dead-code hygiene, stale/uncovered integrated checks, then conventional-commit. Use standalone or as the final phase of spectre-clean/ship. Do NOT use for forensic cleanup (spectre-prune), authoring tests (spectre-test), or full validation.
Skill Claude Code
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 Code
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 Code
Triage a working set into risk tiers (P0–P3) and add risk-appropriate behavioral tests. Trigger after a feature is built or when asked to add/strengthen tests; when orchestrated by spectre-clean/ship, consume the parent risk plan and assigned test/fixture batch. Do NOT trigger for brute-force coverage, cleanup…
Skill Claude Code
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 user flows, screens, states, copy, and accessibility in ux.md. Two stages: align flows, then specify. Use after scope/PRD for behavioral UX; not backend, scope, or architecture.
Skill Claude Code
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 /…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: