If you were not explicitly told to run implement, stop and say so instead of continuing.

If you are not the implementation agent, delegate the entire job to that agent in the assigned worktree. Include the original ticket/spec, base, size, brief, files, scratch/report path and fleet result contract verbatim; do not implement or review in the parent. If the agent cannot be found or launched, report blocked (reviewed=no for fleet) rather than silently doing the work yourself. The agent loads this skill and follows the worker instructions below; this delegation does not repeat inside it. Wait for its result and preserve the fleet one-line output unchanged.

Implement the work described by the user in the spec or tickets.

For a large or multi-part ticket, split it into smaller /implement runs by logical slice, or checkpoint with /compact between major phases (after planning, after test-writing, before the final review). A single long session re-sends its whole growing history on every turn, so cost compounds with session length far faster than with the same work split into smaller ones.

Run test suites expected to take over about 30 seconds in the background, end the turn and wait for the completion notification. Never poll with sleep or Monitor loops: each poll re-sends the whole session.