Runs a systematic debugging workflow for bugs, regressions, flaky behavior, and performance surprises. Use when something is broken, failing, throwing, slow, flaky, or when the user asks to debug or diagnose a specific problem.
Clarifies vague feature, refactor, or product plans against repo docs, domain language, ADRs, and current code. Use when a plan needs questioning, terminology alignment, trade-off discovery, or documentation-aware design before PRD, issues, prototype, or TDD work.
Creates a concise local handoff document so Codex work can resume in a later session or another local context. Use when ending a session, pausing work, transferring context, or summarizing current progress without duplicating existing PRDs, issues, tests, or plans.
Produces a local-first architecture audit for codebases that feel hard to change, test, or navigate. Use when the user wants refactor opportunities, shallow module detection, interface simplification, dependency analysis, or a sequenced architecture improvement plan without immediate code edits.
Plans and creates approved throwaway prototypes for UI, state model, or business logic questions before production implementation. Use when the user wants to test an idea, compare UI options, validate behavior, or explore uncertainty without committing to production code.
Establishes repo-local configuration for the Codex Engineering Workflow Pack. Use when starting the pack in a repo, when workflow skills lack project context, or when issue/docs/test/handoff locations need to be discovered and recorded.
Guides feature work and bug fixes through a red-green-refactor loop using vertical slices. Use when the user wants test-first development, acceptance criteria implemented safely, or one behavior delivered at a time.
Breaks a PRD, plan, or feature document into local-first vertical slice issues with clear implementation notes. Use when work needs to become independently implementable markdown issues before TDD, prototyping, or scoped execution.
Converts an existing conversation, clarified plan, or feature idea into a local-first PRD draft. Use when the user wants a PRD, product spec, requirements document, or durable feature plan before issue slicing or implementation.
Produces a read-only system map for an unfamiliar code area before changes begin. Use when the user needs broader context, module relationships, caller/callee flow, domain language, ADR constraints, or test surface understanding without editing code.
AGENTS.md instructions for SetraTheXX/Codex-Engineering-Workflow-Pack, a project described as: Local-first engineering workflow toolkit for Codex: skills, Coordinator Mode, worktree isolation, guarded dispatch, and parallel agent workflows.
Turn a repository roadmap, plan, issue, PRD, progress file, or direct goal into a bounded CEWP workflow proposal with explicit scope, verification, budget, ownership, and approval. Use when the user asks to complete a multi-step roadmap with CEWP; recommend native Codex for simple low-risk work.
Turn a direct goal, issue, PRD, PLAN.md, or progress.md into one bounded CEWP supervised checkpoint and show its scope, verification, ownership, and budget before approval. Use when the user wants CEWP governance for work that benefits from checkpoints, recovery, independent review, or a receipt.
Inspect and recover the latest or selected CEWP supervised run, including generated progress, pauses, blockers, budgets, ownership, and safe resume actions without losing trusted evidence. Use when the user asks for status, interruption recovery, budget recovery, rollback, cancellation, or what to do next.
Approve, execute, verify, repair, continue, independently review, preview, or explicitly finalize the current CEWP supervised checkpoint through Core gates. Use when the user asks to run or continue an already proposed CEWP checkpoint.