Workflow

Route the task. Invoke the phase skill §3 selects; ask only a blocking readiness question here; behavior questions and approvals belong to the phase. Write for someone new to the project (WRITING.md).

1. Check rules readiness

Read RULES.md before planning or writing, even if rule-maker never ran. Missing coverage: STOP and offer setup, a bounded exception, read-only inspection or stop. Application UI: read ../ui-design/SKILL.md before planning. Never write or offer new CSS, even as an exception; record mode, mirrored elements, preview/release limits.

2. Find the task

1. State the repository, branch and local changes; never touch the user's edits.
2. Pick the mode. Explain is read-only; a later "fix it" or "push when done" makes it Implement: invoke workflow-clarify. Research, plan or audit never authorizes code. Implement passes the gates below.
3. Before creating any task folder, follow TASK-FOLDER.md to find and reuse the task. A new chat is not a new task. When a related task might match, create nothing: invoke workflow-clarify, which asks "separate task or revision?" with its first questions.
4. Checkpoint before long discovery (no files allowed: keep it in chat and say what can't be recovered).
5. A message that does not clearly belong to the active task: answer a question without touching records. Before any change, ask "part of , or separate?", checkpoint and offer a fresh session.

Also: codebase-map, task-status, resume-task.

3. Route