Skill

scope

Create a task scope before starting work. Defines boundaries, acceptance criteria, and file limits to prevent scope creep. Use before any non-trivial task.

Install

npx claudepluginhub artmin96/forge-studio --plugin behavioral-core

Tool Access

This skill is limited to using the following tools:

ReadWriteGlobGrep

SKILL.md

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

startup-financial-modeling

Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.

startup-business-analyst

32.9k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Steps

Parse the task description from $ARGUMENTS.

Identify which files will need to change. Use Glob and Grep to find relevant files — keep the list tight.

Create the directory .claude/scopes/ if it does not exist.

Generate a scope document at .claude/scopes/{task-name}.md where {task-name} is a slugified version of the task (lowercase, hyphens, no spaces).

Scope Document Format

The document must be under 15 lines. Use this exact structure:

# {Task Name} ## Task {One sentence: what exactly needs to change.} ## Files {Explicit list of files that will be touched — one per line, prefixed with `-`.} ## Boundaries {What does NOT change — explicit exclusions, one per line, prefixed with `-`.} ## Done When {Testable acceptance criteria — one per line, prefixed with `-`.} ## Max Files {Number — default 5. Adjust if the user specifies a different limit.}

Create Task Scope

Define a focused scope for: $ARGUMENTS

Steps

Parse the task description from $ARGUMENTS.
Identify which files will need to change. Use Glob and Grep to find relevant files — keep the list tight.
Create the directory .claude/scopes/ if it does not exist.
Generate a scope document at .claude/scopes/{task-name}.md where {task-name} is a slugified version of the task (lowercase, hyphens, no spaces).

Scope Document Format

The document must be under 15 lines. Use this exact structure:

# {Task Name}

## Task
{One sentence: what exactly needs to change.}

## Files
{Explicit list of files that will be touched — one per line, prefixed with `-`.}

## Boundaries
{What does NOT change — explicit exclusions, one per line, prefixed with `-`.}

## Done When
{Testable acceptance criteria — one per line, prefixed with `-`.}

## Max Files
{Number — default 5. Adjust if the user specifies a different limit.}

After Creating

Present the scope document to the user and ask: "Does this scope look right? Confirm and I'll start."

Do NOT proceed with implementation until the user confirms.