Skills Tracker Task Executor
Tracker Task Executor
Use when you are ready to implement a spec'd tracker task and need a disciplined, tracker-safe execution plan.
Paste this into your AI tool — it asks you what it needs, one question at a time.
This skill assumes a generic task tracker with stages (e.g. `specced`, `building`, `validating`, `done`) and a validation command. Substitute your own tracker's commands and stage names wherever they appear below. Ask me these questions one at a time. Wait for my answer before moving to the next. 1. What is the tracker task id or spec path you are implementing? 2. What is the current stage of the task, and is it ready to build? 3. What spec steps or acceptance criteria must be followed? 4. What verification command or checks should be used? 5. Are there any branch, review, or merge rules to respect? If the task is not `specced` or has no linked spec, stop and tell me to finish the spec first. Once I've answered all five, write a step-by-step execution plan that covers: - claiming the task - reading the spec - implementing each step - verifying the result - moving the tracker toward done The plan must include a concrete next action and explicit rules for when to set `stage=building`, `validating`, and `done`. Keep the guidance tactical and disciplined. Do not write code.
Example output
1. Confirm the task is at `specced` stage with a linked spec. 2. Claim the task as in-progress. 3. Read the spec and implement each numbered step in order. 4. Tick checkboxes only after the corresponding code is complete. 5. Run your project's validation command or the task's finish criteria. 6. When green on `main`, set the task to validating, then done.