smux-compozy-pairing

Orchestrate tmux-based Codex and Claude pairing to generate Compozy PRD, TechSpec, and tasks.

Updated May 15, 2026
One-click install
npx skills add https://github.com/JBonfim/skill-developer --skill smux-compozy-pairing-jbonfim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smux-compozy-pairing
Source: https://github.com/JBonfim/skill-developer/tree/main/.agents/skills/smux-compozy-pairing
Command: npx skills add https://github.com/JBonfim/skill-developer --skill smux-compozy-pairing-jbonfim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, tmux, and includes scripts (resource) and assets (resource) and references (resource) components.

What problem does it solve?

This Skill orchestrates an interactive tmux-based pairing workflow to produce a complete Compozy plan (PRD/TechSpec/tasks) with peer review and autonomous checkpoint resolution, without requiring a human approval loop.

Core Features & Use Cases

  • Interactive tmux workspace orchestration: Boots Codex and Claude Code in separate worker panes and routes all exchanges through tmux-bridge for reliable collaboration.
  • PRD → TechSpec → task breakdown pipeline: Conditionally runs PRD generation, then TechSpec, then tasks, gating each phase on the presence of the expected Compozy artifacts.
  • Guardrailed autonomous checkpoints: Forces orchestrator-owned decisions at checkpoints, escalates only when source requirements are contradictory, and prevents headless shortcuts like codex exec or claude -p.
  • Use Case: When implementing a new feature, use this to collaboratively generate a consistent PRD, sharpen the TechSpec with architectural counterweighting, and decompose tasks into validated execution units for compozy start.

Quick Start

Run the smux-compozy-pairing workflow by first providing a feature name that maps to a tasks directory under .compozy/tasks/<feature-name>/.

Frequently Asked Questions about smux-compozy-pairing

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

FAQPage Schema
How do I generate a PRD and TechSpec using tmux pairing?

To generate a PRD and TechSpec using tmux pairing, this workflow boots Codex and Claude Code in separate panes, routing exchanges through tmux-bridge to collaboratively produce and validate Compozy planning artifacts gated by phase.

How does autonomous checkpoint resolution work during task decomposition?

Autonomous checkpoint resolution works by forcing orchestrator-owned decisions during task decomposition, escalating only when source requirements are contradictory, and preventing headless shortcuts like codex exec or claude -p.

Do I need tmux-bridge and python3 to run the Compozy pairing workflow?

Yes, you need python3, tmux, and active tmux-bridge connectivity to run the Compozy pairing workflow, along with Codex and Claude interactive workers available to participate in the session.

Can I use this workflow to decompose feature plans into validated tasks without human approval?

Yes, you can use this workflow to decompose feature plans into validated tasks without human approval by applying guardrailed autonomous checkpoints that conditionally gate PRD, TechSpec, and task generation phases.

What is the best way to coordinate Codex and Claude for architectural review?

The best way to coordinate Codex and Claude for architectural review is orchestrating an interactive tmux workspace that pairs the agents to provide architectural counterweighting and validate execution units against generated specifications.

Why does the Compozy task generation workflow require strict phase gating?

The Compozy task generation workflow requires strict phase gating on _prd.md, _techspec.md, and _tasks.md files to ensure each planning artifact exists and is validated before progressing to the next decomposition stage.