circuit

Circuitry

One command. The right workflow. No babysitting.

You describe your task. Circuitry classifies it, picks the right workflow, and runs it. Research before decisions, decisions before code, independent review before shipping. If a session dies, the next one picks up where it stopped.

Get Started

Install from the plugin marketplace:

/plugin marketplace add petekp/circuitry
/plugin install circuit@petekp
/reload-plugins

The repo is petekp/circuitry, the plugin is named circuit. Commands use the plugin name: /circuit:run, /circuit:build, etc.

Start a new Claude Code session and run:

/circuit:run evaluate microservices vs modular monolith vs serverless for our growing backend

That's it. Circuitry classifies your task, picks the right workflow, and runs it.

How It Works

Circuitry owns the developer session lifecycle. Every task maps to a workflow (what kind of job) and a rigor profile (how much scrutiny).

Five workflows, named after your job:

Workflow	What it does
Explore	Investigate, understand, choose among options, shape a plan
Build	Features, refactors, docs, tests, mixed changes
Repair	Bugs, regressions, flaky behavior, incidents
Migrate	Framework swaps, dependency replacements, architecture transitions
Sweep	Cleanup, quality passes, coverage improvements, docs-sync

Five rigor profiles:

Rigor	Budget
Lite	Plan and do. No independent review.
Standard	Plan, do, independent review. One fix loop.
Deep	Research phase, seam proof. Workflows that include review still run it.
Tournament	Competing proposals, adversarial evaluation, convergence.
Autonomous	Unattended. Evidence-gated. Checkpoints auto-resolve; workflows that include independent review still run it.

Every workflow follows the same phase spine: Frame, Analyze, Plan, Act, Verify, Review, Close, Pause. Not every workflow uses every phase, but the semantics stay stable.

1. The router classifies your task. Circuitry matches your task to a workflow and rigor profile. Quiet by default: it routes and proceeds unless something is genuinely ambiguous.

2. Steps run in the right order. Research before decisions. Decisions before implementation. Implementation gets an independent review from a separate session. Every step saves progress to disk.

3. Progress survives crashes. Active run state (active-run.md) is updated after every phase. Session handoff state lives in ~/.claude/projects/ so fresh sessions resume where the last one stopped.

4. You step in where it matters. Circuitry pauses at checkpoints for your judgment (scope confirmation, tradeoff decisions). Everything else runs autonomously.

What Circuitry Is Not

• Not a CI/CD tool. Circuitry runs inside Claude Code sessions, not in pipelines.
• Not for trivial edits. The router can say "this is trivial, do it inline." That restraint is part of the product.
• Not a replacement for skills. Circuitry orchestrates skills. If you need TDD discipline, install the tdd skill. Circuitry will use it at the right phase.

Commands

Router (auto-classifies your task):

You type	What happens
/circuit:run <task>	Router picks the best workflow and rigor
/circuit:run fix: <bug>	Repair Lite -- test-first bug fix
/circuit:run repair: <issue>	Repair Deep -- broad investigation
/circuit:run develop: <feature>	Build Standard -- plan, implement, review
/circuit:run decide: <choice>	Explore Tournament -- adversarial evaluation
/circuit:run migrate: <target>	Migrate Deep -- inventory, coexistence plan, batches
/circuit:run cleanup: <target>	Sweep Standard -- cleanup by confidence/risk
/circuit:run overnight: <scope>	Sweep Autonomous -- unattended quality pass

Direct circuits (skip the router):

You type	What happens
/circuit:explore	Investigation, decisions, planning
/circuit:build	Features, refactors, docs, tests
/circuit:repair	Bug fixes with regression contracts
/circuit:migrate	Migrations with coexistence planning
/circuit:sweep	Cleanup and quality sweeps
/circuit:review	Standalone fresh-context code review
/circuit:handoff	Save session state for the next session

See CIRCUITS.md for the full catalog with phase breakdowns and usage examples.

Key Features

Automatic workflow selection. Describe your task. Circuitry picks the right workflow and rigor level.