To Tasks

Break a plan into sequential tracer-bullet task files, checked into .tasks/.

Tasks are always sequential — no parallel work. Each task is worked one at a time via /next-task, with the context cleared between tasks to keep the agent from getting overwhelmed.

Only one feature at a time — .tasks/ holds the current feature's plan and is deleted when the feature is done.

Asking questions

Whenever you put a question to the user — the quiz in step 5, or an ad-hoc question when something is unclear or has drifted (a stale roadmap brief, a plan that conflicts with the code) — ask it and wait for their answer before carrying on.

Drift found in step 2 or 3 is worth a question, but don't ask as you find it: finish grounding the plan, then ask the drift questions alongside step 5's quiz.

Process

1. Check for an existing plan

If .tasks/ already exists and contains task files, stop and tell the user. Either they need to finish the current feature (via /next-task) or explicitly discard it before starting a new plan.