Scratch me
Cat-grade engineering skills for coding agents. Spec → tickets → TDD in worktrees, plus repo hygiene. No slop.
npx -y skills add ai-meow/felix-skills --skill scratch-meAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
What its author says it does
Copied from the file, not written here
QA/interview session to sharpen the understanding of a feature before any code. Grills the user with questions one at a time, then writes a one-page spec (goal, definition of done, out of scope, open questions) that grooming and meow consume. Use when the user says scratch-me, wants to spec a feature, clarify requirements, or align before implementation.
SKILL.md
2.0 KB, as published. Nobody here has run it
scratch-me 🐾
Scratch until it's clear. An interview, then a one-page spec. Read ../no-slop.md first.
Interview
Before asking anything, read the relevant code so questions are grounded in reality, not generic.
Ask one question at a time. Prioritize questions that:
- kill ambiguity in behavior ("what happens when X is empty?")
- expose hidden scope ("does this apply to the Monoprix channel too, or D2C only?")
- surface constraints (perf, auth, migrations, backwards compat)
- force a decision between two designs the code could support
Stop interviewing when new answers stop changing the spec — typically 5–10 questions. Never ask a question the codebase already answers.
Spec
Write docs/specs/<kebab-feature>.md from this template. Hard limit: one page. If it doesn't fit, the feature is too big — say so and propose a split.
# <Feature>
## Goal
One sentence. Who benefits, what changes for them.
## Definition of Done
- [ ] Observable, testable behaviors. Each line becomes a test in meow.
- [ ] "User sees X when Y" — not "code is clean".
## Out of scope
- Explicitly excluded things people might assume are included.
## Decisions
- Choices made during the interview, one line each, with the "why" in ≤5 words.
## Open questions
- Only questions that block nothing now. Blocking questions get asked, not written.
The DoD is the contract: grooming slices it into tickets, meow turns each line into tests. Write DoD lines so that a failing test could be written from each one verbatim.
End by outputting the spec path. Nothing else.