show-me-your-work

Record decision trails for multi-phase tasks in an append-only TSV log.

2|Updated Apr 3, 2026

Search Tags:#audit #review #log #record #decision-trail #tsv #autonomous-work

Ready to run

npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill show-me-your-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: show-me-your-work
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/show-me-your-work
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill show-me-your-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams keep a reviewable decision trail for long-running or unattended work by recording decisions in a TSV log, enabling traceability and accountability.

Core Features & Use Cases

Append-only TSV logging: Each decision is recorded as a single row in a decisions.tsv file, preserving history.
Evidence-ready entries: Columns include timestamp, phase, decision, why, evidence, and result to support auditing and cross-model reviews.
Auditability & governance: Enables review workflows, cross-model checks, and easier handoffs for multi-phase projects.
Use Case: For autonomous workflows or work reviewed after the fact, reviewers can reconstruct what happened and why.

Quick Start

Create a decisions.tsv in the working directory and append a new row for each decision to maintain an auditable trail.

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 maintain a decision trail for long-running autonomous tasks?▼

An append-only TSV log preserves history by recording each decision as a single row with fields like timestamp, phase, decision, why, evidence, and result, ensuring history cannot be overwritten and reviewers can reconstruct events accurately.

How do I log decisions and evidence for an unattended workflow run?▼

You log decisions for unattended runs by appending rows to a decisions.tsv file, populating columns for phase, decision, why, evidence, and result to create an audit-ready record for post-hoc review.

What is the best way to create an audit-ready record for multi-phase projects?▼

The best way to create an audit-ready record for multi-phase projects is enforcing an append-only TSV logging policy that captures evidence and outcomes, enabling cross-model checks and reproducible governance.

Can I use a TSV log to support reviewer-enabled handoffs in autonomous work?▼

Yes, you can use a TSV log to support reviewer-enabled handoffs by providing a structured, evidence-ready decision trail that allows reviewers to reconstruct exactly what happened and why during the run.

What columns are needed to track a decision trail for reproducibility?▼

To track a decision trail for reproducibility, you need columns including timestamp, phase, decision, why, evidence, and result, structured within an append-only TSV file to enforce governance.

Why does an append-only policy matter for autonomous work logs?▼

An append-only policy matters for autonomous work logs because it prevents the modification of historical entries, ensuring that the decision trail remains a trustworthy, audit-ready artifact for accountability.