Scope Work
PLANNING SPINE STEP 1 of 3 — Scope the work: define what is in and out of scope and save as specs/product/SCOPE_LATEST.yaml. Use before slice-tasks or plan-release on any new initiative. Not a substitute for slice-tasks (step 2) or plan-work (step 3).
Install
npx skills add danielvm-git/bigpowers --skill scope-workgit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/scope-work ~/.claude/skills/scope-workPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Scope Work > **Spine position:** Step 1 — scope-work → slice-tasks → plan-work. Turn the current conversation into a bounded PRD at `specs/product/SCOPE_LATEST.yaml`. Without a scope boundary, implementation drifts — stories expand, estimates blow up, and "done" becomes undefined. ## Pre-flight - [ ] Do you have a clear user need or problem statement? If not, run `elaborate-spec` first. - [ ] Does `specs/product/VISION_LATEST.yaml` exist? If yes, read it for north-star alignment. - [ ] Is there an existing `SCOPE_LATEST.yaml`? If yes, you're refining, not creating from scratch. ## Process 0. **Read planning-context.yaml** — If `specs/planning-context.yaml` exists, read it before doing anything else: ```bash test -f specs/planning-context.yaml && echo "Context found" || echo "No context — starting fresh" ``` Pre-populate `feature_name`, `constraints`, and `out_of_scope` from the file. Skip re-asking questions already answered by elaborate-spec. If the file is absent, proceed normally. 1. **Gather context** — Read existing `specs/` artifacts (`release-plan.yaml`, `plans/TECH_STACK_LATEST.md`, `requirements/VISION_LATEST.yaml` if any). Understand what the project is building and why. 2. **Interview (if needed)** — Clarify: What is the goal? Who are the users? What is definitely in scope? What is explicitly out of scope? What constraints exist (time, budget, tech)? How will success be measured?
Details
- Skill name
scope-work- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/scope-work/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Scope Work skill do?
PLANNING SPINE STEP 1 of 3 — Scope the work: define what is in and out of scope and save as specs/product/SCOPE_LATEST.yaml. Use before slice-tasks or plan-release on any new initiative. Not a substitute for slice-tasks (step 2) or plan-work (step 3).
How do I install the Scope Work skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill scope-work. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Scope Work popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Assess Impact
292danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Slice Tasks
292danielvm-git/bigpowers
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
Run Planning
292danielvm-git/bigpowers
DISCOVER-PHASE ADVANCER — Drive the discover-phase checklist (specs/planning-status.yaml) through survey-context → scope-work → research-first → elaborate-spec → plan-release → slice-tasks. NOT a duplicate of plan-work or the planning spine; it orchestrates the pre-coding discover phase only.
State Management
207Owl-Listener/ai-design-skills
Managing shared context, memory, and state across multiple agents.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.