task-flow

Begin with exploration of the repository, then grill the owner with the mandatory questions and record answers verbatim in grill.md. Write the product agreement if code changes behavior, create the task, branch, and task folder, then write the plan before any code edit.

A task folder lives at docs/tasks/<branch-name>/ and holds grill.md, plan.md, and progress.md. It is created as a draft before the first edit, gets its number via the task creation command, and is committed to the branch rather than left uncommitted.

The task-flow guard refuses edits to application code until three things exist: a task folder matching the branch name, a plan in it, and a declared state in progress.md. The refusal names the mandatory action of the current state.

The folder is taken apart by the last commit before the PR opens, not after approval. The grill goes to the archive, findings go to the epic plan, and the rest is deleted; opening a PR while the folder exists is refused.

Yes, work begins with an epic and tasks outside one are not taken unless the owner explicitly orders that specific work. Epic tasks are created all at once and linked to the epic card as sub-issues.

Guards judge file presence, edit paths, and declared states, not meaning: they cannot verify grill completeness, plan immutability, or whether texts match what was done. Those aspects are held by the articles and owner review.