sniff-my-plan
Skill1 starsChanged 4 months agoGPL-2.0View on GitHub
Sniff-test a plan for INTENT ALIGNMENT via `/sniff-my-plan {file?}` — a light, pre-execution backstop that answers one question: do we actually know what we are building and why? Reads the plan (a file if given, otherwise the plan in context — one read/written this session, an inline plan in the conversation, or `.omc/plans/{TICKET}/{TICKET}.md` from the branch) and reconstructs its intent as a five-part statement — Goals, Why, How-it-achieves-the-goals, Non-Goals, and Success/Done criteria. Where the plan is too thin to fill a section, it ASKS — questions batched in small groups, grouped by section, each with a proposed default so the user can reply "defaults are fine." Once the statement is complete it starts an ALIGNMENT CONVERSATION: it states its understanding back, flags where the reconstructed intent and the plan's actual content diverge, and helps the user adjust. This is NOT roast-my-plan (that audits executability) and NOT dead-horse (that probes the agent's confidence): it is the lightest gate, checking comprehension and alignment BEFORE either of those. It is advisory and EPHEMERAL — screen-only, it never writes a file and never edits the plan. ACTIVATE when the user says "/sniff-my-plan", "sniff my plan", "sniff-test this plan", "what is this plan even for", "do we agree on the goal", "gut-check this plan", or "is this plan rich enough".
In this repository19 other files it gives its agents.
- better-technical-writingSkill
- create-skillSkill
- dead-horseSkill
- debug-codeSkill
- eat-the-frogSkill
- fetch-website-contentSkill
- git-commit-instructionsSkill
- git-push-prSkill
- git-summarySkill
- hunk-reviewSkill
- javascript-development-guidanceSkill
- javascript-jestSkill
- javascript/react-17-to-18Skill
- javascript-react-development-guidanceSkill
- javascript-ts-zod-guideSkill
- react-router-v7-best-practicesSkill
- roast-my-codeSkill
- roast-my-planSkill
- ticket-fix-flowSkill
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.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.

