askit-build-workflowlisted

# askit-build-workflow ## Purpose Author a plugin's workflows: ordered arcs that chain multiple skills toward an outcome (Standard sec 3.4). Two modes: `create` authors `_workflows/<name>.md` (steps, inputs/outputs handed between steps, exit criteria); `improve` resolves findings. Authoring depth is in [references/authoring-workflows.md](references/authoring-workflows.md). Follows the shared builder contract ([../../docs/reference/builder-pattern.md](../../docs/reference/builder-pattern.md)). ## When to use When the user asks to author, scaffold, or improve a workflow, or to formalize a recurring multi-skill sequence into an ordered arc. ## create mode 1. Identify the recurring arc: the ordered skills, what is handed between steps, and the exit criteria. Skip the interview if in context. 2. Author `_workflows/<name>.md` (copy `templates/workflow.md`): frontmatter `steps` (each naming the skill it invokes) plus a body describing the handoffs and exit criteria. 3. Every referenced skill MUST exist (S5). Every chaining step MUST be permitted by the chain contract (sec 3.4); use `askit-build-chain-contract` to add the permission if needed. 4. A workflow SHOULD declare which agent targets it supports. 5. Evaluate (`node scripts/evaluate.mjs . --json`) until S5 is clean. ## improve mode 1. Run evaluate and read findings. 2. For an S5 finding (a step references a skill not on disk), fix the skill name or create the skill. Tighten the handoffs and exit criteria. 3. Re-run to conf