adv-opportunity-scout

Identify missed opportunities and design leverage points in AI-assisted engineering workflows.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Sharper-Flow/Advance --skill adv-opportunity-scout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adv-opportunity-scout
Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-opportunity-scout
Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-opportunity-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of scope drift and shallow design in AI-assisted engineering by systematically identifying missed opportunities and leverage points during discovery and design phases.

Core Features & Use Cases

  • Bounded Opportunity Scouting: Automatically scans for alternative approaches, overlooked patterns, and edge cases within strict constraints.
  • Leverage Point Identification: Highlights shortcuts, reusable components, and simplification paths to optimize design efficiency.
  • Contract-Tied Routing: Ensures all findings are grounded in project objectives and acceptance criteria, with automated routing for low-risk, high-payoff improvements.

Quick Start

Invoke the adv-opportunity-scout skill to analyze the current design draft for potential leverage points and simplification opportunities.

Frequently Asked Questions about adv-opportunity-scout

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

FAQPage Schema
How do I identify leverage points in AI-assisted engineering workflows?

To identify leverage points in AI-assisted engineering, you analyze current design drafts against project objectives to automatically surface alternative approaches, overlooked patterns, and simplification paths.

What is bounded opportunity scouting in spec-driven development?

Bounded opportunity scouting systematically scans for alternative approaches, overlooked patterns, and edge cases within strict constraints to prevent scope drift and shallow design during discovery.

How do I prevent scope drift when using AI for software design?

Prevent scope drift in AI-driven software design by grounding all findings in project objectives and acceptance criteria, using contract-tied routing to ensure only low-risk, high-payoff improvements proceed.

How do I find reusable components and shortcuts during the design discovery phase?

Find reusable components and shortcuts during design discovery by applying leverage point identification to structured inputs like project proposals and current-state findings to optimize design efficiency.

What inputs do I need to analyze a design draft for missed opportunities?

Analyzing a design draft for missed opportunities requires structured input of project proposals, acceptance criteria, and current-state findings to successfully generate fate-routed candidate recommendations.

When should I use contract-tied routing for design recommendations?

Use contract-tied routing for design recommendations when you need to ensure all identified improvements are grounded in project objectives and acceptance criteria, automatically routing low-risk, high-payoff changes.