scope-worklisted

Define what is in and out of scope for the current effort and save as specs/product/SCOPE_LATEST.yaml. Use when user wants a PRD, scope definition, or before plan-release on a new initiative.model: sonnet
danielvm-git/bigpowers · ★ 2 · AI & Automation · score 66

Install: claude install-skill danielvm-git/bigpowers

# Scope Work Turn the current conversation into a bounded PRD at `specs/product/SCOPE_LATEST.yaml`. ## Process 1. Read existing `specs/` artifacts (`release-plan.yaml`, `plans/TECH_STACK_LATEST.md`, `requirements/VISION_LATEST.yaml` if any). 2. Interview (if needed): goal, users, in-scope, out-of-scope, constraints, success metrics. 3. Write `specs/product/SCOPE_LATEST.yaml` with: `core_value`, `summary`, `in_scope[]`, `out_of_scope[]`, `constraints`, `success_criteria`, `references`. 4. Run `research-first` if external dependencies are proposed. > **HARD GATE** — Every `in_scope` item must map to a future epic/story ID or explicit deferred note in `out_of_scope`. ## Verify → verify: `test -f specs/product/SCOPE_LATEST.yaml && grep -c 'out_of_scope' specs/product/SCOPE_LATEST.yaml | awk '{if($1>0) print "OK"; else print "MISSING"}'`