Keep Codex App predictable for feature-driven work.
This config keeps the repo skill-based, spec-first, and validation-driven:
docs/features/<feature-id>/FEATURE.mdis the source of truth for one feature.- Skills help Codex write specs, research unknowns, generate acceptance, implement, and repair.
- In target app repos,
$HOME/.codex/scripts/gateand$HOME/.codex/scripts/acceptance --feature <FEATURE_DIR>decide done. - When editing this
dot-codexconfig repo itself, do not run gate or feature acceptance unless explicitly requested. - No in-repo orchestrator.
Greenfield:
codex "Use the app-to-features skill for this app idea"- Pick one generated feature directory.
codex "Use the feature skill for docs/features/<feature-id>"- If needed,
codex --search "Use the research skill for docs/features/<feature-id>" codex "Use the acceptance-author skill for docs/features/<feature-id>"codex "Use the feature-execute skill for docs/features/<feature-id>"- In the target app repo, run gate and feature acceptance.
Brownfield:
- Choose one
FEATURE_DIR. codex "Use the feature skill for docs/features/<feature-id>"- If needed,
codex --search "Use the research skill for docs/features/<feature-id>" codex "Use the acceptance-author skill for docs/features/<feature-id>"codex "Use the feature-execute skill for docs/features/<feature-id>"- If checks fail,
codex "Use the auto-improve skill for docs/features/<feature-id>" - In the target app repo, run gate and feature acceptance.