reach-opportunities

Identify low-effort, high-impact improvements from plan implementation diffs.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/brmatola/gremlins --skill reach-opportunities
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reach-opportunities
Source: https://github.com/brmatola/gremlins/tree/main/skills/reach-opportunities
Command: npx skills add https://github.com/brmatola/gremlins --skill reach-opportunities

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The reach-opportunities skill helps teams surface small, high-value improvements to recently implemented work, preventing scope creep and reinforcing momentum.

Core Features & Use Cases

  • Audit context: loads plan goals and current implementation diff to surface relevant opportunities.
  • Opportunity classification: sorts opportunities by complexity (trivial/small/medium) and ties them to plan goals.
  • Decision guidance: recommends what to tackle now vs defer and when to spin off bigger ideas.
  • Documentation hooks: can generate output ready for PR notes or CLAUDE.md updates.

Quick Start

Run reach-opportunities after finishing implementation review on plan "my-plan" to identify quick wins; examine the list and pick trivial opportunities to implement in the next iteration

Frequently Asked Questions about reach-opportunities

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

FAQPage Schema
How do I identify quick wins after a plan implementation review?

To identify quick wins after plan implementation, evaluate the plan diff and score opportunities by complexity. This surfaces low-effort, high-impact improvements like polish and gaps tied to plan goals.

What is the best way to prevent scope creep during post-implementation review?

Post-implementation review prevents scope creep by sorting improvements into complexity scores (trivial, small, medium) and recommending what to tackle now versus what to defer or spin off into bigger ideas.

How do I score improvement opportunities by complexity for decision making?

Score improvement opportunities by complexity by evaluating the plan diff and classifying adjacent improvements as trivial, small, or medium, producing a structured output that guides decision making.

Can I generate PR notes and documentation updates after plan review?

Yes, you can generate PR notes and documentation updates after plan review. The process provides documentation hooks that output structured results ready for CLAUDE.md updates or pull request notes.

Does plan review opportunity identification work for active plans only?

Opportunity identification applies to active plans undergoing review. It loads plan goals and current implementation diffs to surface relevant adjacent improvements and gaps for decision making.