The Core Workflow
Small, focused skills for taking a feature from investigation to runtime proof.
The core workflow is a sequence of independent skills. Each skill owns one job, produces one explicit result, and stops before the next responsibility begins.
request
-> analyze
-> plan
-> implement
-> code-review
-> verify
These core skills are included in Premium. In Codex, use $skill-name instead
of /skill-name. The free bundle includes Apex.
Available stages
| Skill | Produces | Stops before |
|---|---|---|
analyze | Evidence, constraints, risks, and acceptance criteria. | Planning or editing. |
plan | An implementation-ready plan, with an optional GitHub issue. | Implementation. |
implement | The scoped change and relevant static checks. | Runtime proof. |
code-review | Separate Spec and Standards verdicts. | Runtime verification. |
verify | Current proof for every acceptance criterion. | Completion while anything is unproven. |
code-debug | A reproduced root cause, regression coverage, and a verified fix. | Guessing without a red-capable loop. |
Minimal by design
The skills do not duplicate each other. analyze does not create a plan,
implement does not claim runtime proof, and code-review does not replace
verify. The agreed plan is the shared source of truth. A GitHub issue is optional for
focused work and is read in full when supplied.
Use a skill directly when only one stage is needed:
/analyze investigate slow navigation
/plan use the current analysis
/implement https://github.com/owner/repo/issues/123
/code-review issue 123 since origin/main
/verify issue 123
/code-debug reproduce the intermittent save failure
Flags
Core skills intentionally expose almost no workflow configuration. code-debug
accepts -a or auto to choose safe reversible debugging decisions without
pausing. Automation across the complete sequence belongs to apex and
oneshot, documented under Advanced.