Menu
Start tracked work the right way: search first, restore task context, check dependencies, then mark the task in progress.
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
Close Trekker work cleanly by reviewing context, adding a summary comment, marking the task complete, and surfacing the next ready item.
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 | start-task |
| description | Start tracked work the right way: search first, restore task context, check dependencies, then mark the task in progress. |
Use this skill when the user wants to begin working on a Trekker task.
trekker search "keyword-from-task"
trekker task show TREK-12
trekker history --entity TREK-12
trekker comment list TREK-12
trekker dep list TREK-12
trekker task update TREK-12 -s in_progress
After starting the task, summarize:
If the task id is not known, inspect current in_progress and ready tasks before choosing one.