implementation-phase

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

1) Read project `AGENTS.md`, `codex.toml` (if present), and target work item folder `spec/features/<work-id>-<slug>/`.
   - `<work-id>` must use `S-<stream>-<nnn>` (example: `S-core-001`) for new work.
   - For legacy single-file specs, read the matching file under `spec/features/`.
2) Execute the implementation phase in this exact order for the same work item ID:
   - `Run $test-plan <work-id>`
   - `Run $write-tests <work-id>`
   - `Run $implement-feature <work-id>`
3) Validate outcomes after each step:
   - `test-plan`: `test-plan.md` is updated with AC-mapped cases and fixtures.
   - `write-tests`: tests are added/updated under `tests/`, the quick command is run, and the result is classified as passing, expected red, or unexpected failure.
   - Expected red is allowed only when each failure maps to an unimplemented AC, the failing signatures are recorded in `test-results.md`, and no previously passing behavior regressed.
   - `implement-feature`: AC checklist is completed, implementation checks pass, and work item docs include commands plus milestone smoke evidence when applicable.
4) Failure handling:
   - Continue from `write-tests` to `implement-feature` for a documented expected-red baseline.
   - Unexpected deterministic failures: run `debug-loop`.
   - Many simultaneous failures: run `failure-triage`.
   - Do not continue when failures are unrelated to unimplemented ACs, alter existing behavior, or cannot be explained.
5) End with a concise status summary:
   - completed steps
   - blockers/deferred items (if any)
   - next recommended command:
     - `Run $ship-feature <work-id> ...` when all steps are complete
     - otherwise `Run $debug-loop ...` with the failing signature

From rafaie/codex_home, Apache-2.0.

More from rafaie/codex_home