mirror of
https://github.com/duthaho/claudekit.git
synced 2026-06-15 22:44:55 +03:00
duthaho
83 lines
3.4 KiB
Markdown
83 lines
3.4 KiB
Markdown
# Changelog
|
|
|
|
All notable changes to this project will be documented in this file.
|
|
|
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
|
|
## [Unreleased]
|
|
|
|
## [4.0.0] - 2026-05-07
|
|
|
|
### Verification-first engineering toolkit
|
|
|
|
Initial release of the verification-first claudekit. Built for senior ICs and
|
|
tech leads who already know how to ship and want a workflow that keeps the bar
|
|
high without ceremony.
|
|
|
|
### Skills (15)
|
|
|
|
A 5-phase spine — **Investigate → Design → Implement → Verify → Ship** — plus
|
|
2 setup skills off-spine. All user-invocable as `/claudekit:<name>`.
|
|
|
|
| Phase | Skills |
|
|
|-------|--------|
|
|
| Investigate | `investigate-root-cause`, `map-codebase`, `audit-dependencies` |
|
|
| Design | `shape-spec`, `write-plan`, `plan-review`, `plan-review-architecture`, `plan-review-experience` |
|
|
| Implement | `test-first`, `incremental-shipping` |
|
|
| Verify | `verification-gate`, `evidence-driven-debugging` |
|
|
| Ship | `code-review-loop`, `release-and-changelog` |
|
|
| Setup | `init` |
|
|
|
|
Every skill has 8 required sections: Frontmatter, Overview, When to Use,
|
|
Process, Rationalizations table, Evidence Requirements, Red Flags, References.
|
|
|
|
### Agents (8)
|
|
|
|
One specialist per job; each agent has a single dispatcher.
|
|
|
|
- `planner` — decompose specs into executable plans
|
|
- `architect` — architecture-dimension reviewer for plans
|
|
- `experience-reviewer` — UX + DX dimension reviewer for plans
|
|
- `investigator` — root-cause investigation with evidence chain
|
|
- `tester` — design and write tests with red-green discipline
|
|
- `code-reviewer` — pre-merge structural review of diffs
|
|
- `security-auditor` — OWASP-aligned review of sensitive paths
|
|
- `scout` — codebase mapping and dependency audits
|
|
|
|
### Rationalizations + Evidence Requirements
|
|
|
|
The headline pattern: every skill names the excuses an engineer makes to skip a
|
|
step (verbatim quotes, with steelmanned reasoning, named failure modes, and
|
|
concrete alternatives) and the artifact each checkpoint must produce. "It seems
|
|
right" is failure; the artifact is required.
|
|
|
|
### Pre-completion gate
|
|
|
|
`verification-gate` is the load-bearing skill. Before any "done" claim, it
|
|
forces: restate the claim, run named tests with full output, run the negative
|
|
path, verify in a non-IDE environment, cross-check the original ask, sign the
|
|
gate. Six steps, ~5 minutes.
|
|
|
|
### Plan-review pipeline
|
|
|
|
`plan-review` orchestrates two parallel reviewers — `plan-review-architecture`
|
|
and `plan-review-experience` — each scoring 5 sub-dimensions 0-10 with cited
|
|
findings. Findings consolidate into one ranked fix gate. Catches structural
|
|
issues before code.
|
|
|
|
### Setup wizard
|
|
|
|
`/claudekit:init` interactively scaffolds:
|
|
|
|
- **Rules** — API, frontend, migrations, security, testing → `.claude/rules/`
|
|
- **Output styles** — 5 native Claude Code output styles ship with the plugin in `output-styles/` (auto-discovered, no init step). Switch via `/config`.
|
|
- **Hooks** — auto-format, block-dangerous-commands, notifications → `.claude/hooks/` + `settings.local.json`
|
|
- **MCP Servers** — Context7, Sequential, Playwright, Memory, Filesystem → `.mcp.json`
|
|
|
|
### Voice
|
|
|
|
Engineering-only. No founder/VC/coaching language. No "ambitious vision," no
|
|
"10x outcomes," no "delight." Engineering analogies, real file paths, real
|
|
commands. Take a position; state what evidence would change it.
|