skills.rest
connor-git-yaml
connor-git-yamlCOMMUNITY
Explore all skills by this author →
GitHub

spec-driver-story

Execute the Spec Driver workflow in Codex while preserving artifact gates and outputs.

15|5|Updated Feb 10, 2026
Search Tags:#workflow#codex#agents#orchestration#spec-driver
One-click install
npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill spec-driver-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driver-story
Source: https://github.com/connor-git-yaml/cc-plugin-market/tree/main/.codex/skills/spec-driver-story
Command: npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill spec-driver-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts and runs the Spec Driver workflow inside Codex, preserving the original artifacts, gates, and governance so teams can keep a single, Codex-native execution surface without rewriting the workflow.

Core Features & Use Cases

  • Codex-native wrapping of the Spec Driver mode to reuse existing artifacts and gates.
  • Deterministic execution with inline sub-agent runs that mirror the original plugin steps.
  • Use cases include prototyping Spec Driver runs, validating workflows in Codex, and comparing Codex results against the plugin baseline.

Quick Start

Initiate the spec-driver-story trigger in Codex to execute the Spec Driver flow with the same artifacts and gates as the original workflow.

Frequently Asked Questions about spec-driver-story

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

FAQPage Schema
How do I run Spec Driver workflows inside Codex while preserving artifact gates?▼

To run Spec Driver workflows inside Codex with preserved artifact gates, use this wrapper to convert and execute the workflow natively, maintaining the original governance and deterministic outputs without rewriting the flow.

What is a Codex-native wrapper for Spec Driver orchestration used for?▼

A Codex-native wrapper for Spec Driver orchestration is used to execute the original workflow inside Codex, keeping a single execution surface to prototype runs, validate workflows, and compare results against the plugin baseline.

Can I compare Codex execution results against the original Spec Driver plugin baseline?▼

Yes, you can compare Codex execution results against the original Spec Driver plugin baseline by running this wrapper, which mirrors the plugin steps through inline sub-agent runs while respecting the same artifact gates.

Does the Codex Spec Driver wrapper maintain the same artifacts and execution rules as the plugin?▼

Yes, the Codex Spec Driver wrapper maintains the same artifacts and execution rules as the plugin, fulfilling gate respect, predictable execution, runtime model handling, and alignment with the source skill's execution rules.

What is the best way to automate Spec Driver mode execution in Codex?▼

The best way to automate Spec Driver mode execution in Codex is initiating the trigger to run the flow with inline sub-agent runs, ensuring deterministic execution and preserving existing artifacts without manual workflow rewriting.

Related Skills

Explore More Software Engineering Skills→
connor-git-yamlconnor-git-yaml
15

spec-driver-fix

Integrate Spec Driver mode into Codex with preserved artifacts and gates.

Community
Advanced
yoshisadayoshisada

kiln-research

Automate baseline-vs-candidate plugin research and emit a markdown report.

Community
Advanced
antigravityos187-sketchantigravityos187-sketch

epic-orchestrate

Coordinate specialized sub-agents through a 6-phase workflow with file-based artifacts.

Community
Advanced
connor-git-yamlconnor-git-yaml
15

spec-driver-doc

Run Spec Driver mode inside Codex while preserving artifacts and gates.

Community
Advanced