scopelisted

# Scope `/scope` is the second parent skill in the shirabe parent-skill pattern, sitting on the tactical chain (BRIEF → PRD → DESIGN → PLAN) the way `/charter` sits on the strategic chain (VISION → STRATEGY → ROADMAP). It walks an author through the four tactical-chain children as a single conversation, holds state across child boundaries, enforces the pattern-level invariants (state schema, resume ladder, three exit paths, child inspection, worktree discipline), and lands at one of three terminal exits: a `full-run` that produces a PLAN at `docs/plans/PLAN-<topic>.md`, a `re-evaluation` exit that writes a Decision Record at a settled- upstream boundary (PRD or DESIGN), or an `abandonment-forced` exit that force-materializes the most-recently-running child's intermediate as a Draft artifact. The pattern-level contract surface is documented in `${CLAUDE_PLUGIN_ROOT}/references/parent-skill-pattern.md` and its four companion references. `/scope` is the second concrete consumer after `/charter`; the seven SKILL.md structural elements below align section-by-section with the pattern's required structural elements, and the prose contracts after them bind the `/scope`-specific asymmetries the tactical chain introduces (two settled-upstream boundaries, a Mandatory-with-auto-skip gate on `/prd`, a refuse- and-redirect Slot 5 shape for PLAN's downstream-owned lifecycle states, and a terminal child with two output modes). ## Team Shape `/scope` runs as a single-agent skill in the v1