smux-compozy-pairing

Orchestrate Codex and Claude workflows in tmux to generate PRD, TechSpec, and tasks.

2.5k|134|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill smux-compozy-pairing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smux-compozy-pairing
Source: https://github.com/compozy/compozy/tree/main/.agents/skills/smux-compozy-pairing
Command: npx skills add https://github.com/compozy/compozy --skill smux-compozy-pairing

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Coordinates an autonomous, TMUX-based pairing workflow where a single orchestrator aggregates inputs from Codex and Claude to generate PRD/TechSpec/tasks, reducing handoffs and manual coordination.

Core Features & Use Cases

  • Autonomous multi-agent orchestration: One workflow that coordinates Codex, Claude, and an orchestrator to produce structured artifacts (PRD, TechSpec, tasks).
  • TMUX-driven collaboration: Spawns worker panes for Codex and Claude, enabling parallel thinking with a live UI bridge.
  • On-demand assets & scripts: Uses assets, references, and scripts to bootstrap sessions, boot prompts, and start-up commands.
  • Run-time contract & safety: Enforces the runtime contract to ensure proper sequencing and guarded execution.

Quick Start

Launch the pairing workflow for a feature by specifying the feature slug under .compozy/tasks and the repo root, then attach to the tmux session and let Codex and Claude iterate.

Frequently Asked Questions about smux-compozy-pairing

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

FAQPage Schema
How do I orchestrate Codex and Claude in a tmux session for feature development?

Multi-agent AI workflow orchestration coordinates Codex and Claude in tmux to generate structured artifacts like PRDs and TechSpecs. It uses a single orchestrator to aggregate inputs from both agents, reducing manual handoffs during feature development.

How does tmux orchestration work for multi-agent AI pairing?

Tmux orchestration spawns separate worker panes for Codex and Claude, enabling parallel thinking with a live UI bridge. The orchestrator coordinates these agents to produce structured artifacts like PRDs and tasks with minimal human supervision.

Can I run AI pairing workflows in headless automation mode without a TUI?

Yes, the workflow explicitly supports both interactive TUI workflows and headless automation constraints. You can generate PRD, TechSpec, and task artifacts without direct terminal interaction by enforcing the runtime contract for guarded execution.

Do I need to manually coordinate task generation between Codex and Claude?

No, you do not need to manually coordinate task generation. The orchestrator autonomously aggregates inputs from Codex and Claude to generate PRD, TechSpec, and tasks, reducing handoffs and manual coordination overhead during feature development.

What is the runtime contract in multi-agent AI workflow orchestration?

The runtime contract enforces proper sequencing and guarded execution across Codex, Claude, and the orchestrator. It ensures safe multi-agent AI workflow operations by satisfying requirements for frontmatter-driven skill discovery, boot prompts, and on-demand scripts integration.

How do I bootstrap a multi-agent tmux session with on-demand scripts and assets?

You bootstrap a multi-agent tmux session by specifying the feature slug under .compozy/tasks and the repo root. The workflow then uses on-demand assets, references, and scripts to initialize sessions, load boot prompts, and execute start-up commands.