codex-deck-flow

Orchestrate multi-agent coding workflows with git worktrees and daemon control messages.

8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/asfsdsf/codex-deck --skill codex-deck-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-deck-flow
Source: https://github.com/asfsdsf/codex-deck/tree/main/skills/codex-deck-flow
Command: npx skills add https://github.com/asfsdsf/codex-deck --skill codex-deck-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

codex-deck-flow eliminates the friction of coordinating long-running, multi-step coding work by keeping a persistent workflow running in the background while you prepare approvals and control execution.

Core Features & Use Cases

  • Persistent multi-agent workflows: Create, validate, reconcile, inspect, and trigger multi-task coding plans with dependency ordering.
  • Daemon-owned execution: Starts (or reuses) a background daemon and sends operator control messages so scheduling continues after the skill turn ends.
  • Isolation via worktrees: Runs each task in an isolated git worktree to reduce branch conflicts and keep task boundaries clean.
  • Explicit merge policy: Keeps merge behavior explicit and avoids applying integration merges unless the user requests it.
  • Control-messaging & stop flow: Supports daemon control messages like stopping workflow processes and enqueuing scheduler triggers.

Quick Start

Ask the AI to activate codex-deck-flow by explicitly mentioning $codex-deck-flow and describe the workflow you want (including project root/workflow id when resuming) so it can create/validate/show tasks for approval and then trigger execution.

Frequently Asked Questions about codex-deck-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate persistent multi-agent coding workflows with task dependencies?

Persistent multi-agent coding workflows are orchestrated by creating a single workflow JSON contract to coordinate task dependencies, isolated git worktrees, and explicit control-message scheduling. The system validates and reconciles runtime state before triggering daemon-owned execution.

What is the best way to isolate multi-agent code execution across different git branches?

Isolating multi-agent code execution is handled by running each task in an isolated git worktree. This approach reduces branch conflicts and keeps task boundaries clean while the background daemon manages the overall workflow scheduling.

How do I manage and stop background daemon processes for running workflow tasks?

Background daemon processes are managed using explicit control-messaging commands like daemon-send and stop-workflow-processes. These messages allow you to enqueue scheduler triggers and halt execution without requiring manual intervention.

Does codex-deck-flow automatically merge git branches when a workflow task completes?

Automatic merging is not performed; the workflow enforces an explicit merge policy. It avoids applying integration merges unless you explicitly request them, ensuring you maintain control over branch integration after task execution.

How do I inspect task readiness and reconcile runtime state for an existing workflow?

Task readiness and runtime state are inspected by resolving the workflow using the project root or workflow ID. The system runs validate, reconcile, status, and show commands to inspect readiness and correct any runtime state discrepancies before triggering execution.