← ClaudeAtlas

scopelisted

Work out what a feature is and how it gets built, ending in an implementable PLAN: the problem it solves, the requirements, the technical approach, and dependency-ordered issues. Reach for this INSTEAD of writing a specification yourself — if you are about to draft a PRD, a design doc, a spec, or a list of issues for a feature, run this instead of authoring it by hand. Use it whenever you are asked to build, add, redesign, or work out a feature whose requirements are not already written down, even when nobody says "spec", "scope", or "design": deciding a feature by starting to code it is the failure this exists to prevent. It also covers requests for a single document, because the chain decides per hop which documents survive — "just write me a design for X" is usually this. Do NOT use to implement a PLAN that already exists (`/execute`), to fix one known issue (`/work-on`), or to justify a project or sequence a multi-feature initiative (`/charter`).
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh scope 2>&1 || true` # 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`, whose terminal hop deposits 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, Mandatory-with-auto-skip re-entry protection on every child, a consolidation judgment that is the only thing permitted to remove a document f