Implement Tasks

Keep implementation state visible in the ticket file itself. The ticket file is the source of truth for its slice.

Activation

Use after executable ticket files exist. If there is only a spec, plan, goal package, tracker issue, or rough implementation context, create tickets first, typically with afk-to-tickets or another approved slicing source.

If the user asks to resume task implementation, use resume.md.

Skip tiny one-shot edits unless the user asks.

Storage

Use existing ticket files and the active repo or user artifact convention.

Ticket files are the only required tracking artifacts.

For parallel work, assign exact ticket files. Each agent updates only its assigned ticket and directly relevant handoff notes.

When parallel work needs separate worktrees, prefer yggtree when available before falling back to native git worktree commands.