save-workflowlisted

# *save-workflow — Capture the Workflow We Just Ran ## Purpose Workflows (ordered multi-step procedures) evaporate faster than patterns. This skill captures the workflow just executed in the current conversation — goal, ordered steps with the exact commands used, gotchas — into a structured, reusable local file at `.claude/skills/local/<workflow-name>.md`, while step order and command details are still hot in context. ## Boundary: workflow capture vs pattern capture | Command | Captures | Shape of output | |---------|----------|-----------------| | `*save-workflow` (this skill) | A WORKFLOW: an ordered multi-step procedure with concrete commands, preconditions, and outputs | Replayable step list | | `*save-skill` (NOT yet implemented; route there only if present) | A PATTERN: a reusable judgment rule or heuristic, not step-ordered | Rule + rationale | If the user wants to save a rule/insight rather than a procedure, say so and point at `*save-skill` (if present) instead of forcing it into workflow shape. ## When to use — and when to refuse - Use at the end of (or right after) a conversation segment where a multi-step procedure was actually performed: commands run, files produced, a repeatable sequence completed. - **MUST refuse honestly**: if the conversation contains no discernible executed workflow (pure discussion, brainstorming, a single trivial command), say so explicitly and stop. Do NOT fabricate steps that were never performed. ## The 5-Step Capture Fl