Start a new Codex session after installation so the bundled skills are available.
## Usage
Invoke a specific skill when you know the role you want:
```text
Use $planner to write the next implementer prompt for this feature.
Use $implementer with docs/prompts/chunk-03.md.
Use $validator to verify this chunk against the frozen API contract.
Use $orchestrator to run the staged implementation loop for this checklist.
```
The usual flow is:
1. Use `planner` to freeze scope, contracts, validation, and the next chunk.
2. Use `implementer` to execute only that chunk.
3. Use `validator` when runtime, UI, API, integration, or regression evidence is needed.
4. Use `orchestrator` when you want Codex to coordinate the loop across chunks.
## Notes
- The skills are intentionally separate. Keeping the roles separate makes the boundaries clearer and reduces accidental scope widening.
-`validator` reports evidence and risk. `planner` or `orchestrator` decides whether a chunk is accepted.
-`orchestrator` may commit accepted chunks only when the user explicitly authorizes commits.
- If the same skill names also exist as standalone local skills, Codex may show duplicates. After the plugin is installed and verified, remove or disable the standalone copies if you want only the plugin version.
After pushing marketplace changes, run `codex plugin marketplace upgrade arcana-codex-plugins`.
If this plugin changed, reinstall it with `codex plugin add staged-implementation@arcana-codex-plugins`, then start a new Codex session so updated skills are loaded.