Claude Kit

A verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine — Investigate, Design, Implement, Verify, Ship — plus 8 specialist agents and 5 output styles. Built for senior ICs and tech leads.

Get Started View on GitHub

What makes claudekit different

Every skill has a Rationalizations table — the excuses an engineer makes to skip a step (“I see the problem, let me just patch it”) with rebuttals. Every checkpoint has Evidence Requirements — a specific artifact you could paste into a code review. Pre-completion gates refuse “tests pass — trust me” claims. No founder voice; engineering-only rigor.

Four layers, one plugin

15 Skills A 5-phase spine. All user-invocable. Each skill has rationalizations + evidence + red flags.

8 Agents One specialist per job. Planner, architect, experience-reviewer, investigator, tester, code-reviewer, security-auditor, scout.

5 Output Styles Native Claude Code output styles — Brainstorm, Deep Research, Implementation, Review, Token Efficient. Switch via /config.

MCP Servers Optional integrations: real-time library docs, persistent memory, browser automation, structured reasoning.

Install in 2 minutes

# Add the marketplace
/plugin marketplace add duthaho/claudekit-marketplace

# Install the plugin
/plugin install claudekit

# Configure your project (optional)
/claudekit:init

Skills trigger automatically based on what you’re doing. Ask Claude to shape a spec, write a plan, investigate a bug, or review code — the right skills activate without any commands.

Why Claude Kit

Raw Claude Code is powerful but brittle. Self-reported “done” claims don’t hold up. Bugs get patched at the line where the error appeared, not at the cause. Plans say “implement the X” and hide three sub-decisions nobody made.

Problem	What Claude Kit v4 adds
Self-reported “done” claims	`verification-gate` — pre-completion check that requires pasted evidence
Symptom-fixed bugs	`investigate-root-cause` — 4-phase, no fix without a written hypothesis
Vague plans	`write-plan` — file paths, exact test commands, falsifiable acceptance per task
Skip-it discipline	Rationalizations tables in every skill — the excuses get named with rebuttals

The 5-phase workflow

Phase	What happens	Skills
Investigate	Surface every fact about the system, with file:line citations	`investigate-root-cause`, `map-codebase`, `audit-dependencies`
Design	Spec → plan → reviewed before implementation	`shape-spec`, `write-plan`, `plan-review`, `plan-review-architecture`, `plan-review-experience`
Implement	Red-green-refactor; vertical slices behind feature flags	`test-first`, `incremental-shipping`
Verify	Mandatory pre-completion gate; active-debug paper trail	`verification-gate`, `evidence-driven-debugging`
Ship	Reviewable PRs with verification evidence; atomic releases	`code-review-loop`, `release-and-changelog`
Setup (off-spine)	One-time scaffolding wizard for project config	`init`

Explore the workflows →

Ready to ship faster?

Installation Step-by-step setup for your first project.

Create your own skills Add project-specific skills, agents, and modes.