Add Phasekeeper workflow skill#389
Conversation
|
Hi maintainers, adding a bit of context so this is easier to review. Phasekeeper is a board-first workflow skill for long-running Codex projects; the goal here is a small, self-contained catalog entry that scaffolds and operates the workflow without external services. I pushed two small follow-ups after opening the PR: one softens the commit guidance so the skill respects repo policy and operator authorization, and one tightens the trigger description so implicit invocation is narrower. Current validation on the latest branch:
Maintainer edits are enabled. If |
|
Note To use Codex here, create a Codex account and connect to github. |
|
@codex This skill is meant to help Codex manage long-running projects with phase boards, specs, verification logs, and clean handoffs. I also pushed two small follow-ups after opening the PR: one to avoid implying Codex should commit without repo/operator permission, and one to make the trigger description narrower. I’m happy to adjust the scope or move it if needed. |
|
Codex Review: Didn't find any major issues. 🎉 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
This adds Phasekeeper, a board-first workflow skill for long-running Codex projects.
Phasekeeper helps Codex keep durable project state across sessions by scaffolding and following:
AGENTS.mdoperating rulesWORKFLOW.mdprocess guidancedocs/boards/README.mdas the active phase pointerPROGRESS.mdas a concise handoff archiveThe skill is intentionally conservative: implementation starts from an approved spec and active board, issues are logged on the board, verification commands are recorded, and session closeout leaves an explicit next step.
Why this belongs in the catalog
This is useful for users who run multi-session coding projects with Codex and need more structure than chat history. It packages a repeatable workflow that can be installed into any repo without external services or authentication.
How to try it
After installing the skill, ask Codex:
The bundled initializer creates the workflow files if they do not already exist and skips existing files unless
--forceis used.Validation
git diff --check.