Implement Tickets

Keep implementation state visible in the selected tracking home. The tracking home is the source of truth for its slice.

Activation

Require an executable local or remote ticket. If none was provided or found, recommend afk-to-tickets or another approved slicing source and stop.

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

Skip tiny one-shot edits unless the user asks.

Tracking Home

Resolve the ticket identifier before implementation.

• For a local ticket file, use that file as the tracking home and continue with the existing workflow.
• For a remote ticket, ask whether to create a local Markdown counterpart and track implementation locally, or keep implementation tracking in the remote source through an available remote mechanism.

When remote tracking is chosen, inspect the available mechanism and agree with the user where the ticket status, execution evidence, review state, findings, and handoff notes will live. Use that location as the tracking home.

Keep local tracking artifacts outside agent-created commits unless the user or repository convention explicitly opts them in. Remote tracking remains external to Git unless a local counterpart is selected.