Menu
Use when configuring, validating, starting, stopping, or inspecting the packaged codex-task-watchdog background task watcher.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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-watchdog |
| description | Use when configuring, validating, starting, stopping, or inspecting the packaged codex-task-watchdog background task watcher. |
| user-invocable | true |
Use this skill to run the packaged codex-task-watchdog workflow as a background
task watcher. The event server stays alive, a cron source triggers polling
passes, and each pass claims at most one newly added active task. After a task
completes, the workflow reviews the completed Codex log for reusable lessons,
creates or updates project-scope skills under .agents/skills, reviews those
skill changes, and commits the accepted queue and skill updates.
This is not an OS service registration flow. Do not install systemd units, launchd plists, or login items unless the user explicitly asks for that.
In the project that should own the task queue:
.rielflow/workflows.rielflow-events./tasks/list.jsonlThe codex-task-watchdog workflow must be installed or checked out under the workflow
definition directory together with its dependency workflows:
codex-design-and-implement-review-loopcodex-deepdesigncodex-recent-change-quality-loopThe project should allow repository-local skills under .agents/skills; the
watchdog uses that directory for post-task skill extraction.
Create:
.rielflow-events/sources/codex-task-watchdog-cron.json
.rielflow-events/bindings/codex-task-watchdog-cron-to-workflow.json
Source example:
{
"id": "codex-task-watchdog-cron",
"kind": "cron",
"schedule": "*/30 * * * * *",
"timezone": "Asia/Tokyo"
}
Binding example:
{
"id": "codex-task-watchdog-cron-to-workflow",
"sourceId": "codex-task-watchdog-cron",
"workflowName": "codex-task-watchdog",
"match": {
"eventType": "cron.tick"
},
"inputMapping": {
"mode": "template",
"template": {
"taskListPath": "./tasks/list.jsonl",
"request": "Run one codex task watchdog polling pass.",
"scheduledAt": "{{event.input.scheduledAt}}",
"sourceId": "{{event.sourceId}}",
"scheduleId": "{{event.input.scheduleId}}",
"timezone": "{{event.input.timezone}}"
},
"mirrorToHumanInput": false
},
"execution": {
"async": true,
"dedupeWindowMs": 30000,
"maxConcurrentPerKey": 1,
"concurrencyKey": "codex-task-watchdog"
}
}
rielflow workflow validate codex-task-watchdog --workflow-definition-dir .rielflow/workflows
rielflow events validate --workflow-definition-dir .rielflow/workflows --event-root .rielflow-events
Start the rielflow event server with nohup from the project directory:
mkdir -p .rielflow/logs
nohup rielflow events serve \
--workflow-definition-dir .rielflow/workflows \
--event-root .rielflow-events \
> .rielflow/logs/codex-task-watchdog-events.log 2>&1 &
echo $! > .rielflow/logs/codex-task-watchdog-events.pid
Inspect:
tail -f .rielflow/logs/codex-task-watchdog-events.log
rielflow events list --event-root .rielflow-events --output json
Stop:
kill "$(cat .rielflow/logs/codex-task-watchdog-events.pid)"
rm .rielflow/logs/codex-task-watchdog-events.pid
Use an emitted cron payload when you want to test without waiting for the schedule:
rielflow events emit codex-task-watchdog-cron \
--workflow-definition-dir .rielflow/workflows \
--event-root .rielflow-events \
--event-file payload.json \
--output json