Shared vocabulary and decision process for designing module interfaces and test seams. Use when Codex needs to decide where a seam belongs, judge whether a module is deep or shallow, design an interface that serves slicing and acceptance, or make code easier to test and navigate.
Maintain a repository's domain vocabulary and architecture decision records. Use when Codex needs to sharpen terminology, resolve ambiguous domain concepts, update CONTEXT.md, create ADRs, or support grill-with-docs, triage, TDD, diagnosis, or architecture work with durable domain language.
Clarify a feature, refactor, architecture idea, or product plan against existing code and domain docs. Use when requirements, terminology, constraints, or success signals are unclear before to-prd, to-issues, triage, or implementation, and Codex should update CONTEXT.md or ADRs only when domain terms or decisions crystallize.
Scan a codebase for architecture friction and deepening opportunities. Use when Codex needs to audit old code, find shallow modules, improve testability, identify seams before implementation, or report architecture blockers without directly changing product code.
Move issues, external PRs, new ideas, manual test feedback, existing-codebase audits, and regression reports through workflow triage states. Use when Codex needs to classify work, verify claims, detect already-implemented behavior, ask for missing info, create agent-ready briefs, or route changes before implementation.
Lightweight acceptance gate for completed slices, bug fixes, PRs, or implementation branches. Use when Codex needs to verify that work matches the originating issue or PRD, prove acceptance criteria and regression checks, decide pass/fail/blocked before handoff, or record acceptance evidence in GitHub, a PR, or local markdown.
Break a PRD, plan, spec, or parent issue into independently grabbable vertical-slice issues on the configured issue tracker. Use when Codex needs to convert a durable contract into implementation slices with acceptance and regression evidence requirements.
Turn already-clarified requirements, conversation context, plans, or codebase findings into a durable PRD on the configured issue tracker. Use when Codex needs to synthesize intent into a parent contract before slicing work, without reopening a full requirements interview.