Inspect .agents/state/INDEX.md plus unfinished task summaries first; do not bind, select, or create any task state file yet.
Resolve workflow context before calling $ac-memory:

identify task type (feat / fix / refactor / chore / docs)
determine whether this is a new task or continue
check whether the request is a pure copy-edit exempted by AGENTS; if yes, do not enter workflow state handling
treat active / blocked as resumable only when the user explicitly indicates continue
if unfinished task-state files exist but the user intent is a new task, create a new task instead of auto-resuming
if the user says continue, first try explicit task-id or exact TASK_TITLE
if exact resolution fails, build a small candidate set from stable substring / keyword matches against unfinished TASK_TITLE
if the candidate set has one clear match, surface it and let the user confirm before binding
if the candidate set has multiple matches, list the candidates and require user confirmation before binding

Call $ac-memory only after the target task is resolved, so .agents/state/INDEX.md and the selected or newly created task state file are valid and ready for routing.
Determine route using the AGENTS risk score:

single for low-risk work: run minimal ac-plan then ac-execute responsibilities in the same thread, do not edit files before the Contract is written and PLAN_FROZEN=true, and after execution perform summary closeout by writing CURRENT_ROLE: single and WORKFLOW_STATUS: completed
single + reviewer when review must be forced: complete the same collapsed planning/execution path, hand off to $ac-review, then reclaim control after a pass for final summary closeout
planner -> executor -> reviewer for multi-file, high-risk, or workflow-rule changes; reclaim control after $ac-review passes for final summary closeout
for low-risk work that is not AGENTS copy-edit exempt, prefer single unless workflow routing semantics, AGENTS core rules, review conclusions, or shared terminology across multiple workflow assets also change

Echo a concise state line such as [STATE] <task-id> | <role> | <status> | 已检查/已更新 when helpful, then emit the standard workflow progress display and keep it aligned with the real phase in the active task state file. 5.5. When running a low-risk non-copy-edit task, the caller may echo a concise line such as 当前按轻量 workflow 执行（简版 Contract、聚合验证、按需 review）; the workflow progress display may be shortened as long as the active task state remains accurate.

ac-workflow