issue-review

Review tracker issues using the Rule of 5 methodology.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/charly-vibes/wai --skill issue-review-charly-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-review
Source: https://github.com/charly-vibes/wai/tree/main/.agents/skills/issue-review
Command: npx skills add https://github.com/charly-vibes/wai --skill issue-review-charly-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the rigorous review of issues in trackers like GitHub or Beads, ensuring they are clear, actionable, and well-defined before development begins.

Core Features & Use Cases

  • Iterative Refinement: Applies the "Rule of 5" methodology for deep, multi-pass issue analysis.
  • Comprehensive Checks: Validates completeness, scope, dependencies, plan alignment, and executability.
  • Use Case: Before starting a sprint, run this Skill on all new feature issues to catch ambiguities, scope creep, or missing dependencies, preventing costly rework later.

Quick Start

Run the issue-review skill to perform a Rule of 5 analysis on all GitHub issues labeled 'needs-review'.

Frequently Asked Questions about issue-review

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

FAQPage Schema
How do I automate issue review for GitHub issues before a sprint?

Automating issue review involves iteratively checking GitHub issues for completeness, scope, and dependencies. This skill applies the Rule of 5 methodology to analyze issues labeled 'needs-review', providing actionable feedback and commands for refinement before development begins.

What is the Rule of 5 methodology in agile workflow automation?

The Rule of 5 methodology is an iterative issue tracking review process that validates five core areas: completeness, scope, dependencies, plan alignment, and executability. It ensures issues in systems like GitHub or Beads are clear, actionable, and well-defined.

How do I check issue dependencies and scope alignment in Beads?

Checking issue dependencies and scope alignment in Beads requires precise issue referencing and clear success criteria. The Rule of 5 review process analyzes these factors to catch ambiguities, scope creep, or missing dependencies early.

Can I use this issue tracking review for agile project management?

Yes, you can use this issue tracking review for agile project management by running it on all new feature issues before starting a sprint. It validates plan alignment and executability to prevent costly rework later in the development cycle.

What are the limitations of automating quality assurance for issue tracking?

Automating quality assurance for issue tracking requires precise issue referencing and clear definitions of success criteria to function effectively. Without well-defined inputs in systems like GitHub, the automated validation cannot provide accurate actionable feedback.