spec-plan

Automate OpenSpec planning and create a bounded execution handoff packet.

5|1|Updated Apr 8, 2026

Search Tags:#design #planning #execution #handoff #OpenSpec #change-management #task-slicing

Ready to run

npx skills add https://github.com/Catsofsuffering/ccsm --skill spec-plan-catsofsuffering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-plan
Source: https://github.com/Catsofsuffering/ccsm/tree/main/templates/codex-skills/spec-plan
Command: npx skills add https://github.com/Catsofsuffering/ccsm --skill spec-plan-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables structured planning and creation of a bounded execution handoff for OpenSpec changes, aligning Codex-driven planning with Claude execution.

Core Features & Use Cases

Define an Execution Handoff Contract and boundaries before execution
Break down changes into concrete work packets suitable for bounded execution
Update OpenSpec artifacts (change id, execution goal, allowed/protected boundaries, required verification)
Ensure design.md contains an Execution Handoff Contract and tasks.md is sliceable into executable steps
Prepare and emit the exact bounded packet Codex will hand off to Claude for execution

Quick Start

Select the active change and prepare the bounded execution packet.

Frequently Asked Questions about spec-plan

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

FAQPage Schema

How do I create an execution handoff packet for OpenSpec changes?▼

An execution handoff packet for OpenSpec changes is created by defining an Execution Handoff Contract in design.md and breaking tasks.md into concrete execution slices, producing a bounded packet with change id, execution goal, boundaries, and verification steps.

What is an Execution Handoff Contract in change planning?▼

An Execution Handoff Contract is a defined boundary structure within design.md that specifies the execution goal, allowed and protected boundaries, and required verification for a change before it is handed off for bounded execution.

How do I break down OpenSpec changes into concrete execution slices?▼

You break down OpenSpec changes into concrete execution slices by refining tasks.md into specific executable work packets, ensuring each slice aligns with the bounded execution parameters defined in the Execution Handoff Contract.

When do I need to prepare a bounded execution packet for change management?▼

You need to prepare a bounded execution packet when a change requires design, task refinement, and a bounded packet for execution, ensuring OpenSpec artifacts are updated and the handoff is properly scoped before execution begins.

Does spec-plan work without additional dependencies for task slicing?▼

Yes, spec-plan operates without additional dependencies, automating the task slicing and execution handoff preparation entirely within the OpenSpec artifact structure to produce the bounded packet for execution.

What are the limitations of using a bounded execution handoff for change management?▼

The bounded execution handoff approach is limited to changes requiring design and task refinement within OpenSpec artifacts, and may not suit changes that cannot be constrained to a bounded execution packet or lack verifiable boundaries.