Output style (plain words, no dashes, no hyphens) 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 with 2 to 5 milestone sub items rolled up from the spec's

Build plan

, then Verify it: /check verify and Test it: /test . 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.

One command, inferred intent (

/scope [what]

, never a subcommand):

plan

(default): no scope yet + a product sized idea, or asking for the next slice. Full pass: ask → decompose into coarse feature sections → order + phase → write.

replan

scope exists + no argument. Opens with a short where things stand readout (git branch and ahead/behind the remote, feature counts by status, and each in-progress feature's resume point) so a bare

/scope

doubles as the "where was I, what is safe to pick up" orientation, then reconciles what shipped, surfaces plan vs reality drift (code or specs with no scope row), enrolls needs surfaced during the build, reorders, and queues the next slice. The normal living rhythm, not rare: run bare

/scope

again.

add

scope exists + argument names a single feature. Enroll one coarse row (intent + order + tier + Needs spec) without planning again: /scope . Show more Installs 261 Repository jsmastery-pro/skills GitHub Stars 785 First Seen Jul 11, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass