Scope
Run /scope to turn a product idea into a living, coarse scope in docs/scope/ and keep...
Install
npx skills add jsmastery-pro/skills --skill scope -g -a claude-code -y- Repository
- jsmastery-pro/skills1.6k
- Category
- Design
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Mediumabout 2,678 tokens
- Runs scripts
- No, instructions only
What it does
Run /scope to turn a product idea into a living, coarse scope in docs/scope/ and keep it current: plan a new product, plan the next slice, enroll one named feature, or run with no argument to reconcile after shipping and queue what is next. Seeds WHAT to build; /architect designs, /develop builds.
Output style (plain words, no dashes, no hyphens)
<!-- OUTPUT-STYLE:START -->Write everything this skill produces, files and messages alike, in plain simple language. Talk to the reader as you, warm and direct like a colleague, and present every step as a recommendation they may run or skip, never an order. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only, not read-only. Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. Use short sentences, commas, or parentheses. Clear beats clever.
What this skill does
Turns an idea into an ordered, coarse, living plan and keeps it honest as the product ships. Answers what to build, in what order, how heavy, which need a decision first, not how to build one thing (that is /architect and /develop).
Scope shape, coarse and small: a slim At a glance table (# · Feature · Phase · Status) + feature sections grouped by phase (see scope-template.md). Each section: heading ### N. Name with short tags only when they matter (needs a decision, an approach override, a workflow tier override like · GA), a 1 to 2 line intent, one Done when: line (acceptance criteria seeds, the WHAT), checkbox steps.
Feature shape lifecycle: not yet designed → one box, its entry command. On spec capture, /architect fills the built ready shape: Design it (spec) ticked, spec linked, Build it: /develop <feature> with 2 to 5 milestone sub items rolled up from the spec's ## Build plan, then Verify it: /check verify <feature> and Test it: /test <feature>. Atomic build tasks stay in the spec's ## Build plan, never here; every box is a command or tracked milestone. Status: in the table and beside the heading; spec and code pointers once they exist.
