Menu
Use when adding, deleting, listing, showing, or editing codex task queue items in ./tasks/list.jsonl for the packaged codex-task-watchdog workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when implementation work in a rielflow project changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the packaged `claude-code-design-and-implement-review-loop` workflow, including design/plan alignment, implementation, review, user-facing documentation refresh, commit-message generation, and built-in git commit/push steps.
Use when implementation work in a rielflow project changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the packaged `codex-design-and-implement-review-loop` workflow, including design/plan alignment, implementation, review, user-facing documentation refresh, commit-message generation, and built-in git commit/push steps.
Use when requested work should first be converted into a project-scope Rielflow workflow and then executed through Rielflow. Applies to workflow-first implementation, review, refactoring, documentation, or maintenance tasks where no existing package workflow exactly fits, and to requests that explicitly say to work through a project-scope workflow.
Use when requested work should first be converted into a project-scope Rielflow workflow and then executed through Rielflow. Applies to workflow-first implementation, review, refactoring, documentation, or maintenance tasks where no existing package workflow exactly fits, and to requests that explicitly say to work through a project-scope workflow.
Use when running, editing, or troubleshooting the packaged claude-code-deepdesign rielflow workflow for design-doc specification authoring with deep and broad review loops.
Use when installing a rielflow workflow bundle from a public GitHub directory URL with workflow checkout. Covers project/user scope destinations, duplicate handling, overwrite behavior, registry metadata, validation, and checkout troubleshooting.
| name | codex-task-queue |
| description | Use when adding, deleting, listing, showing, or editing codex task queue items in ./tasks/list.jsonl for the packaged codex-task-watchdog workflow. |
| user-invocable | true |
Use this skill to manage the ./tasks/list.jsonl queue consumed by the
packaged codex-task-watchdog workflow.
Treat these user requests as requests to add an active item to the watchdog
task queue:
watchdog taskを追加せよwatchdog taskを追加してCodex watchdogにタスクを積んでcodex-task-watchdogにこの作業を予約してtasks/list.jsonlにwatchdog用タスクを追加してWhen the user says watchdog task, assume they mean a task queue item for
codex-task-watchdog, not starting or stopping the background watcher, unless
they explicitly mention daemon setup, cron/event serving, start, stop, or
status inspection.
Default path: ./tasks/list.jsonl.
Each line is one JSON object. Recommended fields:
{
"id": "task-20260604-001",
"status": "active",
"kind": "design-and-impl",
"title": "Short task title",
"prompt": "Concrete work request for Codex or a dependency workflow.",
"workflowInput": {},
"constraints": [],
"acceptanceCriteria": [],
"createdAt": "2026-06-04T00:00:00.000Z"
}
Statuses:
active: runnable by the next watchdog polling pass.running: claimed by the workflow; later polling passes skip while this exists.done: completed; when every task is done, polling passes skip.failed or cancelled: ignored by automatic selection.Kinds:
design-and-impl: dispatches codex-design-and-implement-review-loop.design-deepthin, design-deepthink, deepdesign, or design: dispatches codex-deepdesign.review: dispatches codex-recent-change-quality-loop.adhoc: runs the prompt in the local Codex worker step.tasks/ exists.tasks/list.jsonl.id; use timestamp ids when the user does not specify one.status to active unless the user explicitly asks otherwise.workflowInput instead of inventing top-level fields.Example:
mkdir -p tasks
printf '%s\n' '{"id":"task-20260604-001","status":"active","kind":"adhoc","title":"Update docs","prompt":"Refresh README for the new option.","workflowInput":{},"createdAt":"2026-06-04T00:00:00.000Z"}' >> tasks/list.jsonl
Use jq when available:
jq -c . tasks/list.jsonl
Fallback:
sed -n '1,200p' tasks/list.jsonl
jq -c 'select(.id == "task-20260604-001")' tasks/list.jsonl
Rewrite the JSONL file without the matching id:
tmp="$(mktemp)"
jq -c 'select(.id != "task-20260604-001")' tasks/list.jsonl > "$tmp"
mv "$tmp" tasks/list.jsonl
Do not delete a running task unless the user explicitly asks to recover or
cancel the active run. Prefer changing it to failed or cancelled with a
short result.note.
If a workflow run died and left a stale running task, inspect rielflow
session status/export output and SQLite workflow_messages evidence first.
Do not recover by reading workflow communication from inbox/outbox files. Then either:
status back to active to retry, orstatus to failed with result.reason.After a successful run, codex-task-watchdog may also create or update
project-scope skills under .agents/skills based on the completed Codex log and
commit the accepted task queue and skill changes.