implement-ticket

name	implement-ticket
description	Execute one ticket of a product-task spec.
disable-model-invocation	true

Implement ticket

Execute a single ticket of a task, on the already-checked-out feature branch. It runs once per session, for one ticket: a fresh session picks up the ticket, does it, and either commits it or hands off at a human touchpoint. The ticket is the unit of a run and of a commit — the ticket model, and the branch/status conventions this skill relies on, are in ../../tasks/concepts.md and ../../tasks/structure.md.

Invocation

/implement-ticket <NN> — the ticket number is always required, and the feature branch is assumed checked out.

Step 1 — Load

Resolve the task folder from the branch (issue-<number>) and read the main spec.md, the target ticket's tickets/NN-<slug>/spec.md, progress.md, questions.md, and .agents/delegation.md. If ticket NN has only a brief.md, it isn't scoped — tell the developer to scope it with a to-tickets run, and stop.

Step 2 — Check runnable

Read the ticket's Blocked by list — the whole runnable test lives there, so check nothing else. Resolve each entry by kind: a T<NN> entry must be checked in progress.md; a Q<NN> entry must be resolved or waived in questions.md. If every entry clears, proceed; otherwise report exactly which blockers are open and stop.

Step 3 — Execute

Start at the first unchecked leaf and work in order, checking each box as it completes — resuming after a human touchpoint skips the leaves already checked. Stop at the first unchecked [human] leaf and hand off (Step 5).

Step 4 — Verify

Run every code-quality check the repo defines (per .agents/rules/code-quality.md) plus the relevant unit tests. Intentional scaffold TODOs may keep ESLint red the way the add-new-page skill documents — say so explicitly rather than chasing green. Then walk the ticket's acceptance criteria and confirm each agent-checkable one holds. A (human) criterion is not yours to judge — it is a touchpoint Step 5 stops for.

Step 5 — Close

Key the close to whether the ticket has any human touchpoint — a [human] leaf, or a (human) acceptance criterion:

• No touchpoint → fully autonomous. Check the ticket's box in progress.md, then commit — the box tick folded into the commit so the worktree is clean after. A plain descriptive subject, the repo's Co-Authored-By trailer, and no #issue reference (the PR's Resolves #N already links it; a commit that names the issue spams its timeline). Done.
• Any touchpoint → stop and hand off. Stop at the first unchecked [human] leaf; or, when the leaves are all [agent] but a (human) criterion remains, after implementing them and before committing. Say what the developer must do, link the Figma node, and point at the scaffold's TODO (design): markers. The developer does the work; for a [human] leaf they check its box and ask the session to continue — it resumes from the next unchecked leaf (Step 3), never by re-invoking the skill. Once every leaf is done, the developer commits and checks the progress.md box at their commit.