Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Search & research

scope

Scope definition before implementation — two modes. Quick mode (default): IN/OUT/exit criteria brief → BRIEF.md. Full mode (/scope full): L0→L4 layered spec chain → spec.md. Trigger: '/scope', '/brief', '/specify', 'scope this', '스펙 잡아줘', '범위 잡아줘', 'spec 만들어', '스펙 만들어', '기획 정리해줘', 'plan this'. Do NOT trigger for: bug fixes, single-file changes, existing spec, brainstorming.

AlexZio00 · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add AlexZio00/sovereign-skills --skill scope

About this skill


skill_type: workflow tools: Read, Write, Edit, Glob, Grep, Agent, Bash, AskUserQuestion name: scope user_invocable: true description: | Scope definition before implementation — two modes. Quick mode (default): IN/OUT/exit criteria brief → BRIEF.md. Full mode (/scope full): L0→L4 layered spec chain → spec.md. Trigger: '/scope', '/brief', '/specify', 'scope this', '스펙 잡아줘', '범위 잡아줘', 'spec 만들어', '스펙 만들어', '기획 정리해줘', 'plan this'. Do NOT trigger for: bug fixes, single-file changes, existing spec, brainstorming. not_for:

  • "Bug fix, single-file change -> implement directly"
  • "Existing BRIEF.md/spec.md -> Edit directly"
  • "Exploration only -> brainstorming agent" see_also:
  • skill: goal-lock relation: "scope=planning, goal-lock=execution"
  • skill: freeze relation: "scope=define boundaries, freeze=enforce boundaries" depends_on: skills: [] agents: [] files:
    • "CLAUDE.md"
    • "scripts/ambiguity_gate.py" concurrency_profile: sequential

/scope — Scope Definition Engine v1.0

Unified brief + specify. Lock down "what you will do and what you will NOT do" before implementation. Quick (default) = IN/OUT lock + BRIEF.md. Full = L0→L4 layer chain + spec.md.

Dominant Variable

Is the Scope OUT section explicitly written? — IN alone causes scope creep during implementation. OUT must be explicit to lock it. In Full mode, additionally L2 decision clarity is the dominant variable.

Trigger

  • /scope (Quick default)
  • /scope full (Full mode)
  • /brief (Quick backward compat)
  • /specify (Full backward compat)
  • "scope this", "스펙 잡아줘", "범위 잡아줘", "기획 정리해줘"
  • "spec 만들어", "스펙 만들어", "plan this"

Discard If

  • Bug fix, 1-file edit → implement directly
  • BRIEF.md/spec.md already exists → use Edit
  • Exploration only → delegate to brainstorming

Key Assumptions

  1. Project CLAUDE.md exists (existing projects) — if broken: can't auto-scan constraints, write from user input only.
  2. User provides idea/requirement in ≥1 sentence — if broken: ask "Tell me in one sentence what to build" once.

Mode Selection

ModeTriggerOutputBest For
Quick (default)/scope, /briefBRIEF.mdFeature add, clear change
Full/scope full, /specifyspecs/{name}/spec.mdArchitecture change, multi-module, complex design

Unsure? Start Quick → if user wants more detail: "Shall we switch to full mode?"


Quick Mode — IN/OUT Brief

Step 1: Detect project

  • Existing project: CLAUDE.md, package.json etc. exist → 2-level Glob + keyword Grep (10-file cap)
  • New project: skip

Step 2: Ambiguity score gating

Score clarity across 4 dimensions (0-10 each), by judgment.

DimensionCheck
FunctionWhat behavior is being added/changed — are inputs/outputs concrete?
BoundaryWhat is explicitly excluded — is IN/OUT clear?
VerificationHow is "done" verified — is there a measurable criterion?
AssumptionsAny hidden assumptions — dependencies on existing system/data/environment?

Gating (deterministic): hand the 4 scores to the gate script and read its stdout — don't average them by eye. Resolve the script from the skill's own directory rather than a path relative to the invocation cwd — python scope/scripts/... only works when the shell happens to be sitting one level above scope/, and breaks in every other cwd:

GATE_SCRIPT=$(find ~/.claude -name "ambiguity_gate.py" -path "*/scope/scripts/*" -type f 2>/dev/null | head -1)
python "$GATE_SCRIPT" quick --scores '{"function":8,"boundary":7,"verification":6,"assumptions":9}'
# -> {"ok": true, "avg": 7.5, "weakest": "verification"}

ok: false → target the dimension the script names as weakest with clarifying questions (max 3). Exceeds question limit → conservative minimum scope + [assumed] tag.

Step 3: Generate Brief

## Brief: [feature name — verb phrase]

**Goal**: [1-2 sentences. Start with verb.]

**Scope IN**
- [concrete items]

**Scope OUT** ← Required, min 2 items
- [natural extension but excluded]

**Constraints**
- [file/action/integration constraints — min 1 if existing project]

**Exit Criteria**
- [ ] [who/what] [action] → [measurable result]

**Risk Flags**
- [min 1]

**Contraindication**
- [condition where this approach doesn't fit — min 1]
- Example: "If data > 100K rows, this design has performance issues", "If team > 2 people, API contract first"

Step 4: Min-item validation → Approval → Save BRIEF.md

The gate script takes --file, not stdin, so it needs something on disk to read — but Invariant 5 says the deliverable (BRIEF.md) isn't saved until after approval, and approval isn't requested until the script says ok: true. Break that cycle by writing the drafted brief to a scratch file (e.g. .scope-draft.md) first: the scratch write is not the Invariant-5-gated save, it exists purely so the deterministic script has a path to read. Draft freely, re-run the gate as many times as needed, all before any approval exists.

Validate the scratch draft against the minimum-item requirements — don't count bullets by eye. A bolded aside inside a section (e.g. **Note**: ...) can look like a new section header on a human skim and silently truncate a manual count; a regression test locks this exact failure mode closed in the script.

GATE_SCRIPT=$(find ~/.claude -name "ambiguity_gate.py" -path "*/scope/scripts/*" -type f 2>/dev/null | head -1)
python "$GATE_SCRIPT" min-items --file .scope-draft.md
# -> {"scope_out": 2, "risk_flags": 1, "contraindication": 1, "constraints": 1, "ok": true}

Pass --new-project for new projects (Invariant 6 waives the Constraints requirement). ok: false → the per-field counts in the JSON show which section is short; revise .scope-draft.md, add items there, and re-run before moving to approval.

Request approval only once the script reports `ok: true

Read the complete source ↗