workflow

Workflow Templates

Run one of six opinionated workflow templates. Each template fixes an ordered list of phases and the agents to dispatch, so common task types follow the same proven path every time.

Target

$ARGUMENTS

Hard Rules

1. Run only the template named in Target. If Target names none, or the first word matches no template, do not guess — follow Step 3 or Step 4 and stop until the user answers.
2. Execute a template's phases in listed order. A phase begins only after the previous phase's done-when condition holds.
3. Report status after every phase, and emit the Workflow Report only when every executed phase has a status row.
4. On a failed gate or retry, escalate effort to max for the next attempt and state that you are doing so — never silently re-run at the same effort.
5. spike produces a report only (no code changes); hotfix applies the minimal fix (no refactoring, no improvements).
6. When consuming security-scanner output, use its exact enums — Severity CRITICAL/WARNING/SUGGESTION, Confidence HIGH/MEDIUM/LOW.
7. For tasks that fit no template, tell the user to use /dev instead of forcing a template.

Steps

1. Read the template name from the first word of Target. Done when: the name equals one of the six templates below, or you route to Step 3/4.
2. Read the task description from the rest of Target. Done when: the task text is captured (empty is allowed — spike and security-audit can run without a description).
3. If Target names no template — list the six templates with their one-line summaries and ask the user to choose. Done when: the user names a template; do not proceed before then.
4. If the first word matches no template — name the single closest template and ask the user to confirm before running it. Done when: the user confirms or picks another; do not proceed before then.
5. Run the matched template's phases (see Templates) in order. At each dispatch point, dispatch the named agent; if that agent is absent from .claude/agents/, perform the phase inline and write "agent unavailable — ran inline" in that phase's Notes. Done when: every phase's done-when condition is met.
6. After each phase, record its status row for the Workflow Report (see Output). Done when: Step 5's final phase done-when holds and every executed phase has a row — only then emit the report.