Agent skill

fable-scope-discipline

Use when implementing any change in existing code — when tempted to clean up nearby code, add unrequested validation or options, fix something "arguably in scope", or when the diff is growing past what was asked.

DizzyMiigithub.com/DizzyMiiGitHub ↗
claude-codeMIT
Install
npx skills add DizzyMii/fable-skills --skill fable-scope-discipline --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/fable-scope-discipline/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 52
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Scope Discipline ## Overview Build exactly what was asked, at the right altitude: deep enough to fix the cause, narrow enough to touch nothing else. Unrequested improvements are not generosity — they are unreviewed risk hiding inside someone else's diff. ## Rules 1. **Implement what was asked.** Nothing speculative, nothing "while I'm here." 2. **Adjacency is not scope.** "Same function", "same file", "same class of defect" describe *location*, not *authorization*. The user's words define the task; nearness defines nothing. 3. **The argument test.** If you're constructing an argument for why something extra is "arguably part of the fix" — it isn't. Real scope never needs the argument. Put the argument in your report and let the user decide. 4. **The open-question test.** If the extra fix has an unresolved design choice (raise or clamp? rename to what?), that proves it's its own task. You can't settle a contract question inside someone else's bugfix. 5. **Right altitude.** Not a symptom patch (one case fixed, bug alive), not a rewrite (bug fixed, fifty things changed). Root cause, within scope. 6. **No drive-bys.** No renames, reformatting, refactors, or dependency bumps the chang

What's inside
Steps it walks through
  1. Overview
  2. Rules
  3. Rationalizations (verbatim from baseline failure)
  4. Red Flags — stop and shrink the diff
More from fable-skills
All skills →
About this skill
What does the fable-scope-discipline skill do?

Use when implementing any change in existing code — when tempted to clean up nearby code, add unrequested validation or options, fix something "arguably in scope", or when the diff is growing past what was asked.

How do I install it?

Run `npx skills add DizzyMii/fable-skills --skill fable-scope-discipline --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From DizzyMii/fable-skills, a repository with 52 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going