← ClaudeAtlas

sprint-scopinglisted

Phase 2 of /cadence:weekly. Sequential per-project scope interview (5 carry-over Qs + 5 scope Qs, one at a time) with brainstorming and the issue-quality-gate. Triggers on "sprint planning", "weekly scope", "what ships this week", "scope the next cycle", or "/cadence:weekly phase 2".
Brite-Nites/brite-claude-plugins · ★ 0 · AI & Automation · score 59
Install: claude install-skill Brite-Nites/brite-claude-plugins
# Phase 2 — Sprint Scoping Sequential per-project loop. For each active project, surface alternatives via brainstorming, run the adaptive interview from BC-5810 § 2 (5 carry-over Qs + 5 scope Qs), enforce the issue-quality-gate from § 3 with block-with-override, and append a project block to the weekly-planning checkpoint as decisions accumulate. No Linear mutations — those are deferred to Phase 3 (BC-5761). This skill is inline (model inherits). Phase 2 is interactive Q&A — it cannot run as a dispatched subagent (per BC-5760 issue Notes). ## Gate-respect Every multi-option `AskUserQuestion` in this skill is bound by the [gate-respect contract](../_shared/gate-respect.md). Once the planner picks an option — at the enricher-dispatch-error prompt, any CQ/SQ prompt, or the quality-gate failure prompt — execute that exact option. If an internal code path wants to deviate (condense, skip, batch, fast-path under context pressure), re-prompt via a new `AskUserQuestion` instead of silently self-selecting a lighter variant. Writing to a dogfood-notes, checkpoint, or breadcrumb file is not permission to deviate. Origin: BC-5866 (W17 dogfood of this skill). ## § 1 Inputs (state object) Reads from the session state object populated by Phases 0–1: - `state.team.id` — Brite Company UUID, set in Phase 0 - `state.cycle.current` — cycle being *planned* (W+1) - `state.cycle.previous` — cycle being *audited* (W) - `state.projects[].audit_card` — Phase 1 fan-out output (`shipped`, `carry_