ワンクリックでManusで任意のスキルを実行

continue-task

スター28

フォーク0

更新日2026年4月15日 21:45

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 ページを確認してインストールできます。

Manusで実行

ソース

ma08

ma08/botfiles

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Continue Task

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.

Invocation

/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>

Commands

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>"

Process

Resolve the existing task home first.
If resolution is ambiguous, stop and surface the candidates. Do not guess.
Read the resolved status.md first. Treat task metadata and local status recap as the source of truth.
Use only a short transcript tail as fallback for final pre-interruption context.
Adopt the task into the current session by running sync_task_metadata.py against the resolved status file.
If the task home lives in another repo, treat that workspace as canonical before making code changes.
After adoption, update the status file with a short takeover note, refreshed current state, and next step.
If no tracked task home exists, stop and suggest creating one instead of fabricating resume context.

Output Expectations

Confirm the adopted task folder, status file, tracker URL, transcript path, and canonical workspace.
Summarize the current state, last meaningful progress, and next unblock or decision.
If the user only asked to get up to speed, stop after the brief. Otherwise continue from the adopted status file.

Notes

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.
If the resolved task still points at a live foreign zellij session, treat that as diagnostic context unless the user explicitly wants cross-session messaging.

このリポジトリの他の Skills

同じリポジトリ

start-zellij-session-for-task

ma08/botfiles

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.

2026-06-3028

start-new-task

ma08/botfiles

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".

2026-06-2428

create-oracle-review-powered-goal-plan

ma08/botfiles

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.

2026-06-2328

create-ticket-session

ma08/botfiles

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`.

2026-06-2228

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.

Continue Task

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.

Invocation

/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>

Commands

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>"

Process

Resolve the existing task home first.
If resolution is ambiguous, stop and surface the candidates. Do not guess.
Read the resolved status.md first. Treat task metadata and local status recap as the source of truth.
Use only a short transcript tail as fallback for final pre-interruption context.
Adopt the task into the current session by running sync_task_metadata.py against the resolved status file.
If the task home lives in another repo, treat that workspace as canonical before making code changes.
After adoption, update the status file with a short takeover note, refreshed current state, and next step.
If no tracked task home exists, stop and suggest creating one instead of fabricating resume context.

Output Expectations

Confirm the adopted task folder, status file, tracker URL, transcript path, and canonical workspace.
Summarize the current state, last meaningful progress, and next unblock or decision.
If the user only asked to get up to speed, stop after the brief. Otherwise continue from the adopted status file.

Notes

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.
If the resolved task still points at a live foreign zellij session, treat that as diagnostic context unless the user explicitly wants cross-session messaging.