agentleFS
Sign inStart free
quietmachineworksquietmachineworks/qmw/skills/help/SKILL.md

help

Skill0 starsChanged 2 months agoMITView on GitHub

The qmw skills - what each does, and when to reach for it

76 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 9 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 57 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Keep the shape - one line per skill, the trigger first, the moment it belongs to second.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 57 edited versions of this file we could read. “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

Print the map below, in the language of the conversation, and nothing else: no preamble, no summary after it, no offer to run one. The user typed a help command; they want the list and their prompt back.

Keep the shape - one line per skill, the trigger first, the moment it belongs to second. Adapt the wording to the language, never the order.

before the code is written
  /qmw:audit-rules      which of your stated rules are actually enforced, and which could be
  /qmw:freeze-rule      build the check for one rule, freeze today's count, wire it into CI

a codebase you inherit or doubt
  /qmw:audit-codebase   the whole codebase under nine lenses, prioritized, fixes nothing
  /qmw:refactor         one finding repaired, behavior pinned before and proven after
  /qmw:upgrade-deps     dependencies raised one proven step at a time, each raise alone

a codebase you keep
  /qmw:build-feature    one change built and proven to land, the rest held, fresh eyes on the diff

before it reaches users
  /qmw:run-qa           play a real user through the UI, screen by screen, on an empty environment
  /qmw:check-release    the release checklist executed - clean clone, real artifact, go or no-go

when something is already wrong
  /qmw:fix-bug          one reported bug, reproduced in a browser before any fix, proven after

when you pick the work back up
  /qmw:status           where the work stands - open bugs, work landed, deps held, last verdict

when the agent itself is the problem
  /qmw:audit-agent      what your skills, hooks and plugins cost against what they earn

the whole cycle at once
  /qmw:full-cycle       audit-codebase, refactor, upgrade-deps, run-qa, check-release - one guided passage

this map
  /qmw:help             the skills and the moment each one belongs to

Then close with these two lines, translated the same way:

audit-codebase feeds refactor, run-qa and fix-bug feed each other, check-release gates the tag.
Everything that audits writes nothing; everything that repairs proves it did.

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.

Check your setup, free