agentleFS
smkg75smkg75/wikidoc/skills/help/SKILL.md

help

Skill2 starsChanged 18 days agoMITView on GitHub

The flow of the six commands, what each produces, and where this workspace stands.

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

Files
SKILL.md

Help

Prints the flow, then where the workspace stands. Writes nothing.

Step 1 — The flow

Print this, as is:

setup     once per machine; config.yaml from the documents themselves, the wiki anchored, the inboxes swept     files
tri       one filing pass: collect, read, route, decide, apply, learn                                         files
quick-tri the quick pass: tri sized on the inboxes alone, Desktop and Downloads first                         files
wiki      answers from the wiki and writes to it; fires on its own when a fact is asked or surfaces           wiki
tidy      the regular clean of the wiki, done alone: one git commit to read, the open questions named        wiki
help      this flow, and where the workspace stands                                                           read-only

Done when: the six lines are printed.

Step 2 — Where the workspace stands

Resolve the workspace: $WIKIDOC_HOME, default ~/.wikidoc. No config.yaml: say the machine is fresh and that /wikidoc:setup comes first; stop.

Found: run memory.py stats (scripts/ sits beside skills/ at the plugin root), list logs/ for the last archived pass, and list the headings of wiki/state.md to read the sections that hold the open questions and what awaits the user. Print, in this order:

  • the corpus — files in memory, and the unanswered and refused counts
  • the last pass — its name and date, and a bench/routing.json still in the workspace, which is a pass left hanging that /wikidoc:tri resumes
  • the open questions, one line each
  • what awaits the user, one line each

Then name the next command. A hanging pass or open questions: /wikidoc:tri. Nothing waiting: say so.

Done when: the four blocks are printed and no file was written.

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.