build-ticket
Build ticket
Implement the work described by a ticket, and stop with a result the user can review: built, checked, reflected on, reviewed, independently verified, and with evidence for each done check. Work unattended by default. Stop early only where this skill says to.
If the user asks to be in the loop (e.g. "with me", "let's collaborate"), pause and ask them instead wherever this skill says to pick a default, make a significant decision, or carry a question into the report. Continue with their answer.
1. Load the ticket
If the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.
Read the ticket in full, and the spec or design document its context points to. Claim the ticket in the tracker, if the tracker supports that.