Skip to content

Add Phasekeeper workflow skill#389

Open
coderdeep11 wants to merge 3 commits into
openai:mainfrom
coderdeep11:add-phasekeeper-skill
Open

Add Phasekeeper workflow skill#389
coderdeep11 wants to merge 3 commits into
openai:mainfrom
coderdeep11:add-phasekeeper-skill

Conversation

@coderdeep11
Copy link
Copy Markdown

@coderdeep11 coderdeep11 commented May 4, 2026

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.md operating rules
  • WORKFLOW.md process guidance
  • docs/boards/README.md as the active phase pointer
  • phase board and phase spec templates
  • PROGRESS.md as a concise handoff archive

The 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:

Use Phasekeeper to set up this repo.

The bundled initializer creates the workflow files if they do not already exist and skips existing files unless --force is used.

Validation

  • Validated the skill metadata with the local skill validator.
  • Compiled the bundled Python initializer.
  • Ran the initializer against a throwaway directory and confirmed it created the expected workflow files.
  • Ran git diff --check.

@coderdeep11 coderdeep11 requested a review from a team May 4, 2026 19:27
@coderdeep11 coderdeep11 changed the title Add Phasekeeper skill Add Phasekeeper workflow skill May 4, 2026
@coderdeep11
Copy link
Copy Markdown
Author

coderdeep11 commented May 4, 2026

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:

  • quick_validate.py skills/.curated/phasekeeper
  • python3 -m py_compile skills/.curated/phasekeeper/scripts/init_phasekeeper.py
  • initializer smoke test confirmed the expected scaffold files
  • git diff --check

Maintainer edits are enabled. If .curated is too strong for this workflow, I’m happy to move it or reduce scope.

@chatgpt-codex-connector
Copy link
Copy Markdown

@coderdeep11
Copy link
Copy Markdown
Author

@codex
Please review this PR for clarity, safety, validation, and whether Phasekeeper fits in .curated.

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.

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🎉

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant