← ClaudeAtlas

scope-architectlisted

Use this skill to map the vertical scopes of a feature — Shape Up's "map the scopes" (step 8) as committed, mechanically enforceable contracts. Triggers on: "map the scopes", "write the scope contracts", "scope contract", "the discovered tasks don't fit any scope", "re-slice the substrate" (operations map-scopes). Writes the committed scopes/*.md contracts by import-graph slicing along business flow, with write-whitelist substrates and e2e fixtures. NOT for decomposing a pitch into tasks (ba-pitch-analyzer) or cutting scope at ship time (scope-hammer).
nguyenvanphituoc/shapeup-sdlc-plugin · ★ 2 · AI & Automation · score 75
Install: claude install-skill nguyenvanphituoc/shapeup-sdlc-plugin
# Scope Architect (pure worker v1.0) **Slice by flow, never by directory — and write it as a contract a hook can enforce.** Groups a feature's tasks into independent, vertically-sliced **scopes** and writes each as a committed contract (`shapeup/<slug>/scopes/<scope-id>.md`) the rest of the harness enforces mechanically: the sandbox hook denies writes outside a substrate, t0-verify runs the fixtures, the evaluator asserts only against the affordance manifest. This skill is the **sole writer** of scope contracts — a distinct authority from the planner (task decomposition) and a distinct failure mode (directory-thinking, PA1) deserving its own anti-rationalization table. ## Input contract — the WorkOrder | Field | What it is | |---|---| | `operation` | `map-scopes` — the only operation this skill has. It covers first slicing after the board exists, folding discovered items in, and re-slicing a stuck scope; the payload says which of those you are doing | | `payload.feature` / `payload.spec_folder` | Slug + committed spec (read ux-behavior.md for manifests; usecases for flows) | | `payload.tasks[]` | The board's tasks with their touched files — the slicing input | | `substrate.allowed` | `scopes/*.md` + `scope-board.md` — your ONLY write surface | ## Core process ``` 1 SLICE build an import/business-flow graph over the tasks' touched files (grep heuristic is fine; AST is an optimization). One scope = one call chain: the UI screen + the API route + t