By serpro69
Structure pre-implementation planning into PRDs, design specs, and task files; verify code against design docs; enforce code quality via SOLID-aware git diff reviews; and bootstrap commit policies — turning development workflow into a guided, reviewable process.
Apply Chain-of-Verification (CoVe) with true factored verification using isolated sub-agents.
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification.
Verify implemented code against design and implementation documentation, detecting spec deviations, missing implementations, and outdated docs.
Run implementation review in isolated mode with an independent spec-reviewer sub-agent that has zero authorship bias.
Migrate this project from Task Master MCP to native markdown-based task tracking.
Independent code reviewer with no authorship attachment. Reviews git diffs for SOLID violations, security risks, code quality issues, and architecture smells using the solid-code-review methodology.
Independent design document reviewer with no authorship attachment. Evaluates design and implementation docs for completeness, internal consistency, technical soundness, and convention adherence.
Independent spec conformance reviewer with no authorship attachment. Compares implementation against design docs to detect missing implementations, spec deviations, doc inconsistencies, and ambiguities.
Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
Review design and implementation docs produced by analysis-process. Evaluates document quality, internal consistency, and technical soundness. Use after analysis-process completes and before starting implementation-process.
Use when writing code to ensure you follow development best practices during development and implementation.
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
claude-toolbox is a collection of "tools" for all your Claude Code workflows — pre-configured MCP servers, skills, sub-agents, commands, hooks, statuslines with themes, and more - everything you need for AI-powered development workflows, used and battle-tested daily on many of my own projects.
This is a template repository and plugin system that gives you a ready-to-use Claude Code development environment. It ships with MCP servers, a kk plugin (skills, commands, hooks), themed statuslines — all configured and wired together.
The repo serves dual purposes:
kk plugin via the Claude Code plugin system to get skills, commands, and hooks[!NOTE] We focus on collaborative development. Claude Code settings are split between two project-scoped files:
.claude/settings.json— upstream-managed defaults, synced to all downstream repos (permissions baseline, env vars, model, plugins, statusline).claude/settings.local.json— per-repo overrides, never synced (hooks, MCP server enables, additional permissions, personal preferences)"Don't ask again" permission grants land in
settings.local.jsonautomatically.
Three servers, configured at user-level (~/.claude.json) to keep API keys out of the repo:
| Server | Purpose |
|---|---|
| Context7 | Up-to-date library documentation and code examples |
| Serena | Semantic code analysis via LSP — symbol navigation, reference tracking, targeted reads |
| Pal | Multi-model AI integration — chat, debugging, code review, planning, security audit |
| Capy | Persistent knowledge base — cross-session project memory with FTS5 search |
The kk plugin's skills are knowledge-aware via Capy. Skills search for relevant context before executing (architecture decisions, review findings, language idioms) and index valuable learnings after producing output. Knowledge persists across sessions per-project using an FTS5 full-text search index.
Installation: brew install serpro69/tap/capy then run capy setup in your project directory.
[!NOTE] Capy is optional. All skills work fully without it — search steps return nothing and index steps are skipped. The bootstrap script sets up capy automatically if the binary is on PATH.
klaude-plugin/)The kk plugin contains all development workflow functionality — 10 skills, 4 commands, and hooks — distributed via the Claude Code plugin system. Skills are invoked as /skill-name, commands as /kk:dir:command.
Includes: analysis-process, implementation-process, testing-process, documentation-process, development-guidelines, solid-code-review, implementation-review, design-review, merge-docs, cove (Chain-of-Verification). Plus commands for CoVe, implementation review, design review, Task Master migration, and sync workflow updates. See the plugin README for full details.
.claude/settings.json) — baseline permissions: auto-approves safe bash commands and WebSearch while blocking dangerous patterns. Per-repo MCP tool permissions go in settings.local.json..claude/scripts/statusline_enhanced.sh) — rich statusline with model, context %, git branch, session duration, thinking mode, and rate limits. Themes: set CLAUDE_STATUSLINE_THEME to darcula, nord, or catppuccin, and CLAUDE_STATUSLINE_MODE to dark (default) or light to match your terminal background.serena/project.yml) — language detection, gitignore integration, encoding settingsnpx claudepluginhub serpro69/claude-toolbox --plugin kkMulti-agent /workflow development pipeline (planner → plan-review → coder → code-review) with typed handoff contracts, lifecycle hooks, and MCP servers.
Claude Code workflow patterns: prompting, CLAUDE.md maintenance, multi-agent orchestration
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Corca Workflow Framework — consolidated hooks and skill orchestration for structured development sessions
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.