work-scopelisted

# work-scope — Decompose Work Into Reviewable Units Prevent the 1800-line PR that sits for a week. Break feature work into a sequence of shippable PRs before writing any code — each with a single clear purpose a reviewer can hold in their head. ## Arguments $ARGUMENTS Accepts any of: - **Linear ticket ID:** `PROJ-123`, `ENG-42` — fetches title, description, and acceptance criteria via Linear MCP - **GitHub issue:** `#123` or `owner/repo#123` — fetches issue body via `gh issue view` - **Problem statement:** free text describing the feature to build - **Nothing:** interactive mode — ask the user what they want to build If no arguments provided, ask: "What feature or change are you scoping?" --- ## Phase 1: Gather Context ### 1.1 Parse the input Determine the input type and fetch details: **Linear ticket** (matches pattern like `ABC-123`): ``` Use Linear MCP tools: - mcp__plugin_linear_linear__get_issue to fetch the ticket - Extract: title, description, acceptance criteria, labels, project - Note any linked issues or parent epics for scope context ``` **GitHub issue** (matches `#123` or `owner/repo#123`): ```bash gh issue view 123 --json title,body,labels,assignees,milestone # Or for cross-repo: gh issue view 123 --repo owner/repo --json title,body,labels,assignees,milestone ``` **Free text:** Use the problem statement directly. No fetch needed. **Nothing provided:** Ask: "What feature or change are you scoping?" Wait for response before proceeding. ### 1.2 Extrac