Skip to content
Skills Library
AI & agents · Automation

codex-deck-flow

/codex-deck-flow

Use this skill when the user asks for persistent multi-agent coding workflows with task dependencies, per-task codex sessions, git worktree isolation, and explicit merge flow backed by one JSON workflow file under ./.codex-deck/. Always use this skill when the user explicitly mentions `$codex-deck-flow` or `codex-deck-flow`.

Repository
codex-deck ↗
Licence
MIT
Last repository change
17.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
17
Scripts
9
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 9 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/codex_resume_noninteractive.py, scripts/daemon.py, scripts/daemon_client.py, scripts/daemon_send.py, scripts/run.sh, scripts/session_state.py, scripts/session_summary.py, scripts/task_runner.py, scripts/workflow.py

What it does and when to use it

Use this skill when the user asks for persistent multi-agent coding workflows with task dependencies, per-task codex sessions, git worktree isolation, and explicit merge flow backed by one JSON workflow file under ./.codex-deck/. Always use this skill when the user explicitly mentions `$codex-deck-flow` or `codex-deck-flow`.

Original author description

Use this skill when the user asks for persistent multi-agent coding workflows with task dependencies, per-task codex sessions, git worktree isolation, and explicit merge flow backed by one JSON workflow file under ./.codex-deck/. Always use this skill when the user explicitly mentions `$codex-deck-flow` or `codex-deck-flow`.

How it works

  1. Mandatory activation contract
  2. Strict task creating mode
  3. Core runtime model
  4. Route by intent
  5. Reference loading boundaries
  6. References
Original SKILL.md headings · 95 lines, 758 words
SKILL.md preview
---
name: codex-deck-flow
description: Use this skill when the user asks for persistent multi-agent coding workflows with task dependencies, per-task codex sessions, git worktree isolation, and explicit merge flow backed by one JSON workflow file under ./.codex-deck/. Always use this skill when the user explicitly mentions `$codex-deck-flow` or `codex-deck-flow`.
allowed-tools: Bash(${CLAUDE_PROJECT_DIR}/.claude/skills/codex-deck-flow/scripts/*:*)
---

# Orchestrate Persistent Multi-Agent Workflows

Use this skill to create workflows, inspect workflows, and send control messages to the background codex-deck-flow daemon.

This skill is an **operator control client**, not the long-running orchestrator. After the daemon has started successfully and a control message has been sent successfully, the skill should stop.

Detailed operational guidance is routed through `references/*.md`:

- Command sequences and syntax: `references/commands.md`
- Workflow/task authoring rules: `references/authoring.md`
- Failure recovery runbooks: `references/runbooks.md`
- Scheduler vs workflow-task guidance placement: `references/guidance-routing.md`
- Architecture, contracts, and role prompts: `references/agent-flow-design.md`
- Scheduler mutation heuristics (scheduler task only): `references/scheduler.md`

## Mandatory activation contract

- If the user explicitly mentions `$codex-deck-flow` or `codex-deck-flow`, treat that as a strict instruction to use this workflow system.
- Do not switch to direct ad-hoc coding as the primary path while that request is active.
- In the first response after activation, say that codex-deck-flow orchestration is active and state the first command you are running.
- If the user gives `project root` plus `workflow ID` for a workflow that the current session has not created, loaded, or already resolved, first run `resolve-workflow`, then continue with `validate`, `reconcile`, and `status`.
- If the current session already knows the workflow path from `create`, a previous `resolve-workflow`, or earlier inspection in the same chat, reuse that path instead of resolving again.
- If the user already gave a workflow path, start with `validate`, then `reconcile`, then `status`.
- If no workflow exists yet, start with `create`, then immediately `validate`, then `show` or `status`, and present the authored tasks/prompts for user approval before `trigger`.
- If the user explicitly includes `Strict task creating mode`, keep the normal create/validate/show flow, but use the strict authoring protocol described below.
- Keep merge explicit. Never run `merge --apply` unless the user explicitly asked to apply the integration branch into the target branch.
- Once `trigger` or `daemon-send` succeeds, stop. Do not continue the same skill turn as if it were the orchestrator.

## Strict task creating mode

When the user explicitly includes `Strict task creating mode`, treat that as a workflow-authoring protocol layered on top of the normal codex-deck-flow create flow.

Rules:

- Still run `create`, then `validate`, then `show` or `status` as usual.
- The draft workflow JSON already exists after `create`; approval still gates `trigger`, not draft creation.
- If you must ask the user a clarifying question before the workflow is ready, the assistant message must end with exactly:
  - `<codex-deck-flow>Question<codex-deck-flow/>`
- When asking the user to approve the authored workflow, the assistant message must end with exactly:
  - `<codex-deck-flow>Request approve:workflow-file-name.json<codex-deck-flow/>`
- Replace `workflow-file-name.json` with the JSON file name only, for example `feature-delivery.json`.
- Use only the file name token after `Request approve:`. Do not add brackets or extra wrappers.
- Do not put any additional text after the strict tag suffix.
- Once the user approves, exit strict task creating mode and continue with the normal codex-deck-flow flow.
- If the approval message includes workflow data for an already-created draft, reuse that workflow and do **not** run `create` again.
- The approval workflow data may include fields such as `workflowPath`, `workflowFileName`, `workflowId`, `projectRoot`, and `boundSessionId`; treat that as the canonical handoff for reusing the already-authored draft.

## Core runtime model

- One workflow = one JSON file under `./.codex-deck/`.
- The daemon is the orchestration owner and can serve workflows from multiple project roots.
- The skill starts daemon if needed, sends one control message, then stops.
- Worker tasks run in isolated `git worktree` directories.
- Scheduler continuity should use codex-deck-flow non-interactive app-server-backed resume behavior (`scripts/codex_resume_noninteractive.py` behavior model), not raw `codex resume SESSION_ID` semantics in daemon mode.

Use `references/agent-flow-design.md` for full runtime contracts and role data.

## Route by intent

Use this decision route, then follow details in `references/commands.md`:

1. New workflow request: `create` -> `validate` -> `show/status` -> user approval -> `trigger`
2. Existing workflow by known path: `validate` -> `reconcile` -> `status`
3. Existing workflow by project root + workflow ID when path unknown in current session: `resolve-workflow` -> `validate` -> `reconcile` -> `status`
4. Explicit daemon control message: `daemon-send` or `stop-workflow-processes`
5. Merge request: `merge` preview, and `merge --apply` only if explicitly requested

## Reference loading boundaries

- Scheduler task only: `references/scheduler.md`
- Scheduler/workflow-task guidance file rules and routing: `references/guidance-routing.md`
- Non-scheduler roles should not load scheduler-specific mutation guidance.

## References

Canonical references:

- `references/commands.md`
- `references/authoring.md`
- `references/runbooks.md`
- `references/guidance-routing.md`
- `references/agent-flow-design.md`
- `references/scheduler.md` (scheduler task only)

Implementation scripts:

- `scripts/workflow.py`
- `scripts/task_runner.py`
- `scripts/daemon.py`
- `scripts/daemon_client.py`
- `scripts/codex_resume_noninteractive.py`
- `scripts/session_state.py`
- `scripts/session_summary.py`
Files in this package (17)
  • SKILL.md 6 KB
  • agents/openai.yaml 1 KB
  • references/agent-flow-design.md 38 KB
  • references/authoring.md 2 KB
  • references/commands.md 7 KB
  • references/guidance-routing.md 4 KB
  • references/runbooks.md 2 KB
  • references/scheduler.md 3 KB
  • scripts/codex_resume_noninteractive.py 22 KB
  • scripts/daemon.py 39 KB
  • scripts/daemon_client.py 7 KB
  • scripts/daemon_send.py 2 KB
  • scripts/run.sh 6 KB
  • scripts/session_state.py 5 KB
  • scripts/session_summary.py 56 KB
  • scripts/task_runner.py 22 KB
  • scripts/workflow.py 94 KB

Versions

The database has no other skills named codex-deck-flow.

Database snapshot: 13.11.2026 · package version 8d6d2ab98289 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100agent-deck
    agent-deck, the terminal session manager for AI coding agents. Use when the user mentions "agent-deck", "session", "sub-agent", "MCP attach", or "git worktree", or needs to create, start, message, read, fork, restart, or supervise agent-deck sessions; launch child sessions or…
  • 100multi-session-dev
    用多个 AI 编码会话(Claude Code、claude.ai、Codex 等)并行开发一个或多个仓库时的分工与交接做法:一个管理会话做决策和集成,几个开发会话各在自己的分支和 worktree 里实现、验收、交付,子代理做短调研和审查,云端会话在用户不在时推进。管:什么时候自己做、派子代理还是开新会话;派工前查写入边界、共享契约和版本号、桌面端口数据目录这类只有一份的资源、有几件事在等用户;任务简报;按改动挑验收证据(静态检查、截图或录屏、真机);结束报告第一句和换会话交接;管理会话核对 Git…
  • 100codex-review
    Guides codex-review plugin workflows. Use when the user asks to review a plan or implementation with Codex, mentions codex-review, asks about review status or findings, or needs help with plan resolution or inline plans.
  • 100codex-deck-terminal
    Plan approval-first terminal workflows for codex-deck using markdown plus machine-readable HTML-like tags. Use when a controller or UI should parse shell-step proposals, show executable cards, react to approval or rejection, and continue from structured execution summaries.
  • 100orca
    Orca is an open-source desktop app that runs several coding agents (Claude Code, Codex, OpenCode and any other terminal agent) side by side, each in its own git worktree, with one CLI to script it. Use when the user wants to race agents on the same task, hand work to another…
  • 100codex-cli-invoke-persist
    Create and resume Codex CLI sessions with a persistent session-name-to-thread_id mapping plus last-used model stored in a workspace-scoped JSON file under system temp. Invoke only when the user explicitly names `$codex-cli-invoke-persist` or otherwise clearly requests this exact…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.