Claude Code plugin packaging the SPEAR methodology — Spec-Proven Engineering with Architectural Requirements — as a reusable, installable plugin.
SPEAR is a hybrid of Spec-Driven Development (EARS), Test-Driven Development (red-green-refactor), and Hexagonal Architecture. The plugin enforces the cycle — blocking implementation before a failing test and blocking progression past a layer-boundary violation — and automates the boilerplate: scaffolding the four SPEAR docs, assigning REQ-IDs, tracking per-task phase in a gitignored state file.
The cycle:
spec → prove → engine → arch → refine
Each phase is its own /spear:<name> skill. A session-start hook injects the cycle rules, current phase, and tool-probe results into every Claude Code session that runs in a SPEAR project.
/plugin marketplace add BadgersMC/spear-plugin
/plugin install spear@BadgersMC-spear-plugin
/plugin reload-plugins
Claude Code caches the plugin at ~/.claude/plugins/cache/BadgersMC-spear-plugin/spear/<version>/.
/spear:init
Detects language/build tool, drafts docs/tech-stack.md, docs/requirements.md, docs/implementation.md, docs/tasks.md from bundled templates, and on JVM projects drops a Konsist LayerRulesTest.kt wired to your top-level package. Commits the result.
/spear:spec # draft or revise a REQ + derive tasks
/spear:prove # write the failing test (TDD only)
/spear:engine # minimum code to flip red → green (TDD only)
/spear:arch # layer-rule + framework-annotation scan on the diff
/spear:refine # refactor, confirm suite green, flip task [x], reset state
DOC/INFRA tasks skip prove and engine (spec-done → arch directly).
Designed to run alongside superpowers. SPEAR defers to superpowers for brainstorming, writing-plans, executing-plans, and systematic-debugging. Inside a SPEAR project (docs/requirements.md + docs/tasks.md both present), spear:prove supersedes superpowers:test-driven-development; outside it no-ops back to the superpowers entry point.
- Design spec — why it exists and what it does.
- Requirements — EARS-formatted REQ-IDs.
- Implementation — architecture, data flows, layer rules.
- Tasks — current work.
- Contributing — dev workflow.
- Testing — manual E2E checklist and CI overview.
See LICENSE.