issue-design-review

Reviews draft GitHub issues for scope authority, hidden dependencies, and acceptance criteria before creation.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/rapucha/moon-service --skill issue-design-review-rapucha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-design-review
Source: https://github.com/rapucha/moon-service/tree/main/.agents/skills/issue-design-review
Command: npx skills add https://github.com/rapucha/moon-service --skill issue-design-review-rapucha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent-drafted GitHub issues can silently expand scope, embed unauthorized decisions, or hide dependency cycles before they become implementation authority. This Skill runs an independent read-only design review that challenges the premise, alternatives, and acceptance criteria of a draft issue before it is created or acted upon. ## Core Features & Use Cases - Scope Authority Audit: Reconstructs agent-added scope independently of the drafter's claims and flags unsupported acceptance criteria, optional hardening, and speculative extension points. - Dependency and Rollout Simulation: Traces delivery transitions, actors, permissions, and artifacts to detect dependency cycles and reliance on unavailable ambient work. - Structured Verdict Output: Returns exactly one verdict (ready, revise, or split_required) with a fixed output contract covering evidence, ownership, production-use justification, and repository scope gates. - Use Case: Before an agent creates a nontrivial technical-debt or privacy issue, delegate the draft to a fresh read-only subagent that validates the premise against project policy and returns a verdict with required corrections. ## Quick Start Ask the agent to use the issue-design-review skill to review this draft issue before it becomes implementation authority.

Frequently Asked Questions about issue-design-review

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

FAQPage Schema
How do I review an agent-drafted GitHub issue before creating it?

Delegate the complete draft, the raw motivating user request, and project authority files to a fresh read-only subagent that did not write the draft. The reviewer returns a ready, revise, or split_required verdict with evidence traces for every material acceptance criterion.

What is agent-added scope in an issue draft?

Agent-added scope is any material behavior the drafting agent introduced, strengthened, or made more specific beyond the raw motivating material. Each item must be traced to user intent, evidence, a correctness or safety need, or an explicit owner decision, or it is removed.

When should an issue draft be split instead of revised?

Split when the draft combines independently reviewable outcomes, crosses a hard repository scope gate, or mixes a prerequisite decision with implementation that should not start before that decision. A documentation review threshold alone does not require a split.

Does the issue review modify files or create issues?

No. The review is strictly read-only and must not create or edit issues, files, branches, or pull requests. The primary agent acts on the verdict only when separately authorized, and reviewer output never substitutes for owner approval.

Why does a draft issue get a revise verdict?

Revise is returned when the premise, scope authority, dependencies, or acceptance criteria need correction, such as an unapproved stricter design, a dependency cycle, missing production-use evidence, or an incomplete agent-added scope section.