improve-workflow

Files (2)

• SKILL.md
• LICENSE.txt · references/

SKILL.md (first lines)

# Improve a workflow

1. Review the relevant run's goals, decisions, results, and available execution
   records. Distinguish a process failure from missing capability or unclear scope.
2. Examine judgment, tooling, and plausible alternative approaches. Independent
   perspectives can help when available; label the evidence actually used.
3. For each proposed improvement, cite the observed failure or wasted effort,
   explain the causal link, and name the smallest change that would help.
4. Prefer structural enforcement for repeatable mistakes. Reserve instructions
   for judgment that cannot be encoded reliably; avoid adding rules for speculation.
5. Classify proposals as adopt, reject, or defer with reasons. Apply and verify
   changes already requested; a retrospective-only request returns proposals.

Done when useful improvements have evidence, a disposition, and a way to evaluate
whether they worked. Publishing issues or changing unrelated workflows requires
that scope to be part of the task.

Adapted from pstack; [license and attribution](references/LICENSE.txt).

From wcygan/agent-skills, MIT.

More from wcygan/agent-skills