From kk
Reviews design and implementation docs from analysis-process for document quality, internal consistency, and technical soundness before implementation-process.
npx claudepluginhub serpro69/claude-toolbox --plugin kkThis skill uses the workspace's default tool permissions.
For capy knowledge base conventions, see [capy-knowledge-protocol.md](../_shared/capy-knowledge-protocol.md).
Verifies implemented code against design.md, implementation.md, and tasks.md docs. Detects missing implementations, spec deviations, extra code, doc inconsistencies, outdated docs. Use after tasks or mid-feature.
Reviews design docs with 8-point checklist for problem clarity, success criteria, architecture fit, alternatives, scope, and handoff quality before draft-plan. Auto-dispatched post-design.
Reviews requirements and plan documents using parallel persona agents to surface role-specific issues, auto-fix quality problems, and pose strategic questions.
Share bugs, ideas, or general feedback.
For capy knowledge base conventions, see capy-knowledge-protocol.md.
Pre-implementation review gate that evaluates design documents produced by analysis-process before code is written. Sits between analysis-process (creates docs) and implementation-process (executes them). Reviews two dimensions: document quality/structure (completeness, internal consistency, clarity, convention adherence) and technical soundness (architectural viability, edge cases, failure modes, trade-off analysis).
/kk:design-review)Reviews design documents in the main conversation context. Fast, single-pass review using the workflow below.
/kk:design-review:isolated)Delegates detection to independent reviewers that did not participate in the analysis-process, then annotates their findings with author context. Two parallel reviewers: a design-reviewer sub-agent and pal codereview (external model in native format). Produces a report organized by agreement level with corroborated findings highlighted.
See review-isolated.md for the isolated workflow.
| Type | Code | Description |
|---|---|---|
| Incomplete Spec | INCOMPLETE | Section lacks sufficient detail for implementation |
| Internal Inconsistency | INCONSISTENT | Two parts of the docs contradict each other |
| Technical Risk | TECH_RISK | Architecture choice has unaddressed failure modes, scalability concerns, or edge cases |
| Missing Concern | MISSING | Cross-cutting concern is absent (error handling, migration, backwards compatibility) |
| Ambiguity | AMBIGUOUS | Requirements can be interpreted multiple ways, likely to cause implementation divergence |
| Structure Issue | STRUCTURE | Document doesn't follow project conventions — missing sections, vague subtasks |
| Level | Name | Description | Action |
|---|---|---|---|
| P0 | Critical | Fundamental flaw — design will not work as described, or critical requirement is missing | Must fix before implementation |
| P1 | High | Significant gap — likely to cause rework or wrong implementation | Should fix before implementation |
| P2 | Medium | Moderate concern — ambiguity or missing detail that could cause confusion | Fix or create follow-up |
| P3 | Low | Minor — style, structure, or nitpick | Optional |
Phases:
kk:arch-decisions and kk:review-findings for prior contextSee review-process.md for the detailed step-by-step process.
Standard mode — reviews design.md + implementation.md by default:
/kk:design-review [feature-name]
Standard mode with scope — review specific documents:
/kk:design-review [feature-name] design
/kk:design-review [feature-name] implementation
/kk:design-review [feature-name] tasks
/kk:design-review [feature-name] all
| Scope | Documents reviewed |
|---|---|
| (none) | design.md + implementation.md (default) |
design | design.md only |
implementation | implementation.md only |
tasks | tasks.md only |
all | design.md + implementation.md + tasks.md |
Isolated mode with independent sub-agents:
/kk:design-review:isolated [feature-name]
/kk:design-review:isolated [feature-name] tasks