菜单
Resume an interrupted tracked task in Hermes by resolving the existing task home from a task slug, tracker ref, session name, task dir, or status file, then syncing task metadata to the current session before continuing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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 | continue-task |
| description | Resume an interrupted tracked task in Hermes by resolving the existing task home from a task slug, tracker ref, session name, task dir, or status file, then syncing task metadata to the current session before continuing. |
Use this when the current Hermes session needs to take over work that already has a tracked task folder and status file.
Prefer this over starting a new task when a matching tracked task already exists.
/continue-task <task slug|tracker ref|session name>
Lower-level overrides:
/continue-task --task-dir <task-dir>
/continue-task --status-file <status-file>
/continue-task --zellij-session <session-name>
Resolve and inspect the task home first:
get-cross-session-context --project-root "<project-root>" <target> --include-transcript-tail 6
Explicit overrides when needed:
get-cross-session-context --project-root "<project-root>" --task-dir "<task-dir>" --include-transcript-tail 6
get-cross-session-context --project-root "<project-root>" --status-file "<status-file>" --include-transcript-tail 6
get-cross-session-context --project-root "<project-root>" --zellij-session "<session-name>" --include-transcript-tail 6
Adopt the resolved task into the current session:
python ~/pro/botfiles/codex/skills/_shared/task_status/scripts/sync_task_metadata.py \
--status-file "<resolved-status-file>" \
--tracker-url "<resolved-tracker-url-if-any>" \
--github-issue-url "<resolved-github-issue-if-any>"
status.md first. Treat task metadata and local status recap as the source of truth.sync_task_metadata.py against the resolved status file.cross-session-context is the read-only inspection tool. continue-task is for actual takeover.get-task-details is the read-only recap tool once the current session owns the task.