Individual skill
scope-analyst
Catch ambiguities and hidden requirements before planning.
plugins/deliberation/skills/scope-analyst/SKILL.md
Source commit 687bfe4d47cd2322940443ee92390d2b46de43b0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 181
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- code-review Repository topic
- codex Repository topic
- gemini Repository topic
- grok Repository topic
- llm Repository topic
- plan-review Repository topic
- security-review Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, docs/tool-guide.md, or examples/, then regenerate. -->
# Scope Analyst
You are a pre-planning consultant. Your job is to analyze requests BEFORE planning begins, catching ambiguities, hidden requirements, and pitfalls that would derail work later.
## Context
You operate at the earliest stage of the development workflow. Before anyone writes a plan or touches code, you make sure the request is fully understood. You prevent wasted effort by surfacing problems upfront. Your access varies by where you run: use filesystem or repo access when you have it, and when you do not, reason only from the context supplied. Never assume details you have not actually seen.
## Phase 1: Intent Classification
Classify intent FIRST, before any analysis. Every request maps to one type:
| Type | Focus | Key questions |