Implement

Activation: the developer requests a specific ticket or a clearly scoped direct change. Choose one ready, unblocked ticket; if the reference is ambiguous, resolve it before editing. A direct small task can bypass ticketing when authorized.

Read the ticket when one exists, only relevant sections of approved product/design/technical documents, current code and callers, and applicable repository instructions. Mark an existing ticket In progress. Implement one complete vertical slice using existing patterns. Load only specialists that the slice requires: frontend-engineering, api-design, tdd, diagnosing-bugs, browser-testing, or security-review. A specialist advises the current task; none opens the next stage.

Run targeted tests/typechecks during the work and the relevant full suite before completion. On failure, use the red output to diagnose; do not mark the ticket done while checks fail. Review the diff against the spec and repo standards using code-review. Record commands, results, and any unverified criterion under ticket verification; mark Done only when acceptance criteria and checks pass. When a ticket becomes Done, mark dependent tickets Ready only if all their blockers are Done. Report changed behavior, evidence, and limitations.

Do not implement another ticket, silently revise approved specs, or commit, push, or deploy without authorization. If the ticket contradicts an approved owner document, stop that branch and request a decision. If there is no ticket, report verification in the response rather than inventing one.

Sources: Matt Pocock's implement and Addy Osmani's incremental implementation; upstream automatic commit was removed.