codex-plan-collaboration

Coordinate multi-agent software development workflows through structured plan files.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/qdouble/stack-contracts --skill codex-plan-collaboration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-plan-collaboration
Source: https://github.com/qdouble/stack-contracts/tree/main/.agent/skills/codex-collab
Command: npx skills add https://github.com/qdouble/stack-contracts --skill codex-plan-collaboration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines multi-agent collaboration on software development tasks, ensuring clear communication, structured reviews, and efficient implementation through a defined workflow.

Core Features & Use Cases

  • Structured Collaboration: Manages a multi-stage workflow including review, implementation, audit, and hardening of plans and code.
  • File-Based State Management: Uses a specific file naming and front-matter convention to track the state and history of collaboration rounds.
  • Use Case: When an AI agent (Opus) needs another agent (Codex) to review a proposed code change, it creates a review plan file. Codex then responds, and the process continues through implementation and auditing, all managed via these structured files.

Quick Start

Use the codex-plan-collaboration skill to initiate a review of a new feature plan by creating a review request file.

Frequently Asked Questions about codex-plan-collaboration

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

FAQPage Schema
How do I manage multi-agent collaboration for code reviews and development plans?

Multi-agent collaboration for code reviews and development plans is managed through a structured, file-based workflow using specific naming and front-matter conventions to track state, history, and agent handoffs.

What is the best way to structure an iterative development process with AI agents?

An iterative development process with AI agents is structured using defined stages including review, implementation, audit, and hardening, ensuring clear communication and strict adherence to project lifecycle conventions.

How do I track state and history for an agent workflow during software development?

Agent workflow state and history are tracked using strict file naming and front-matter contracts, enabling seamless agent handoffs and consistent state management across multiple collaboration rounds.

Can I use file-based conventions to handle agent handoffs for plan management?

Yes, file-based conventions handle agent handoffs for plan management by enforcing front-matter contracts that define the state of collaboration rounds, ensuring agents properly review and implement proposed code changes.

When do I need a structured workflow for auditing code changes across multiple agents?

You need a structured workflow for auditing code changes across multiple agents when an AI agent requires another agent to review, implement, and harden proposed plans while maintaining strict lifecycle management and project conventions.