agentleFS
Yeachan-HeoYeachan-Heo/oh-my-claude-sisyphus/skills/show-me-your-work/SKILL.md

show-me-your-work

Skill41k starsChanged 9 days agoMITView on GitHub

Append-only decision trail for long or autonomous work: one TSV row per non-obvious decision — what was chosen, what was rejected and why, the deciding evidence. For work a human will audit later.

75 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use setup-pstack, make-bot-ui and 4 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.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 32 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 24 projects that use this

  • shiwenbin1617Skill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 17 projects that use this

  • shiwenbin1617Skill

    principle-explain-the-number

    Apply before you measure, and before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 34 projects that use this

  • rockcookiesSkill

    redesign-from-first-principles

    Apply when integrating a new requirement into an existing design.

    Also in 3 projects that use this

  • JoshueOsunaSkill

    Poteto Mode

    poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

    Also in 3 projects that use this

The file

Files
SKILL.md

Show Me Your Work

For work a human will audit after the fact, the reply is not the record — the trail is. One row per non-obvious decision, written as it is made.

When to use

  • long, autonomous, or multi-phase work ("run until done", overnight runs)
  • any task the user steps away from and will trust on return
  • multi-day programs where the trail is the post-mortem

The trail

Append to state/decision-trail-{task-slug}.tsv under OMC's state root (create with a header row on first write; one file per task slug when sessions share a checkout). The task slug is lowercase kebab-case and is part of the canonical path. Resolve the state root the way OMC's own scripts do — the checkout's .omc/ by default; when OMC_STATE_DIR is set or a parent .omc-workspace redirects state, the root moves with it, so sibling sessions on the shared root see the same trail. Sibling sessions sharing that root also share the file: hold a lock around the header-exists check and each append — the same file-lock the verification-ledger writer uses (withFileLock on a <trail>.lock sidecar) — or concurrent first writes duplicate the header and racing appends lose rows:

ts <TAB> task <TAB> decision <TAB> rejected <TAB> evidence
  • decision: what you chose, one sentence.
  • rejected: the real alternatives you weighed and the one-line reason each lost. "None considered" is a valid, damning entry.
  • evidence: the command, output, or citation that decided it.

Cell guard: a cell starting with =, +, -, or @ is prefixed with ' so spreadsheet readers cannot parse it as a formula; tabs and newlines inside a cell become spaces. Append only — the trail is never rewritten.

Rules

  • Log at decision time, not at recap time; a trail reconstructed at the end is fiction with a timestamp.
  • Routine mechanical steps are not decisions; judgment calls, scope changes, and risk acceptances are.
  • The final reply summarizes the trail and links it; the trail itself stays the auditable artifact. It is local runtime state under OMC's state root — by repository policy it is not committed; when stakes need an immutable record, quote the decisive rows into the PR description or the linked issue instead of force-adding runtime state.

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.