Codex OpenUsage Feature Design with Dependencies and Tests
Clarify scope, user needs, and compatibility before tracing an OpenUsage change across core types, configuration, and terminal UI. Produce a design and an ordered task list.
中文Install in Codex
Codex with a pinned OpenUsage checkout. Keep the full specification and templates in docs/skills/design-feature/.
- Copy the entire pinned `.codex/skills/design-feature/` directory to `.agents/skills/design-feature/` in the target checkout.
- Open Codex in that checkout and invoke `$design-feature` with the example task and desired output.
- Keep `docs/skills/design-feature/` in the checkout. The entry reads its complete specification and reference files.
Example task
Invoke `$design-feature` in a practice branch to plan a local usage-time filter. Clarify defaults for existing settings and the TUI display boundary before writing the design.What to check
The design identifies core filtering, configuration compatibility, and terminal display responsibilities. Tasks record their prerequisites and associated tests.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why review existing design docs first?
An earlier design may already cover part of the proposal. Review it before deciding how to preserve or extend its constraints.