Codex Dispatch Loop

Reusable Codex Skill and project template for point-budgeted GitHub delivery. It turns a command such as 派工 10 點 into a dependency-aware execution loop:

plan → claim → Writer → independent Review → independent QA → closeout
                         ↑                         │
                         └──── FAIL / rework ─────┘

The loop ends only after every ticket in the dependency closure is individually closed, or a concrete external blocker is recorded. Dependencies control order; they do not merge ticket completion.

Contents

• SKILL.md — installable Codex Skill entrypoint.
• references/ — detailed policy, GitHub contract, role matrix, and bootstrap guidance.
• scripts/ — deterministic plan validation helpers.
• templates/project/ — files to copy into a new product repository and then fill with that project's PRD and commands.

New project usage

1. Copy the project templates into the target repository.

2. Replace the project name, PRD, GitHub repository/project, ticket plan, acceptance criteria, agent roles, and build/test commands.

3. Create the standard GitHub labels and issue fields.

4. Validate the dispatch plan:

   python3 scripts/validate_dispatch_plan.py \
     templates/project/dispatch-plan.example.json

5. Invoke the Skill with 派工 N 點 from the main Codex session. The main session remains the sole dispatcher and keeps the loop alive through Review/QA rework.

This repository is initialized for the public GitHub release eaiccc/codex-dispatch-loop.

Design boundary

The Skill and workflow are reusable. Product behavior, PRD scope, issue IDs, provider policies, secrets, runtime commands, open decisions, and GitHub repository identifiers are not copied between projects.