القائمة
Print rich task details for the current Hermes task context: status file path, primary tracker URL, machine name, session id, transcript path, zellij session/link, and a short task recap.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Start a detached zellij session for a tracker-linked or natural-language task, and launch Codex or Claude as the default shell with an initial `$start-new-task ...` handoff prompt.
Initialize a new task folder with status.md, user_inputs/initial.md, user_inputs/input_artifacts/, task-progress-artifacts/, and task-progress-artifacts/scratchpad/. Supports GitHub issue URL inputs, Linear issue URL inputs, default Linear issue creation for trackerless starts, tracker-informed slugs, and machine/zellij metadata capture with optional live-session issue block sync.
Initialize a new task folder with status.md, user_inputs/initial.md, user_inputs/input_artifacts/, task-progress-artifacts/, and task-progress-artifacts/scratchpad/. Supports GitHub issue URL inputs, Linear issue URL inputs, default Linear issue creation for trackerless starts, tracker-informed slugs, and machine/zellij metadata capture with optional live-session issue block sync.
Rename Codex app thread labels and titles in local Codex state. Use when a user asks to rename, retitle, relabel, or make a Codex chat/thread easier to find in the Codex app sidebar or thread list, especially when the visible label still shows the first prompt such as "$start-new-task ZON-218".
Create compact Codex `/goal` plan files that require an implementation loop with Oracle GPT-5.5 Pro review between iterations. Use when the user wants a goal plan that explicitly sequences implementation, strongest-model Oracle review, rework from Oracle findings, repeated review until no material changes remain, and final verification.
Create a Linear ticket and immediately launch a detached zellij/Codex worker session for it. Use when the user asks to "create a ticket and start a session", "make a Linear task and $start-zellij-session-for-task", spin up a side worker for a new task, or repeat the common parent-orchestrator flow of drafting a scoped issue, linking it to a parent lane, and starting `$start-new-task ISSUE-ID`.
| name | get-task-details |
| description | Print rich task details for the current Hermes task context: status file path, primary tracker URL, machine name, session id, transcript path, zellij session/link, and a short task recap. |
Resolve task status path and metadata in one read-only command.
/get-task-details [task-slug]
python ~/pro/botfiles/codex/skills/_shared/task_status/scripts/get_task_details.py \
--status-file "<optional-explicit-status-file>" \
--task-dir "<optional-explicit-task-dir>" \
--project-root "<project-root>" \
--task-slug "<optional-slug>"
Default call with no task-slug:
Primary task output should include:
If no task is found for the current session, print a clear message and suggest creating or adopting a tracked task.
status.md path, pass it directly.~/pro/botfiles/docs/task-status-tracker-contract.md.task-slug only when you intentionally want cross-session lookup.HERMES_SESSION_TITLE or SESSION_TITLE before invoking get_task_details.py. The shared helper can then resolve the real Hermes session ID from ~/.hermes/state.db, which mirrors the session identity a human can inspect via /title.sync_task_metadata.py with the real Hermes session ID so current-task pointer lookup and get-task-details align for future calls.