القائمة
Plan multi-step work in Trekker before implementation. Use epics, tasks, and dependencies so work survives session resets.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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.
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 | planning |
| description | Plan multi-step work in Trekker before implementation. Use epics, tasks, and dependencies so work survives session resets. |
Use this skill for work that spans multiple files, requires sequencing, or is likely to continue across sessions.
update_plan only after Trekker is accurate.trekker search "authentication"
trekker epic create -t "User Authentication" -d "JWT login, registration, and session handling"
trekker task create -t "Design auth schema" -d "Users, refresh tokens, and password reset entities" -e EPIC-1 -p 0
trekker task create -t "Implement login endpoint" -d "Credential validation and token issuance" -e EPIC-1 -p 1
trekker dep add TREK-2 TREK-1
Each task description should answer three things:
Before starting a planned task:
trekker dep list TREK-2
trekker task show TREK-2
trekker comment list TREK-2
trekker task update TREK-2 -s in_progress
If the user only wants brainstorming and not committed tracking yet, do not create Trekker items without approval.