ccgs-spec-init

Automate Codex-led initiation and continuation of OpenSpec changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start or resume a CCGS change from Codex.

Core Features & Use Cases

  • Codex remains the orchestrator for the change flow, ensuring OpenSpec is the source of truth.
  • Avoids using Claude as the host shell for artifact creation and progression.
  • Guides the user through the initial OpenSpec checks and the first artifact step.

Quick Start

Start a Codex-led change by running the ccgs-spec-init skill to select the change and prepare the first artifact.

Frequently Asked Questions about ccgs-spec-init

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

FAQPage Schema
How do I initiate an OpenSpec change using Codex?

To initiate an OpenSpec change using Codex, you use a workflow automation skill that selects the change context, validates its status, and prepares the first artifact automatically.

What is the best way to resume an in-progress OpenSpec change?

Resuming an in-progress OpenSpec change requires a Codex-led workflow tool that validates the current status and selects the next artifact to continue the change management flow.

Do I need OpenSpec tooling installed to start a Codex-led change?

Yes, you must have OpenSpec tooling installed and a valid change context available before you can automate the initiation and continuation of changes within the CCGS workflow.

Why use Codex instead of Claude as the host shell for artifact creation?

Using Codex instead of Claude as the host shell ensures Codex remains the orchestrator for the change flow, keeping OpenSpec as the source of truth for artifact creation and progression.

How does the CCGS workflow determine the next artifact for an OpenSpec change?

The CCGS workflow determines the next artifact by validating the change status from OpenSpec and applying automated logic to select the appropriate artifact step for progression.