skills.rest
ryowatanabe
ryowatanabeCOMMUNITY
Explore all skills by this author →
GitHub

kiro-review

Verify task implementations against approved specs and boundaries for APPROVED or REJECTED outcomes.

Updated Feb 25, 2024
Search Tags:#requirements#verification#risk-assessment#code-review#design-review#mechanical-verification#boundary-checks
One-click install
npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-review-ryowatanabe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-review
Source: https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper/tree/main/.claude/skills/kiro-review
Command: npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-review-ryowatanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables an adversarial, boundary-aware review of a task implementation to ensure it aligns with approved specs, boundaries, and verification evidence.

Core Features & Use Cases

  • Boundary- and spec-aligned verification of implementations against requirements and design artifacts.
  • Post-implementation reviews triggered after READY_FOR_REVIEW, remediation, or prior acceptance.
  • Returns a formal APPROVED or REJECTED decision along with mechanical results and remediation guidance.

Quick Start

Submit the task artifacts and run the review to produce an APPROVED or REJECTED verdict.

Frequently Asked Questions about kiro-review

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

FAQPage Schema
How do I verify code implementation against approved specs and boundaries?▼

Spec-aligned verification checks task implementations against approved requirements and design artifacts to detect boundary violations, returning an APPROVED or REJECTED decision with remediation guidance.

What is a formal post-implementation review for task acceptance?▼

A formal post-implementation review is an adversarial, boundary-aware assessment triggered after READY_FOR_REVIEW or remediation cycles to ensure delivery strictly adheres to approved specs and verification evidence.

How do I run a design review using machine-checked diffs and status reports?▼

Submit task artifacts, design documents, and machine-checked diffs to run an automated review that determines an APPROVED or REJECTED outcome based on mechanical verification evidence.

Does boundary-aware code review work without reference documents?▼

No, boundary-aware review requires task artifacts, design documents, machine-checked diffs, and status reports as reference inputs to identify boundary violations and produce a formal verdict.

When should I use formal task reviews for risk assessment?▼

Use formal task reviews during post-implementation phases, remediation cycles, or prior to acceptance to mechanically verify that implementations strictly adhere to approved specs and boundaries.

What does a REJECTED outcome include for remediation cycles?▼

A REJECTED outcome includes mechanical verification results and remediation guidance detailing boundary violations and spec misalignments found during the adversarial review process.

Related Skills

Explore More Software Engineering Skills→
taku-otaku-o
1

kiro-review

Verifies task implementations against approved specs and design boundaries with mechanical checks.

Community
Advanced
miyamo2miyamo2

kiro-review

Assess implementations against approved requirements and design boundaries.

Community
Advanced
jamesjlundinjamesjlundin
32

pr-review

Analyze pull requests and generate structured review reports.

Community
Intermediate
AesopScottAesopScott

reviewer-pack

Standardize review pipelines with configurable severity rubrics and repair-verification gates.

Community
Advanced