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 modules or decision hard reverse. Trigger: /architect.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when the user says "commit", "/commit", "save progress", or asks to land working changes on a feature branch. ocx-mcp working-phase posture — minimises commit count, can amend rolling Checkpoints, offers a one-time PR prompt. For pre-merge cleanup, use `/finalize`.
Use when the user says "finalize", "/finalize", "prepare this branch for main", "clean up history", "squash the branch", or landing a branch on `main`. Rewrites Checkpoint working-phase commits into clean Conventional Commits before fast-forward merge. Flags: `--squash-all`, `--dry-run`.
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 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 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.
| 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 modules or decision hard reverse. Trigger: /architect. |
Role: system design, technical specs, high-level architecture decisions for ocx-mcp.
worker-architecture-explorer. Map current module state, find reusable code, trace cross-module flows.claude/rules/subsystem-mcp.md. Read architecture explorer findingsworker-researcher for trending tools, proven patterns, industry adoption. Check/persist .claude/artifacts/research_*.mdsubsystem-mcp.md is the design contract to extend rather than an implemented subsystem.claude/templates/artifacts/.claude/rules/subsystem-mcp.md — MCP server architecture (intended module map: transport / capabilities / lifecycle), error model, dependency model, where features land. Source of truth and design contract; the server is an early scaffold (not yet implemented).claude/rules/quality-core.md — design principles (SOLID/DRY/KISS/YAGNI), severity tiers.claude/rules/quality-rust.md — Rust-specific design constraints (ownership, async/Tokio, error types)README.md + CLAUDE.md — product positioning, repo map, dependency modelmcp__context7__resolve-library-id + docs query) — 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 Recordsdesign_spec_[component].md — component/feature design specsplan_[task].md — implementation plans (executable plans live in .claude/state/plans/)subsystem-mcp.md invariants/swarm-plan / /swarm-execute — after design approval, with plan artifact/swarm-review — for adversarial review of resulting diffs$ARGUMENTS