Codex Analytics Implementation Slices for Report Ordering
Split a Tiny-Swarm-World analytics change into verifiable work with explicit capability, persistence and report impact.
中文Install in Codex
Open Tiny-Swarm-World in Codex and read its AGENTS.md and QUALITY.md. Bring existing behavior and relevant checks.
- Review `.agents/skills/analytics-slice-workflow/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/analytics-slice-workflow/` in your project and save the reviewed file as `.agents/skills/analytics-slice-workflow/SKILL.md`.
- Start Codex from that project's root, then type `$analytics-slice-workflow` and select the matching skill.
Example task
Outline a sequence for this illustrative report order change.
{"feature":"report categories","oldOrder":"input order","expectedOrder":"alphabetical","affectsStorage":false,"fixture":["Zoo","Ant"]}What to check
Limit the first change to report ordering and assert `order=Ant,Zoo`. Record that the supplied case needs no storage model edit and verify the output.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should I check companion requirement or architecture guidance?
Use requirement guidance when ownership or requirements may drift. Use architecture guidance when boundaries or runtime behavior change.