To Tasks

Break a plan into independently-grabbable AFK checkpoint packets using vertical slices (tracer bullets).

AFK tasks are local checkpoint packets by default. They may be mirrored to an external tracker when requested, but the local tracking files are the AFK execution source of truth unless the user chooses another destination.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.

Use any available source artifact: plan, spec, goal package, tracker issue, handoff, prototype notes, or rough feature context. The gap this skill fills is executable implementation planning.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Task titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."