show-me-your-work
Keep an auditable decision trail for long-running, autonomous, delegated, or multi-phase work. Use whenever a human will review the result after stepping away and needs decisions, evidence, pivots, and verification without rereading the full transcript.
- License 许可
- MIT
- 所属仓库
- caezium/skills
- 最近更新
- 2026-08-24
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- show-me-your-work
- description
- Keep an auditable decision trail for long-running, autonomous, delegated, or multi-phase work. Use whenever a human will review the result after stepping away and needs decisions, evidence, pivots, and verification without rereading the full transcript.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档references/decision-log-template.tsv38 B
- 脚本scripts/log.sh1.2 KB
03 SKILL.md 正文
Show me your work
Maintain one append-only TSV decision log so a reviewer can reconstruct what was decided, why, and on what evidence. Log decisions and checkpoints, not keystrokes.
Start the trail
Copy references/decision-log-template.tsv to decisions.tsv, or use .audit/<task-slug>.tsv when several efforts share a worktree. Keep it local by default. Commit it only when a reviewer needs the trail to trust a large migration, port, or unattended run.
Append safely with:
scripts/log.sh <logfile> <phase> <decision> <why> <evidence> <result>
The helper timestamps the row, preserves single-line cells, and neutralizes spreadsheet formulas. Resolve scripts/log.sh relative to this installed skill.
| Column | Contract |
|---|---|
ts |
UTC ISO-8601 timestamp |
phase |
Current phase or workstream |
decision |
One concrete choice or checkpoint |
why |
Plain-language reason |
evidence |
A resolvable pointer: commit, file:line, test output, trace, screenshot, or artifact path |
result |
Observable state such as tests green, reverted, INCONCLUSIVE, or open |
Write one row for a fork chosen, a verified unit completed, a pivot/revert, a blocker, or a gate changing state. For iterative runs, write one row per meaningful iteration. A wrong call gets a later superseding row; never rewrite history.
Harness availability
| Need | Native path | Fallback |
|---|---|---|
| Locate this run's transcript | Use the active transcript path supplied by Cursor, Claude Code, Codex, or T3 | Match workspace metadata and opening prompt in that harness's scoped history; otherwise use the visible conversation |
| Fresh-eye audit | Use an authorized subagent; request a different model family only when the harness exposes valid model selection | Use an independent inherited-model reviewer; if delegation is unavailable, perform the audit yourself and disclose that limitation |
| Evidence | Use repository/runtime/browser/connector tools available in the harness | Mark the row INCONCLUSIVE; never manufacture a pointer |
Only delegate when the current user and system policy permit it.
End-of-run audit
- Walk the log against the active transcript or visible conversation.
- Confirm every row maps to a real action and every evidence pointer resolves.
- Add omitted forks, abandoned approaches, and verification failures that shaped the result.
- Remove padding; keep only rows a reviewer would audit.
- Ask the fresh-eye reviewer to flag weak evidence, skipped verification, risky choices, and gaps. The reviewer inspects; it does not redo or edit the work.
End the handoff with an Attention section naming the reviewer configuration and its flags. No flags is valid. If model diversity or delegation was unavailable, say so plainly.
<!-- Adapted from poteto/pstack show-me-your-work, MIT License, Lauren Tan, cursor/plugins@51a96e0. -->
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available evidence sources, searches each relevant category, and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
week-prep
Generate a briefing with calendar, tasks, and attention flags. Use for "week prep", "briefing", or "what's on this week".