# Show Me Your Work

> Keep a compact decision trail for long-running or unattended work. Use for $show-me-your-work when a reviewer needs evidence for important choices and verification.

- Skill: `vaibtan/show-me-your-work` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add vaibtan/show-me-your-work`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vaibtan/show-me-your-work/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Vaibtan (https://skillmd.com/u/vaibtan)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/vaibtan/show-me-your-work

---


# Show me your work

Keep a TSV decision log for consequential choices, not a transcript of routine commands.

Use this header:

```text
ts\tphase\tdecision\twhy\tevidence\tresult
```

Record a row when choosing between real alternatives, changing course after evidence, accepting or rejecting delegated work, crossing a phase boundary, or deciding that verification is sufficient. Use `scripts/log.ps1` on Windows or `scripts/log.sh` in a POSIX shell.

Keep evidence as a stable file, line, commit, command result, metric, or URL. Sanitize tabs and newlines. Prefix spreadsheet-formula characters so untrusted evidence cannot execute when the TSV opens.

Before handoff, compare the log with the current task's actual tool results and repository state. Correct stale rows. Report the log path and whether it is intentionally local or part of the requested deliverable. Do not commit it unless the user or repository workflow wants an auditable trail in version control.