---
name: Scope Framing
slug: scope-framing
category: AI Engineering
description: Scope Framing defines the decision, audience, deliverable, exclusions, and failure modes before research starts. Use it when you need research that stays tied to an operational question.
github: "https://github.com/ferrumclaudepilgrim/claude-code-android/tree/main/.claude/skills/scope-framing"
language: Shell
stars: 222
forks: 30
install: "npx degit https://github.com/ferrumclaudepilgrim/claude-code-android/tree/main/.claude/skills/scope-framing ~/.claude/skills/scope-framing"
installs_to: ~/.claude/skills/scope-framing
source_path: .claude/skills/scope-framing/SKILL.md
collection_size: 3
category_size: 2970
collection_url: "https://dirskills.com/collections/ferrumclaudepilgrim/claude-code-android"
added: 2026-09-04T05:24:54.914Z
last_synced: 2026-09-04T05:24:54.914Z
canonical_url: "https://dirskills.com/skills/scope-framing"
---

# Scope Framing

Scope Framing defines the decision, audience, deliverable, exclusions, and failure modes before research starts. Use it when you need research that stays tied to an operational question.

**Install:**

```bash
npx degit https://github.com/ferrumclaudepilgrim/claude-code-android/tree/main/.claude/skills/scope-framing ~/.claude/skills/scope-framing
```

## README

# Scope Framing

Answer every question before starting research. Write the answers into a brief scope document: one paragraph or a short list per question. Then proceed. If you cannot answer question 1, ask the user before starting.

## Required Questions

**1. What decision will this research serve?**
One sentence. Name the decision that will change based on what you find. If no decision is downstream of this research, the research has no purpose. Example: "Whether to use package X or build a custom implementation."

**2. Who will act on the findings?**
Name the actor: a user, an agent, or another system. Different actors need different formats and levels of detail. An agent needs a recommendation. A decision-maker needs tradeoffs. Someone following instructions needs steps.

**3. What does "done" look like?**
Name the specific deliverable that closes this research. Not "I understand the topic" but "a one-page comparison of options A, B, and C with a recommendation." Research without a defined end state expands forever.

**4. What is explicitly out of scope?**
Name at least 2 things you will not research. Naming exclusions forces a scope decision and prevents drift. If you cannot name exclusions, your scope is not defined yet.

**5. What would make this research useless?**
Identify failure modes before you start. Common causes: wrong scope (you answered a related but different question), stale data (the information is outdated for the version in use), missing context (you don't have access to a key constraint that changes the answer).

## Output

Write the scope document before doing any research. Save it or include it at the top of your research output. If scope cannot be defined (if question 1 has no answer), stop and ask the user to clarify the decision before you proceed.
