issue-plan-observer

Review GitHub issues and implementation plans against repository evidence.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/emilyLi2020/WAVE --skill issue-plan-observer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-plan-observer
Source: https://github.com/emilyLi2020/WAVE/tree/main/.agents/skills/issue-plan-observer
Command: npx skills add https://github.com/emilyLi2020/WAVE --skill issue-plan-observer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unvetted GitHub issues and implementation plans often contain hidden risks, mismatches with existing code, missing dependencies, or vague acceptance criteria that lead to wasted development time, failed implementations, and unexpected production issues. This skill provides an unbiased, evidence-based review to catch these gaps before work begins.

Core Features & Use Cases

  • Impartial Risk Identification: Surfaces hidden dependencies, lifecycle issues, platform constraints, and test gaps without bias toward the plan author.
  • Evidence-Based Validation: Compares proposed plans against actual repository code, documentation, recent commits, and branch status to catch mismatches between planned work and current codebase state.
  • Standardized Review Output: Posts consistent, structured GitHub issue comments with clear observations, plan strengths, and actionable suggestions to improve team alignment.
  • Use Case: A developer submits an implementation plan for a new feature; use this skill to catch that the plan references an outdated API endpoint removed in the last release, or that the proposed approach doesn't account for browser memory limits for on-device models.

Quick Start

Use the issue-plan-observer skill to review the implementation plan linked to GitHub issue #<issue-number> and post a structured impartial comment with observed risks and suggestions.

Frequently Asked Questions about issue-plan-observer

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

FAQPage Schema
How do I review a GitHub implementation plan for hidden risks before coding?

Reviewing a GitHub implementation plan for hidden risks requires impartially validating proposed work against existing repository evidence and acceptance criteria. This surfaces unstated dependencies, platform constraints, and codebase mismatches prior to implementation.

What is evidence-based issue review in software development?

Evidence-based issue review compares proposed implementation plans against actual repository code, documentation, and recent commits. This validation mechanism catches mismatches between planned work and the current codebase state to reduce wasted development time.

How do I catch missing dependencies in a GitHub issue plan?

Catch missing dependencies in a GitHub issue plan by impartially assessing the proposed work against repository evidence and platform constraints. This surfaces unstated dependencies and lifecycle issues before implementation begins.

Can I post structured review comments directly to GitHub issues?

Yes, you can post structured review comments directly to GitHub issues. Standardized output includes clear observations, plan strengths, and actionable suggestions to improve team alignment and reduce implementation risk.

Does unbiased plan validation work with existing codebases?

Unbiased plan validation works by comparing proposed plans against existing codebases, recent commits, and branch status. This evidence-based approach detects outdated API references and platform constraint violations without bias toward the plan author.

What are the limitations of automated issue review for implementation plans?

Automated issue review for implementation plans is limited to analyzing repository evidence, code, and documentation provided. It cannot predict undocumented business logic constraints or external system behaviors not reflected in the current codebase.