spec-fast

Coordinate OpenSpec workflow phases with Codex and bounded rework loops.

5|1|Updated Apr 8, 2026

Search Tags:#automation #workflow #codex #openspec #orchestrate #rework #spec-fast

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end coordination of the OpenSpec workflow from Codex orchestration across all phases, reducing manual handoffs and errors.

Core Features & Use Cases

Bounded, state-aware orchestration of proposal to archive using existing phase skills (spec-init, spec-plan, spec-impl, spec-review) with Codex as primary orchestrator
Enforces OpenSpec as truth and guardrails to prevent unsafe behavior; limited rework budget and manual intervention when needed
Provides deterministic rework flows for failed reviews within a two-round budget, surfacing blockers when exhausted

Quick Start

Start the spec-fast orchestration to drive the OpenSpec lifecycle from init through review.

Frequently Asked Questions about spec-fast

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

FAQPage Schema

How do I automate the OpenSpec workflow lifecycle from proposal to archive?▼

To automate the OpenSpec workflow lifecycle, you can use an orchestration tool that coordinates existing phase skills from spec-init through spec-review with Codex as the primary orchestrator. This enforces OpenSpec as truth and reduces manual handoffs end-to-end.

What is bounded rework in automated spec-driven code changes?▼

Bounded rework in spec-driven changes limits failed review retries to a maximum of two rounds using a deterministic rework flow. When the rework budget is exhausted, the orchestration surfaces blockers and requires manual intervention to proceed safely.

How does state-aware resume work for OpenSpec orchestration?▼

State-aware resume for OpenSpec orchestration tracks the progress of predefined phases like spec-init, spec-plan, spec-impl, and spec-review. It allows the Codex orchestrator to resume the workflow seamlessly after interruptions or failed review rounds without restarting from scratch.

Can I use Codex orchestration to manage spec-init and spec-plan phases without manual handoffs?▼

Yes, Codex orchestration can manage spec-init and spec-plan phases without manual handoffs by acting as a single primary orchestrator. It drives the OpenSpec lifecycle across all predefined phases while enforcing guardrails to prevent unsafe behavior.

When should I manually archive an OpenSpec proposal during automated orchestration?▼

You should manually archive an OpenSpec proposal only after Codex confirms the spec-review phase is archive-ready. The orchestration enforces a single orchestrator model and requires this manual archive step to ensure the change lifecycle is reliable and complete.