wtf.refine
Skill7 starsChanged 49 days agoNo licenceView on GitHub
Use when new insights change the scope, acceptance criteria, scenarios, domain language, or technical constraints of an existing Epic, Feature, or Trace — for example "refine epic #10", "re-aim feature #24", "incorporate these comments into the spec", or "the trace revealed the seam is wrong". Insights can come from CLI text, GitHub comments, referenced files or URLs, new Figma designs, or conversation context. Detects the issue kind, re-validates only what changed, shows a before/after diff, posts an audit trail comment, and cascades scenario edits to the Traces that claim them. Also the Re-aim step `wtf.loop` runs headlessly after each verified Trace.
In this repository26 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ste-writingSkill
- wtf.changelogSkill
- wtf.create-prSkill
- wtf.design-featureSkill
- wtf.design-traceSkill
- wtf.epic-to-featuresSkill
- wtf.feature-to-tracesSkill
- wtf.healthSkill
- wtf.hotfixSkill
- wtf.implement-traceSkill
- wtf.loopSkill
- wtf.pr-reviewSkill
- wtf.reflectSkill
- wtf.report-bugSkill
- wtf.retroSkill
- wtf.setupSkill
- wtf.spikeSkill
- wtf.steer-designSkill
- wtf.steer-qaSkill
- wtf.steer-techSkill
- wtf.steer-visionSkill
- wtf.verify-traceSkill
- wtf.write-epicSkill
- wtf.write-featureSkill
- wtf.write-traceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
36 rules. About 0 are common, 22 are distinctive, and 14 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈22
Distinctive · estimate
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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.