Menu
Use when task involve design spec, ADR, one-way-door decision, or evaluate trade-offs between architectural approaches. Invoke before implementation when requirements span subsystems or decision hard reverse. Trigger: /architect.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a diff or PR is too big to review by eye and the question is "what should I actually look at" โ sorts each changed line into wire / CLI / API / logic / test / doc tiers, then opens a clickable local page with the real hunks. A reading order, never a verdict.
Use to implement a plan artifact from `/swarm-plan`, or a free-text implementation task with contract-first TDD + Review-Fix Loop. Tier (`low | auto | high | max`) scales builder model, loop rounds, review breadth, and Codex code-diff gate.
Use for branch, PR, or diff review before landing on main. Tier (`low | auto | high | max`) scales breadth from single reviewer to adversarial panel with architect + SOTA-gap + Codex cross-model gate. Triggers: "review", "/swarm-review", pre-merge checks.
Use when the user says "commit", "/commit", "save progress", or asks to land working changes on a feature or worktree branch. OCX working-phase posture โ minimises commit count, can amend rolling Checkpoints, offers a one-time PR prompt. For pre-merge cleanup, use `/finalize`.
Use for feature planning, task decomposition, multi-perspective research, or ADR scaffolding. Tier (`low | auto | high | max`) scales research depth, architect model, and review breadth. Canonical research primitive for AI config / ADR work.
Use when the user says "codex review", "/codex-adversary", "adversarial review", "cross-model review", or asks for a different-model second opinion on a diff or plan artifact. Complements `/swarm-review` via Codex-CLI. Scopes: code-diff (default), plan-artifact (gate for `/swarm-plan`).
| name | architect |
| description | Use when task involve design spec, ADR, one-way-door decision, or evaluate trade-offs between architectural approaches. Invoke before implementation when requirements span subsystems or decision hard reverse. Trigger: /architect. |
Role: system design, technical specs, high-level architecture decisions for OCX.
worker-architecture-explorer. Map current module state, find reusable code, trace cross-module flowsworker-researcher for trending tools, proven patterns, industry adoption. Check/persist .claude/artifacts/research_*.md.claude/templates/artifacts/.claude/rules/arch-principles.md โ crate layout, design principles, end-to-end command flow, ADR index, where features land (auto-load on Rust files).claude/rules/product-context.md โ OCX positioning, differentiators, competitive landscape, full product vision.claude/rules/product-tech-strategy.md โ golden-path tech choices.claude/rules/subsystem-*.md โ per-subsystem invariants and module maps (load those match design area)mcp__context7__resolve-library-id + get-library-docs) โ current crate API shape when design decision hinge on "what does crate X look like today". Training-data API knowledge decay fast. Fallback: WebFetch of docs.rs.mcp__github__*) โ structured lookup of issues, PRs, releases during discovery. Fallback: gh CLI.Create in .claude/artifacts/ per CLAUDE.md naming:
adr_[topic].md โ Architecture Decision Recordssystem_design_[component].md โ system designsplan_[task].md โ implementation plans$ARGUMENTS