npx claudepluginhub joshft/correctlessCorrectness workflow for structured development. 26 skills with configurable intensity levels: spec-before-code, skeptical review, enforced TDD, formal modeling, adversarial review, verification, documentation, and metrics. Intensity gates let you choose standard, high, or critical rigor per project.
Production-ready workflow orchestration with 79 focused plugins, 184 specialized agents, and 150 skills - optimized for granular installation and minimal token usage
Curated collection of 141 specialized Claude Code subagents organized into 10 focused categories
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations
Composable Claude Code skills that enforce a correctness-oriented development workflow. Spec before you code. Test before you implement. Never let an agent grade its own work.
AI coding assistants are fast but sloppy. They write code that works for the happy path, skip edge cases, and silently introduce bugs that don't surface until production. The same model that wrote the code will review it and say "looks good" — because it's confirming its own decisions.
Correctless fixes this by structuring the workflow so that every phase is executed by a different agent with a different lens:
Same model — but the framing determines what the agent finds.
You need Claude Code and a Claude Max subscription ($100-200/mo).
/plugin marketplace add joshft/correctless
/plugin install correctless
/csetup
git clone https://github.com/joshft/correctless.git .claude/skills/workflow
.claude/skills/workflow/setup
/csetup
Standard intensity by default. To increase: add "intensity": "high" or "critical" to the workflow section of .correctless/config/workflow-config.json.
git checkout -b feature/my-feature
/cspec
/plugin uninstall correctless
/plugin marketplace remove correctless
/plugin marketplace add joshft/correctless
/plugin install correctless
Then restart Claude Code. Git clone users: cd .claude/skills/workflow && git pull && ./setup
Correctless ships as a single plugin with 26 skills. You choose the intensity that matches your project's risk profile. Seven skills are gated behind intensity thresholds — they check your project's workflow.intensity setting and warn if invoked below their minimum.
| Intensity | Overhead | What You Get | Best For |
|---|---|---|---|
| standard | ~10-15 min | 19 core skills: spec, review, TDD, verify, docs, debug, refactor, release | SaaS, APIs, CLI tools, content sites |
| high | ~30-60 min | + adversarial spec review, convergence auditing, architecture tracking | Auth, payments, sensitive data |
| critical | ~1-2 hours | + Alloy formal modeling, live red team assessment | Security infrastructure, crypto, proxies |
Skills like /cpostmortem and /cdevadv are available at all intensity levels — they're about learning from the past, not adding rigor to the present.
Put another way: Standard intensity is like having someone next to you going through a checklist to make sure your project has some sanity. Critical intensity is like taking your Claude Max subscription tokens, setting them on fire, collecting the ash, and using it to create a tiny diamond.
graph LR
A["/cspec<br/>Write spec"] --> B["/creview<br/>Skeptical review"]
B --> C["/ctdd"]
C --> D["/cverify<br/>Rule coverage"]
D --> E["/cdocs<br/>Update docs"]
E --> F["Merge"]
subgraph "/ctdd — Enforced TDD"
direction LR
C1["RED<br/>Write tests"] --> C2["Test Audit<br/>Would tests catch bugs?"]
C2 --> C3["GREEN<br/>Implement"]
C3 --> C4["/simplify"]
C4 --> C5["QA<br/>Hostile review"]
C5 -.->|"Issues found"| C3
end
C --- C1