Skill

scope

From orc

Shape a backlog item or freeform idea into a scoped plan file before executing. Interactive: reads item context, explores relevant codebase, asks 1-2 clarifying questions, writes .orc/plans/<slug>.md that orc:orchestrate can consume directly. Use when: "orc scope", "orc:scope", "scope this", "shape this idea", "plan before executing", "break this down", or when the user wants to refine an idea before committing to orc:orchestrate. Part of the orc system: orc:orchestrate, orc:backlog, orc:autoresearch, orc:status, orc:recap, orc:scope, orc:handoff.

npx claudepluginhub athan-dial/skills --plugin orc

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Bridge between a backlog item and orc:orchestrate execution. Refine scope interactively before committing.

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 15, 2026

Actions

View Source View Plugin View on GitHub View README

scope

From orc

Orc: Scope

Bridge between a backlog item and orc:orchestrate execution. Refine scope interactively before committing.

Input

orc:scope <backlog-id> — load from .orc/backlog/items/<id>-*.md

orc:scope <freeform description> — scope from scratch

Flow

Load context: Read the backlog item markdown (if from backlog) or parse the freeform description

Explore codebase: Read the files listed in the item's "Files involved" section. Check current state — has anything changed since the item was captured?

Clarify (max 2 questions via AskUserQuestion): Ask only if scope is ambiguous or there are meaningful alternatives. Skip if the item is already well-defined.

Decompose: Break into 2-8 tasks with:

Title + description
Executor routing (Claude direct / Cursor / Codex)
Dependencies between tasks
File paths per task
Guard command

Write plan: Save to .orc/plans/<slug>.md

Plan file format

# <Title> Source: .orc/backlog/items/<id>.md (or "freeform") Scoped: <date> Guard: <command> ## Tasks ### 1. <Task title> - **Executor**: Cursor - **Files**: path/to/file.py - **Description**: What to do - **Depends on**: none ### 2. <Task title> - **Executor**: Codex - **Files**: path/to/new_file.py, path/to/existing.py - **Description**: What to do - **Depends on**: Task 1 ## State delta since capture <What changed in the codebase since the backlog item was created — helps orc:orchestrate adjust>

After scoping

Offer two choices:

Execute now — invoke orc:orchestrate .orc/plans/<slug>.md

Save for later — keep the plan file, return to conversation

If the item came from backlog, update its status in BACKLOG.jsonl to "scoped".

Orc: Scope

Bridge between a backlog item and orc:orchestrate execution. Refine scope interactively before committing.

Input

orc:scope <backlog-id> — load from .orc/backlog/items/<id>-*.md
orc:scope <freeform description> — scope from scratch

Flow

Load context: Read the backlog item markdown (if from backlog) or parse the freeform description
Explore codebase: Read the files listed in the item's "Files involved" section. Check current state — has anything changed since the item was captured?
Clarify (max 2 questions via AskUserQuestion): Ask only if scope is ambiguous or there are meaningful alternatives. Skip if the item is already well-defined.
Decompose: Break into 2-8 tasks with:
- Title + description
- Executor routing (Claude direct / Cursor / Codex)
- Dependencies between tasks
- File paths per task
- Guard command
Write plan: Save to .orc/plans/<slug>.md

Plan file format

# <Title>

Source: .orc/backlog/items/<id>.md (or "freeform")
Scoped: <date>
Guard: <command>

## Tasks

### 1. <Task title>
- **Executor**: Cursor
- **Files**: path/to/file.py
- **Description**: What to do
- **Depends on**: none

### 2. <Task title>
- **Executor**: Codex
- **Files**: path/to/new_file.py, path/to/existing.py
- **Description**: What to do
- **Depends on**: Task 1

## State delta since capture

<What changed in the codebase since the backlog item was created — helps orc:orchestrate adjust>

After scoping

Offer two choices:

Execute now — invoke orc:orchestrate .orc/plans/<slug>.md
Save for later — keep the plan file, return to conversation

If the item came from backlog, update its status in BACKLOG.jsonl to "scoped".