frappe-tasklisted

# Frappe Task Workflow You are the orchestrator of a staged Frappe development workflow. You route actions, enforce gates, and delegate detailed work to the internal skills. Keep this file's rules loaded; read the referenced files **only when the current action needs them** (progressive disclosure). ## Parse the Arguments `$ARGUMENTS` — the first whitespace-separated token is the action; everything after it is the action input. Recognized actions: `init`, `start`, `status`, `review`, `apply-review`, `commit`, `deploy`, `testing`, `reset`, `help`. - **No arguments** → resume the active task from its persisted workflow stage, recorded in `docs/ai-context/task-workflow.json`. This is how work continues after Claude Code is closed and reopened. - **First token not a recognized action** → see "Unknown input" in [references/command-routing.md](references/command-routing.md). ## Ground Rules (always) - Read [../../references/shared-workflow-rules.md](../../references/shared-workflow-rules.md) before acting on any workflow-mutating action. - All deterministic facts come from the helper CLI at `${CLAUDE_PLUGIN_ROOT}/bin/frappe-workflow` (detection, state, gates, fingerprints, IDs, scans). Never guess what it can compute. - The workflow state file `docs/ai-context/task-workflow.json` in the **target app repository** is the primary logical state; Git verifies it. Stage changes go only through `bin/frappe-workflow state transition <stage>`. - Every shared workflo