Spec-Driven Planning: a skill for long-running Codex projects

[johnnykor82]

I published a Codex skill/plugin called Spec-Driven Planning:

https://github.com/johnnykor82/spec-driven-planning

It is a workflow for long-running, multi-phase Codex work where the agent needs to keep going for hours without losing the thread.

The idea is:

1. Start from an approved project specification.
2. Turn it into a hierarchical .planning/ tree.
3. Keep only the active path in context: spec -> roadmap -> current phase -> current task.
4. Verify every completed node against the original spec.

It includes:

• a Planning Gate before execution starts
• active phase/task/subtask pointers
• scope-change protocol
• 3-strike error protocol
• findings and progress logs
• requirement-level compliance tables
• templates and an example planning tree

Important note: this skill assumes an approved spec already exists. If there is no spec yet, use a companion workflow such as spec-driven-development first, then use this skill for decomposition, execution, resume, and verification.

Install path:

codex plugin marketplace add johnnykor82/spec-driven-planning

I would love feedback from people doing longer Codex sessions: where the protocol feels too strict, where it saves context, and where the templates should be simpler.