Menu
Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Start tracked work the right way: search first, restore task context, check dependencies, then mark the task in progress.
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.
| name | smart-query |
| description | Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work. |
Use this skill when the user asks questions about the state of work rather than requesting an immediate code change.
trekker task list --status in_progresstrekker readytrekker history --limit 10trekker dep list TREK-12trekker search "auth" then trekker search "login"trekker search for thematic discovery.task list, ready, and history for structural questions.comment list and task show when the user needs the detailed context on one task.