skills.rest
julianjab
julianjabCOMMUNITY
Explore all skills by this author →
GitHub

scope-check

Analyze user requests to identify affected consumer repositories and output a structured scope verdict.

Updated Apr 1, 2026
Search Tags:#routing#multi-repo#scope#orchestrator#verdict#session-manager
One-click install
npx skills add https://github.com/julianjab/ia-tools --skill scope-check-julianjab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/julianjab/ia-tools/tree/main/skills/scope-check
Command: npx skills add https://github.com/julianjab/ia-tools --skill scope-check-julianjab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyse the scope of a user request to determine which consumer repos are touched, then return a structured verdict. It is used by session-manager to decide routing before opening a full sub-session.

Core Features & Use Cases

  • Evaluate a user message to map touched repositories and generate a verdict JSON block for downstream routing.
  • Create a per-task sessions directory and seed scope.md, plan-draft.md, and verdict.json for orchestration.
  • Handle ambiguity in multi-repo requests by delegating to the orchestrator as a one-shot inline subagent in scope-check mode.

Quick Start

Run scope-check on the message to determine touched repos and produce a verdict.

Frequently Asked Questions about scope-check

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

FAQPage Schema
How do I identify scope across multiple repositories for a user request?▼

Multi-repo scope identification analyzes a user message to determine which consumer repositories are touched, then outputs a structured verdict. It evaluates the request to map affected repos and generates a verdict JSON block for downstream routing decisions.

What is a scope verdict in multi-repo orchestration?▼

A scope verdict is a structured JSON block detailing which consumer repositories are affected by a specific request. It is generated by evaluating the user message to map touched repositories, enabling the session-manager to decide routing before opening a full sub-session.

How do I handle ambiguous requests in a multi-repo work session?▼

Ambiguous multi-repo requests are handled by delegating to the orchestrator as a one-shot inline subagent in scope-check mode. The orchestrator evaluates the ambiguity, maps the touched repositories, and returns a structured verdict block to clarify routing.

What files are generated when evaluating multi-repo request scope?▼

Evaluating multi-repo request scope creates a per-task sessions directory and seeds three files: scope.md, plan-draft.md, and verdict.json. These files capture the analysis, draft plan, and final routing verdict for orchestration.

When do I need to run a scope check before opening a sub-session?▼

A scope check is needed before opening a full sub-session when routing a user request across multiple repositories. It determines exactly which consumer repos are touched and outputs a verdict, allowing the session-manager to route the task efficiently.

Does scope check require any dependencies to run?▼

Scope check operates with no external dependencies. It functions as a one-shot inline subagent that evaluates the user message and writes the scope, plan-draft, and verdict files directly to the sessions directory.

Related Skills

Explore More Software Engineering Skills→
danielcastro-devdanielcastro-dev

speclet-draft

Draft collaborative feature plans with clarifying questions to .speclet/draft.md.

Community
Intermediate
jaqgjaqg

lit

Parse natural-language literature intents and sequence lit-* sub-skills.

Community
Advanced
PixelDroid19PixelDroid19

sdd-spec

Converts ambiguous data investigation requests into precise evidence specifications for Data Manager flows.

Community
Intermediate
vndkubivndkubi

impact-analysis

Trace reverse dependencies and estimate blast radius for proposed codebase changes.

Community
Advanced