skills.rest
Catsofsuffering
CatsofsufferingCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ccgs-spec-plan

Plan Codex changes and generate bounded execution handoff packets for Claude.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans the change from Codex and prepares the execution handoff contract for Claude.

Core Features & Use Cases

  • Core contract: Codex remains the orchestrator; Codex owns planning, boundary-setting, and acceptance criteria; Claude executes only after Codex has prepared a bounded handoff.
  • Output preparation: Reads OpenSpec artifacts and defines allowed surfaces, protected surfaces, work packages, and verification criteria.
  • Guardrails: Do not modify product code in this step; do not ask Claude to decide the plan; do not redirect the user to Claude slash commands.

Quick Start

Initiate planning for the active change and generate a bounded handoff packet for Claude.

Frequently Asked Questions about ccgs-spec-plan

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

FAQPage Schema
How do I prepare a Claude handoff packet from OpenSpec planning artifacts?▼

To prepare a Claude handoff packet, define allowed and protected surfaces, work packages, and verification criteria from OpenSpec artifacts to ensure bounded execution.

What is the best way to structure Codex changes before Claude execution?▼

The best way to structure Codex changes is to use Codex as the orchestrator to set boundaries and acceptance criteria, generating a bounded handoff packet for Claude.

Does the OpenSpec planning workflow prevent Claude from modifying product code?▼

Yes, the OpenSpec planning workflow includes guardrails that prevent modifying product code during planning and stop Claude from deciding the execution plan.

Can I use Claude to decide the execution plan during Codex handoff preparation?▼

No, Claude cannot decide the execution plan. Codex must own the planning, boundary-setting, and acceptance criteria before creating the bounded handoff.

What should a bounded handoff contract include for Claude task refinement?▼

A bounded handoff contract should include clearly defined allowed surfaces, protected surfaces, work packages, and verification criteria derived from OpenSpec artifacts.

Why should I avoid redirecting to Claude slash commands during OpenSpec planning?▼

You should avoid Claude slash commands during OpenSpec planning because Codex must remain the orchestrator, owning the plan and boundary-setting to prepare the handoff.

Related Skills

Explore More Product & Management Skills→
benbrastmckiebenbrastmckie
3

skill-implementer

Executes implementation tasks by delegating to a subagent and managing postflight metadata.

Community
Advanced
CatsofsufferingCatsofsuffering
5

ccgs-spec-impl

Dispatch Claude execution from Codex with bounded implementation packets.

Community
Advanced
leyuan0602-glitchleyuan0602-glitch
9

code-acceptance

Verify code changes against executable tests and visual evidence.

Community
Advanced
CrashBytesCrashBytes
6

product-owner

Manage product backlogs, write user stories, and prioritize with RICE.

Community
Advanced