commit 919fb092c0d7390b4cdc43b21d45faf3d9e3bb4b
Author: Coder Agent <coder@agents.omni>
Date: Thu Feb 19 23:41:00 2026
skills/coder: require showboat-style proof-of-work evidence
Task-Id: t-645
diff --git a/skills/coder.md b/skills/coder.md
index eaa70305..60160867 100644
--- a/skills/coder.md
+++ b/skills/coder.md
@@ -16,6 +16,7 @@ Before coding, also load:
4. **Implement** - Make minimal, focused changes
5. **Verify** - Run `bild <namespace>` to confirm compilation
6. **Fix** - If build fails, fix errors and re-verify
+7. **Capture evidence** - Produce a mini proof-of-work artifact before handoff
## Guidelines
@@ -80,10 +81,35 @@ run_bash rm -rf old-ts-directory/
- Add type hints to function signatures
- Use `# : dep <package>` comments for dependencies
+## Evidence Artifact (Showboat-style)
+
+Before declaring implementation complete, create a short, structured proof-of-work artifact that shows what actually happened.
+
+Required sections:
+
+- **Scope** - task id, namespace, and files changed
+- **Commands run** - exact verification/build/test commands
+- **Results** - key output snippets (pass/fail, artifact paths, notable warnings)
+- **Checks performed** - what behavior was manually/automatically validated
+- **Open issues** - anything incomplete, flaky, or needing follow-up
+
+Preferred format and location:
+
+- Commit a markdown artifact in `_/tmp/proof-<task-id>.md` while working
+- Before handoff, either:
+ - move a cleaned version into a durable location committed with the code, or
+ - paste the artifact (or concise equivalent) as a `task comment`
+
+Minimum quality bar:
+
+- Evidence must be specific enough that another person can replay verification
+- Do not claim success without command evidence
+- If verification fails, include the failure and next step instead of hiding it
+
## Task Handoff
If this work is tied to a `task` item:
-- move task to review when coding is done:
+- move task to review when coding + evidence are done:
```bash
task update <task-id> review --json