show-me-your-work

Maintains an append-only TSV decision log recording choices, evidence, and results for reviewable long-running work.

3|2|Updated Aug 28, 2026
One-click install
npx skills add https://github.com/adjohn/pstack --skill show-me-your-work-adjohn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: show-me-your-work
Source: https://github.com/adjohn/pstack/tree/main/skills/show-me-your-work
Command: npx skills add https://github.com/adjohn/pstack --skill show-me-your-work-adjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Long-running or unattended AI work leaves reviewers unable to reconstruct what was decided, why, and on what evidence without rereading entire transcripts. This Skill keeps a single canonical decision trail so a human can audit the run after the fact. ## Core Features & Use Cases - Structured TSV decision log: One row per decision with timestamp, phase, decision, rationale, evidence pointer, and result, rendered as a sortable table on GitHub or in a terminal. - Safe logging helper: The scripts/log.sh script appends well-formed rows, strips stray tabs and newlines, and escapes spreadsheet formula characters in untrusted cell content. - Transcript audit and cross-model review: Verifies every logged row against the actual Claude Code session transcript, then spawns a subagent on a different model tier to flag weak evidence, skipped verification, and risky choices. - Use Case: During a multi-week migration run by an autonomous agent, log each fork, revert, and verification result to decisions.tsv, then commit it with the PR so reviewers can follow the evidence trail. ## Quick Start Ask the agent to keep a show-me-your-work decision log for this task and audit it against the transcript before handing back.

Frequently Asked Questions about show-me-your-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep an audit trail for autonomous AI agent work?▼

Keep a single TSV decision log with one row per decision recording timestamp, phase, decision, rationale, evidence pointer, and result. Append rows at decision points and checkpoints using the log.sh helper, then audit the log against the session transcript before handing back.

What format works best for a decision log reviewers can read?▼

TSV works well because GitHub renders it as a sortable table, spreadsheets open it directly, and terminal tools like column display it cleanly. Each row stays single-line with evidence as a pointer such as a commit SHA or file:line, never prose.

Should the decision log be committed to git?▼

By default the log stays local as a working artifact, kept at decisions.tsv or under .audit/ and left out of git. Commit it only when the work is ambitious enough that a reviewer needs the trail to trust the result, such as a large migration.

Why does the logging script prefix cells starting with = or +?▼

Cells beginning with =, +, -, or @ are prefixed with a single quote so spreadsheet applications do not execute them as formulas. This protects reviewers opening logs containing attacker-controlled text like PR titles or generated filenames.

Can the agent review its own decision log?▼

Self-review is not accepted as sufficient. The skill requires spawning a subagent on a different model tier to scan the trail and transcript for weak evidence, skipped verification, and risky choices, then report flags in an Attention section.