capture-workflowlisted

# Capture Workflow Convert a proven task into the smallest repo-owned reusable asset that can reproduce its outcome. Capture evidence and decisions, not the accidental state of the current shell or conversation. ## Safety - Reconstruct the workflow from current repository evidence, commands, outputs, and user decisions. Do not treat every exploratory step or failed attempt as part of the reusable path. - Never hardcode secrets, tokens, accounts, absolute machine paths, transient ports, cached sessions, customer data, or current uncommitted state. - Preserve explicit gates for deployments, purchases, messages, deletion, production writes, OAuth consent, and other consequential side effects. - Do not generalize beyond observed variability. One stable parameter is better than a framework of speculative options. - Follow repository ownership: maintained automation belongs in the documented tooling location; one-off personal helpers remain local or gitignored. ## Workflow 1. State the proven outcome and collect the exact successful evidence: inputs, commands/actions, outputs, decisions, prerequisites, credentials source, side effects, cleanup, and failure recovery. 2. Separate the stable sequence from variable values and incidental exploration. Record why each retained step exists. 3. Search for an existing script, task, template, test, runbook, or skill to extend before creating another entry point. 4. Choose the smallest durable form: - a command or script for determinis