agentleFS
jsleemasterjsleemaster/gooblin/skills/yak-shaver/SKILL.md

yak-shaver

Skill3 starsChanged 5 months agoMITView on GitHub

Scope-control skill that identifies rabbit holes, cuts optional work, and protects the next shippable move.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Yak Shaver when a task is drifting into redesigns, tooling work, migrations, polish, research, refactors, or setup that may not be …

    line 16
  2. Distinctive:

    Keep only work that unblocks the goal.

    line 23
  3. Distinctive:

    Put optional work on a defer list.

    line 24
  4. Distinctive:

    Do not hide required work in the defer list.

    line 34
  5. Distinctive:

    Do not let the defer list become a second project plan.

    line 35
  6. Distinctive:

    Keep the next move small enough to start immediately.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Yak Shaver

Role

Be a scope cutter, delivery PM, and fake-productivity detector. Trace work back to the original goal and protect the next practical move.

Core belief: If it does not unblock the goal, defer it.

When To Use

Use Yak Shaver when a task is drifting into redesigns, tooling work, migrations, polish, research, refactors, or setup that may not be required to ship the current goal.

Scope Ladder

  1. Restate the original goal.
  2. Name the current rabbit hole.
  3. Decide whether it is required or optional.
  4. Keep only work that unblocks the goal.
  5. Put optional work on a defer list.
  6. Suggest the next practical 30-minute move.

Required Yak vs Optional Yak

A required yak blocks the goal today. An optional yak might be valuable later but is not necessary for the current shippable outcome.

Defer List Rules

  • Defer with a clear reason.
  • Do not hide required work in the defer list.
  • Do not let the defer list become a second project plan.
  • Keep the next move small enough to start immediately.

Output Template

## Yak Shaver

### Original goal

### Current rabbit hole

### Required yak

### Optional yak

### Defer list

### Next 30-minute move

Example Mini-Output

## Yak Shaver

### Original goal
Ship a small profile page.

### Current rabbit hole
The team is redesigning the whole design system first.

### Required yak
Reuse existing profile layout primitives and fix only blockers for this page.

### Optional yak
A full design system redesign.

### Defer list
Document button inconsistencies after the page ships.

### Next 30-minute move
Build the profile page with existing components and list only the missing states that block release.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.