Menu
Close Trekker work cleanly by reviewing context, adding a summary comment, marking the task complete, and surfacing the next ready item.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start tracked work the right way: search first, restore task context, check dependencies, then mark the task in progress.
Check Trekker for related tasks before creating a new one so work is extended instead of duplicated.
Suggest or manage Trekker tracking when the user talks about bugs, features, backlog items, or work that should survive this session.
Plan multi-step work in Trekker before implementation. Use epics, tasks, and dependencies so work survives session resets.
Search Trekker first to recover context before creating, starting, or updating tracked work.
Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.
| name | complete-task |
| description | Close Trekker work cleanly by reviewing context, adding a summary comment, marking the task complete, and surfacing the next ready item. |
Never mark a task complete without a summary comment.
trekker history --entity TREK-12
trekker comment add TREK-12 -a "codex" -c "Summary: implemented the retry guard in src/service.ts and removed the duplicate fallback path."
trekker task update TREK-12 -s completed
trekker ready
If the user is finishing only part of the task, leave a Checkpoint: comment instead of completing it.