spec-driver-feature

To run the Spec Driver workflow inside Codex while preserving original artifacts, activate the spec-driver-feature skill to wrap the existing plugin structure, maintaining consistent artifact paths and gating rules across environments.

Runtime context injection in Codex agent prompts is a mechanism that enforces parallelism controls and dynamically supplies execution context to Spec Driver stages, enabling consistent end-to-end feature development orchestration.

Yes, Codex supports Spec Driver gating rules for feature development by enforcing the original gating structure and preserving artifact paths, which ensures compatible and consistent workflow execution across environments.

Yes, you can use Codex prompts to orchestrate end-to-end feature development workflows by integrating them with the Spec Driver stages to execute research prompts, governance checks, and feature generation using existing runtime context.

To execute governance checks in a Codex feature development workflow, run the Spec Driver mode to apply original artifacts and gates, enforcing runtime context injection and parallelism controls during the governance stage.

Spec Driver artifacts may change paths in Codex if the execution environment lacks proper gating enforcement, which can be resolved by using a Codex-native wrapper that explicitly preserves original artifact paths and structure.