01
It starts by itself
a slice ships. Runs in Claude Code routine.
- ↻ a slice ships
after a feature merges
The scope stays honest after shipping.
Install the Scope skill and make it a habit: follow https://gethabit.dev/skills/jsmastery-pro/scope.md
4K installs2K starsMIT licenceSource on GitHub ↗

Scope
by jsmastery-pro · 4K installs
The skill
Scope turns a product idea into a living, coarse plan in docs/scope/ and keeps it current: plan a product or next slice, enroll a feature, or reconcile after shipping and queue what is next.
Only when you ask.
The habit
The scope stays honest after shipping.
↻ Runs by itselfa slice ships
When does it start? How does it check its work? What does it remember?
Stops after one reconcile pass per run.
Open with git branch, ahead/behind, feature counts by status and each in-progress resume point.
Update feature statuses to match what actually shipped.
Flag code or specs that have no scope row.
Add coarse rows for needs surfaced during the build, with intent, order and tier.
Reorder and mark which features need a spec first.
Mark any feature implying a tool choice as needs a decision, never naming the tool.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the Scope skill helps.
No. It seeds what to build and in what order; architect designs and develop builds.
No. A feature implying a tool choice is marked needs a decision, to keep the scope from rotting.
Copy the prompt at the top into your agent. It installs the skill from jsmastery-pro/skills and sets up the habit. Or run npx skills add jsmastery-pro/skills --skill scope.
Yes. It is published under MIT. Habit is free too.
Install the Scope skill and make it a habit: follow https://gethabit.dev/skills/jsmastery-pro/scope.md
All jsmastery-pro skills →More planning skills →
Works in
Made by jsmastery-pro, published under MIT. Habit links to the original and never changes it. Is this your skill?