Capstone: ship your bench tool

Build-along · ~20 min at your own keyboard

Everything converges here: pick one real recurring need in your business, assemble the pieces you've built across this track, directive, scripts, verification, schedule or webhook, logging. Into a tool that a working agent could actually use tomorrow. You don't graduate into a certificate. You graduate with a shipped tool that runs whether you show up or not.

Your starter: One-page tool doc

Template

Make it yours: Fill it for the tool you actually built and ran. Delete any line that does not apply, and add the one step future-you will forget.

TOOL: [name]
WHAT IT DOES: [one sentence: input -> output]
TRIGGER: [the schedule, or the event that starts it, e.g. a run-complete notification]
INPUTS: [the exports or files it reads, and where they live]
STEPS:
  1. [ ]
  2. [ ]
  3. [ ]
OUTPUT: [what it makes] -> LANDS IN: [folder or sheet]
CHECKS IT RUNS: [the verify step, and what it marks VERIFIED / FAILED]
CANNOT ASSESS: [e.g. whether a result is real, whether the run worked] - these stay with a person.
LOG: [where each run writes a line, with a timestamp]
WHEN IT FAILS: [what a FAIL line looks like, and who reads it]
REVIEW: [who reviews the output, and how long it takes]
TO FIX IT: [where the scripts live, and the one thing future-you will forget]

EVIDENCE
Runs: [count and date range, with log lines]
Output sample: [paste one]
Failure it survived: [what broke, what caught it, what you changed]
Demo: [who you showed it to, and when]

The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.

Do this

0/4

Share what happened

Paste your one-page tool doc (trimmed) plus the evidence set: log lines, an output sample, who you demoed it to, and any failure it recovered from.