kk

Plugin kk from marketplace claude-toolbox in serpro69/claude-toolbox. Commands read from the repo's manifest — today.

Skills (19)

• brainstorm

  TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering wo

• chain-of-verification

  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.

• clarify-docs

  TRIGGER when: asked to clarify or improve existing documentation, PR drafts or issue descriptions, including URLs and pasted bodies. Saves results locally, grounded in requirements and source while preserving meaning. Not for requests to implement, fix or work on an issue, code, config, generic resp

• greet

  Greet the user.

• dependency-handling

  TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.

• design

  TRIGGER when: asked to write or refine a technical design, PRD, specification, implementation plan, or task list, or resume an existing docs/feat/wip feature. Turns ideas and requirements into written design documents, implementation plans, and tasks in docs/feat/wip/ before coding. For conversation

• diff-skill

  Compare two versions of a skill's instructions to detect degradations and complexity increases. TRIGGER when: user asks to diff, compare, or review changes to a skill's markdown instructions. Asymmetric check — only regressions count. Additions, clarifications, and strengthenings are not degradation

• review-tool

  Reviews tool configurations for correctness.

• review-tool

  Reviews tool configurations for correctness.

• document

  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.

• handoff

  Explicitly invoke /kk:handoff to publish active-task context and a fresh-session starter prompt to a new secret GitHub gist. For restarting a conversation or switching providers or machines; requires the GitHub CLI. Not a local save.

• implement

  TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detect

• greet

  Greet the user by name in their preferred language. Use when the user asks for a greeting or a one-line introduction message.

• merge-docs

  Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.

• model

  Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholde

• review-architecture

  Review a written architecture artifact — an ADR (docs/adr/), a broader architecture doc, the architecture section of a design doc, or a domain-reference kit (glossary + traps pages, reviewed as one composite artifact) — against the system it claims to describe. Verifies the EXISTENCE and TOPOLOGY of

• review-code

  Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.

• review-design

  Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.

• review-spec

  Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.

Slash commands (6)

• /kk:chain-of-verification:default
• /kk:chain-of-verification:isolated
• /kk:migrate-from-taskmaster:migrate
• /kk:review-code:isolated
• /kk:review-spec:default
• /kk:review-spec:isolated

Subagents (6)

• architecture-reviewer

  Independent architecture reviewer with no authorship attachment. Verifies a written architecture artifact (ADR, architecture doc, design-doc architecture section, or domain-reference kit — glossary + traps pages reviewed as one composite artifact) against the system it claims to describe — checking

• code-reviewer

  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. - Read - Grep - Glob - mcp__capy__capy_search

• design-reviewer

  Independent design document reviewer with no authorship attachment. Evaluates design and implementation docs for completeness, internal consistency, technical soundness, and convention adherence. - Read - Grep - Glob - mcp__capy__capy_search

• eval-grader

  Independent skill-eval grader with no review authorship or live fixture access. Grades reviewer output by default, or sealed execution evidence in explicit workflow mode. Returns PASS / FAIL / PARTIAL per assertion with one-line evidence. - Read

• profile-resolver

  Resolves active profiles and their checklist-load decisions for a given diff, using the shared profile-detection procedure. Emits a structured resolution report: active profiles with per-file `triggered_by` signal, plus loaded vs. not-loaded checklists with Load-if reasoning. Useful wherever profile

• spec-reviewer

  Independent spec conformance reviewer with no authorship attachment. Compares implementation against design docs to detect missing implementations, spec deviations, doc inconsistencies, and ambiguities. - Read - Grep - Glob - mcp__capy__capy_search

Hooks (2)

• SessionStart

  bash ${CLAUDE_PLUGIN_ROOT}/scripts/set-plugin-root.sh ${CLAUDE_PLUGIN_ROOT}

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/guard/guard.sh

Similar plugins