ccgs-spec-impl

Dispatch Claude execution from Codex with bounded implementation packets.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill ccgs-spec-impl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ccgs-spec-impl
Source: https://github.com/Catsofsuffering/CCGS/tree/main/templates/codex-skills/ccgs-spec-impl
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill ccgs-spec-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, Codex-led way to dispatch Claude as an execution worker without relinquishing acceptance, testing, or archive decisions, eliminating unsafe context switches and ambiguous ownership during implementation.

Core Features & Use Cases

  • Codex orchestration with Claude execution: Construct bounded execution packets and invoke Claude to implement only the approved scope.
  • Structured return and verification: Require a standardized return packet including changed files, tests run, unresolved issues, and a recommended next step, then run Codex-local verification before archive.
  • Guardrails and rework flow: Enforce allowed/protected paths, required checks, and produce a rework packet if verification fails, ensuring Codex retains archive authority.
  • Use Case: When a planned change is ready, generate the execution packet from proposal, design, and task documents, run Claude to implement the scope, then verify and accept or request rework from Codex.

Quick Start

Use the ccgs-spec-impl skill to dispatch Claude with a bounded execution packet for the active change and return the verification results to Codex.

Frequently Asked Questions about ccgs-spec-impl

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

FAQPage Schema
How do I orchestrate Claude execution from Codex for planned implementation work?

To orchestrate Claude execution from Codex, you build a bounded execution packet containing implementation goals, allowed and protected paths, and required tests, which dispatches Claude to implement only the approved scope while Codex retains verification authority.

How does Codex maintain control when dispatching Claude as an execution worker?

Codex maintains control by requiring a standardized return packet from Claude with changed files and tests run, then running Codex-local verification to decide whether to accept the work, request rework, or archive the change.

What is a bounded execution packet in Codex and Claude orchestration?

A bounded execution packet is a structured dispatch payload that defines implementation goals, allowed and protected paths, required tests, and return packet formats, ensuring Claude executes only the approved scope of a planned change.

How to handle verification failures when Claude executes a planned change for Codex?

When verification fails after Claude executes a planned change, the orchestration flow generates a rework packet that enforces required checks, ensuring Codex retains archive authority and can safely request corrections before accepting the implementation.

When do I need Codex orchestration with Claude execution for software engineering?

You need Codex orchestration with Claude execution when a planned change is ready for implementation and you must orchestrate bounded execution while eliminating unsafe context switches and ambiguous ownership during the implementation process.

Does Codex archive implementation changes automatically after Claude execution?

Codex does not archive changes automatically; it enforces a structured return packet from Claude and runs local verification to produce an archive decision, retaining full authority over the final acceptance of the implementation work.