Run any Skill in Manus with one click

scope

Stars1

Forks0

UpdatedJuly 4, 2026 at 08:11

Plan, track, and report multi-step work using Scope. Use when the user wants Codex to manage project state, open tickets, progress, bugs, branches, PRs, or agent coordination.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

briannadoubt

briannadoubt/scope

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	scope
description	Plan, track, and report multi-step work using Scope. Use when the user wants Codex to manage project state, open tickets, progress, bugs, branches, PRs, or agent coordination.
metadata	{"short-description":"Use Scope kanban while coding"}

Scope

Use Scope when work is more than a trivial one-off. Scope is a local-first kanban with epics, stories, bugs, relations, comments, branches, PR links, a web UI, and realtime updates.

Read ../../references/guardrails.md before mutating tickets.

Default Flow

Inspect state with scope --json board or scope --json ticket list.
For new multi-step work, create one epic and focused child stories.
Move the active ticket to in_progress when work starts.
Add comments when a discovery matters to another agent or future you.
Attach branch or PR links when they exist.
Mark tickets done as each discrete piece finishes.

Use scope batch --by codex for related multi-record changes.

More from this repository

same repository

scope

briannadoubt/scope

Plan, track, and report on multi-step work using the Scope kanban (local CLI + web UI). Use when the user asks you to scope/plan a project, list open work, mark a ticket done, link a branch/PR, or coordinate with other agents on shared state. Don't use for one-off questions or trivial single-edit requests.

2026-07-091

board-context

briannadoubt/scope

Summarize the current Scope board, identify active work, and choose the next ticket. Use when starting a session, resuming work, or giving status.

2026-07-041

git-handoff

briannadoubt/scope

Attach branches and PRs to Scope tickets and prepare handoff comments. Use when creating branches, opening PRs, finishing work, or handing work to another agent.

2026-07-041

multi-agent

briannadoubt/scope

Coordinate multiple Codex agents working in one Scope workspace. Use when tasks are parallelized, handed off, blocked, or updated by several agents.

2026-07-041

plan-work

briannadoubt/scope

Break a user request into Scope epics, stories, and bugs before implementation. Use for feature work, refactors, investigations, and broad tasks that need visible progress.

2026-07-041

ticket-ops

briannadoubt/scope

Create, edit, comment, link, prioritize, and close Scope tickets from Codex. Use when the user asks for ticket changes or when work progress should be recorded.

2026-07-041

name	scope
description	Plan, track, and report multi-step work using Scope. Use when the user wants Codex to manage project state, open tickets, progress, bugs, branches, PRs, or agent coordination.
metadata	{"short-description":"Use Scope kanban while coding"}

Scope

Use Scope when work is more than a trivial one-off. Scope is a local-first kanban with epics, stories, bugs, relations, comments, branches, PR links, a web UI, and realtime updates.

Read ../../references/guardrails.md before mutating tickets.

Default Flow

Inspect state with scope --json board or scope --json ticket list.
For new multi-step work, create one epic and focused child stories.
Move the active ticket to in_progress when work starts.
Add comments when a discovery matters to another agent or future you.
Attach branch or PR links when they exist.
Mark tickets done as each discrete piece finishes.

Use scope batch --by codex for related multi-record changes.