issue-review-ready

Validate GitHub issue bodies for required frontmatter and acceptance criteria structure.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill issue-review-ready
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-review-ready
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/issue-review-ready
Command: npx skills add https://github.com/apokamo/kaji --skill issue-review-ready

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issue本文の着手レディネスレビュー。作業着手に足る記述品質があるかを検証する全 workflow 共通ゲート。

Core Features & Use Cases

  • Validates issue body structure (Overview, Objective, Acceptance Criteria)
  • Flags missing rationale and unclear scope; enforces traceable evidence
  • Applies as a universal gate in all workflows between issue creation and work start

Quick Start

Run the issue readiness check on a new issue to verify the body structure, rationale, and completion criteria.

Frequently Asked Questions about issue-review-ready

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

FAQPage Schema
How do I validate issue readiness before starting development work?▼

Issue readiness validation checks an issue's body and frontmatter to ensure it contains a describable problem, measurable goals, and supporting evidence before work begins.

What is issue readiness review in a software development workflow?▼

Issue readiness review is a universal gating mechanism that prevents scope drift by enforcing a well-structured issue body with clear acceptance criteria and traceable evidence.

How do I enforce acceptance criteria and structured documentation in issue tracking?▼

You can enforce structured documentation by running an automated readiness check that validates the presence of an overview, objective, acceptance criteria, and supporting rationale.

Can I use an automated gate to prevent scope drift across multiple workflows?▼

Yes, applying a universal readiness gate between issue creation and work start ensures all workflows require a describable problem, measurable goals, and traceable evidence to proceed.

Why does an issue fail a work-ready readiness check?▼

An issue fails the readiness check when it lacks a well-structured body, missing rationale, unclear scope, or insufficient traceable evidence to support the stated measurable goals.