kspec-review

Name: kspec-review
Availability: InStock
Author: lepahc

Guide reviewers through findings, threads, checks, and verdicts in kspec reviews.

1|2|Updated Jan 16, 2026

Search Tags:#review #traceability #task-management #code-review #acceptance-criteria #kspec

Ready to run

npx skills add https://github.com/lepahc/kynetic-spec --skill kspec-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kspec-review
Source: https://github.com/lepahc/kynetic-spec/tree/main/.agents/skills/kspec-review
Command: npx skills add https://github.com/lepahc/kynetic-spec --skill kspec-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review workflows in kspec are often inconsistent and isolated, leading to missed acceptance criteria and fragmented feedback. This Skill provides a structured approach to recording findings, linking them to specific code paths, plans, or specs, and tracking reviews across cycles for auditability.

Core Features & Use Cases

Create, open, and manage per-cycle review records that thread findings, checks, and verdicts.
Anchor findings to exact code lines, files, or plan/spec sections for precise traceability.
Integrate with task lifecycles (needs_work, approved, etc.) and auto-close reviews on verdicts.
Support for deterministic checks, evidence recording, and threaded discussions to enable rigorous QA.

Quick Start

Create a new task review for a pending task and begin recording findings with anchored references to code paths and plan sections.

Frequently Asked Questions about kspec-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I anchor code review findings to specific code paths and plan sections?▼

You can manage per-cycle code reviews by creating, opening, and tracking review records that thread findings, checks, and verdicts, ensuring audits remain consistent across cycles.

Can I auto-close a task review when a verdict is reached?▼

Structured code and spec reviews solve inconsistent workflows by recording deterministic checks, evidence, and threaded discussions, preventing missed acceptance criteria and fragmented feedback.

What is the best way to maintain traceability for acceptance criteria across review cycles?▼

Traceability for acceptance criteria is maintained by creating per-cycle review records that thread findings, checks, and verdicts, anchoring feedback to exact code paths or plan sections for auditability.

How do I record deterministic checks and evidence for task reviews?▼

Task reviews support recording deterministic checks and evidence by guiding reviewers through threaded discussions and findings anchored to specific code paths, plans, or specs within the project.