issue-plan-observer

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.