Work

Deliver one verified slice at a time, following repository conventions, with evidence proportionate to the change.

Phase 1: Select the task

• An explicit plan path selects that plan. Read it and its referenced source. If the path is missing, stop; do not pick another plan.
• A description selects direct work, even when old plans exist.
• A bare invocation may select the only unfinished ready or in-progress direct plan. Ask if several are plausible. Orchestrated plans resume through flow-orchestrate.
• A coordinator's task brief selects delegated mode. Read references/delegated-mode.md before editing.

Current user instructions override an older plan. Reconcile source drift before editing. A ready task has observable acceptance and satisfied dependencies. Report or verify already completed work instead of redoing it.

Phase 2: Ground the implementation

• Read applicable instructions, nearby code and tests, configuration, and pinned dependency versions.
• Documented repository rules (JSDoc, comments, formatting, logging, lint) beat generic preferences.
• Resolve ordinary details from evidence; ask only about consequential missing choices.
• When unsure about an API, check official docs or the installed library source. Do not add a dependency or build chain because a generic example uses one.