implementation-scope-review

Reviews planned changes before implementation and returns a single-PR, split-required, or revise verdict.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or incoherent changes often reach implementation before anyone checks whether they should be one pull request or several. This Skill runs an independent, read-only pre-implementation scope review so oversized plans are split or revised before code accumulates. ## Core Features & Use Cases - Scope Verdicts: Returns exactly one verdict — single_pr, split_required, or revise — based on repository hard gates, concern counts, and file-size limits. - Behavioral Decomposition: Maps every acceptance criterion to a proposed PR and checks that each slice stays useful and mergeable if later slices never land. - Dependency Liveness Checks: Simulates pre-merge, merge, validation, and activation transitions to detect dependency cycles or reliance on ambient work. - Use Case: Before implementing a feature spanning backend, frontend, and CI changes, delegate the plan to a fresh read-only subagent running this review to get an ordered, independently reviewable PR sequence. ## Quick Start Ask a fresh read-only subagent to use the implementation-scope-review skill on this issue and its acceptance criteria to return a scope verdict and proposed PR sequence before any files are edited.

Frequently Asked Questions about implementation-scope-review

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

FAQPage Schema
How do I check if a planned change is too big for one pull request?

Delegate the issue and plan to a fresh read-only subagent running this scope review. It applies the repository's hard gates on concerns, ordinary files, and code sizes, then returns single_pr, split_required, or revise with a proposed ordered PR sequence.

When should I run a pre-implementation scope review?

Run it when a change may span multiple independently reviewable concerns, subsystems, providers, deployment layers, UI and backend work, or CI, or when project instructions define PR-size gates. It runs before any files are edited.

Can the same agent that wrote the plan run this scope review?

No. The skill requires the primary agent to delegate to a fresh read-only subagent that did not draft the plan. Self-review does not satisfy the preconditions, and the reviewer must not edit files or mutate external state.

What is the difference between scope review and code review?

Scope review evaluates the plan before implementation and decides how work should be packaged into PRs. Code review of the staged diff happens after implementation, using a separate second-agent review when available.

What happens when a plan crosses a hard repository gate?

The default verdict is split_required with the smallest practical ordered PR series. A single-PR exception requires the exact exceeded gate, measured values, rationale, and explicit owner approval recorded through the project's normal workflow.