spec-driver-doc

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

15|5|Updated Feb 10, 2026

Search Tags:#automation #workflow #integration #codex #agents #plugins #spec-driver

Ready to run

npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill spec-driver-doc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driver-doc
Source: https://github.com/connor-git-yaml/cc-plugin-market/tree/main/.codex/skills/spec-driver-doc
Command: npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill spec-driver-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex native wrapper to run the Spec Driver mode while preserving the original artifact gates and workflow.

Core Features & Use Cases

Wraps Spec Driver execution inside Codex for consistent runtime context.
Maintains artifacts, gates, and outputs across the workflow.
Use Case: Run automated Spec Driver tasks without leaving the Codex environment.

Quick Start

Invoke spec-driver-doc to run Spec Driver mode in Codex and preserve the same artifacts and gates as the original workflow.

Frequently Asked Questions about spec-driver-doc

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

FAQPage Schema

How do I run Spec Driver tasks inside Codex without losing artifact gates?▼

To run Spec Driver tasks inside Codex without losing artifacts, invoke the spec-driver-doc wrapper. It injects runtime context and preserves the original file paths, gates, and outputs across the workflow.

What is the benefit of wrapping Spec Driver execution in a Codex-native environment?▼

A Codex-native wrapper for Spec Driver execution provides consistent runtime context while maintaining artifacts and gates. It enables end-to-end task automation without leaving the Codex environment.

How do I maintain file paths and artifacts when automating Spec Driver workflows?▼

To maintain file paths and artifacts during Spec Driver automation, use a Codex-native wrapper that injects runtime context. This preserves the original artifact gates throughout the workflow execution.

Does the Spec Driver Codex wrapper support automated end-to-end workflows?▼

Yes, the Spec Driver Codex wrapper supports automated end-to-end workflows. It wraps Spec Driver execution inside Codex, maintaining artifacts, gates, and outputs across the entire automated process.

Can I use Spec Driver mode in Codex and keep the original artifact gate workflow?▼

Yes, you can use Spec Driver mode in Codex while keeping the original artifact gate workflow. The wrapper preserves the original artifacts, gates, and file paths during runtime context injection.

Why does my Spec Driver workflow lose artifacts when running outside its native environment?▼

Spec Driver workflows lose artifacts without a native environment wrapper because runtime context is not injected correctly. A Codex-native wrapper preserves file paths, gates, and outputs across the workflow.