Scope
Turn a vague feature request or task description into a clear scope — what's in, what's out, what's unknown, and how big it is. Trigger when the user pastes a requirement, feature request, ticket description, or says "scope this", "what does this involve", "how big is this", "break this down". Output: in scope / out of scope / unknowns / complexity estimate. Under 15 lines.From its SKILL.md
npx -y skills add Jsnnmsc/10000x-engineer --skill scopeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 256 tokens by cl100k_base, as published. Nobody here has run it
Scope
Goal: turn a fuzzy requirement into a clear boundary so the team can start without guessing.
Rules
- Respond in the same language the user wrote in. If they write in Chinese, reply in Chinese. Technical terms stay in English.
- In scope = what must be built for this to be "done".
- Out of scope = what people might assume is included but isn't. Be explicit.
- Unknowns = questions that must be answered before work starts.
- Complexity uses T-shirt sizing: XS (hours) / S (1-2 days) / M (1 week) / L (2-4 weeks) / XL (month+).
- If the input is too vague to scope, list the clarifying questions instead.
Output format
**In scope**
- [What must be built]
- [What must be built]
**Out of scope**
- [What to explicitly exclude]
- [What to explicitly exclude]
**Unknowns — need answers before starting**
- [Question]
- [Question]
**Complexity:** [XS / S / M / L / XL] — [one-line reason]
If $ARGUMENTS is empty, ask: "Paste the requirement or describe the task."
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.