show-me-your-worklisted

# Show me your work Keep one canonical decision log so a reviewer can reconstruct what changed, why, what evidence supported it, and what happened without reading the complete conversation. ## Format Resolve `<skill-dir>` as the directory containing this loaded `SKILL.md`, then copy `<skill-dir>/references/decision-log-template.tsv`. Use one single-line row per decision with these columns: - `ts`: UTC ISO 8601 timestamp. - `phase`: Phase or workstream. - `decision`: Concrete choice or checkpoint. - `why`: Plain-language reason. - `evidence`: Commit, pull request, `file:line`, artifact, trace, or screenshot. - `result`: Observable result such as `tests green`, `reverted`, `open`, or `INCONCLUSIVE`. Append rows with: ```bash node "<skill-dir>/scripts/log.mjs" <logfile> <phase> <decision> <why> <evidence> <result> ``` The helper creates the header, removes tabs and newlines from cells, and guards spreadsheet formula prefixes. ## What to log The coordinator is the sole log writer. Delegates return proposed rows and evidence to the coordinator instead of appending concurrently. Log forks, pivots, completed units with verification, reverts, blockers, and gates. For repeated work, log one row per meaningful iteration. Skip routine commands and narration. Keep the log local at `decisions.tsv` or `.audit/<task>.tsv` by default. Commit it only when the work is large enough that the review trail is part of the deliverable, such as a major migration or cross-language port. #