review-design-4e3574 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited review-design-4e3574 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Pre-implementation review gate that evaluates design documents produced by /kk:design before code is written. Sits between /kk:design (creates docs) and /kk:implement (executes them). Reviews three distinct dimensions
/kk:review-design)Reviews design documents in the main conversation context. Fast, single-pass review using the workflow below.
/kk:review-design:isolated)Delegates detection to independent reviewers that did not participate in the design, then annotates their findings with author context. One internal design-reviewer sub-agent plus external review chosen once at discovery: pal codereview (document-review branch) when an API model is available, otherwise one pal clink CLI review per eligible non-authoring provider using its configured model (variable count; on the clink roster the provider that authored the documents is excluded; PAL's shipped clients get default provider mappings that the report labels as assumed, and an operator declaration, for example in the project's CLAUDE.md or AGENTS.md, overrides them and is required for any other client name). Every reviewer applies the same shared design-review criteria and verification policy, framed as document review so planned implementation is not reported as missing code. Produces a report organized by agreement level with corroborated findings highlighted.
listmodels exposes CLI client observations in every mode for the clink path; unresolved discovery keeps the internal review with an explicit external coverage limit. Operator setup (the minimum PAL build, CLI read access outside the project, provider declarations) is described in the plugin README under "Isolated reviews with external models"design / implementation / tasks subsets as standard mode; missing requested documents are disclosed, not substitutedSee review-isolated.md for the isolated workflow; it replaces the standard-mode process file in that mode and is the only place that loads the isolated-only shared files (the design-review criteria, the PAL codereview protocol and the external-review protocol). Standard mode does not read them.
| 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 |
Mandatory order — methodology before evaluation. The flow below is strictly sequential. Load this SKILL.md, the selected process file and shared protocols before reading or evaluating subject documents. Only bounded inspection for a declared routing predicate may precede remaining instruction loads. The review methodology and rubric precede the design documents they assess.
Phases:
kk:arch-decisions and kk:review-findings for prior contextSee review-process.md for the detailed step-by-step process.
Post-design gate. This is the recommended review step after /kk:design completes and before /kk:implement begins. The default scope reviews all documents, including task-format checks.
Standard mode — reviews all documents by default:
/kk:review-design [feature-name]Standard mode with scope — review specific documents:
/kk:review-design [feature-name] design
/kk:review-design [feature-name] implementation
/kk:review-design [feature-name] tasks| Scope | Documents reviewed |
|---|---|
| _(none)_ | design.md + implementation.md + tasks.md |
design | design.md only |
implementation | implementation.md only |
tasks | tasks.md only |
Isolated mode with independent sub-agents:
/kk:review-design:isolated [feature-name]
/kk:review-design:isolated [feature-name] tasks~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.