Menu
Admit design evidence and turn an Agent mission into a coherent Stage and authority architecture.
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
Assess an existing Agent version and design a frozen, independent evaluation specification.
Use only when Codex is explicitly asked to create, take over, assess for evolution, or improve an OPL-compatible Agent, including its architecture, prompts, skills, contracts, evaluations, or authority boundaries. Do not use because OMA was mentioned or @-mentioned, another Agent is producing a deliverable, or a deliverable validator, render, or QA check failed.
Diagnose an exact OPL EvidenceBundle without taking evaluator or runtime authority.
Produce an evidence-bound complete next AgentBlueprint and semantic change set.
| name | oma-design-basis-architecture |
| description | Admit design evidence and turn an Agent mission into a coherent Stage and authority architecture. |
Normalize mode, exact target identity, objective, acceptance criteria, non-goals, constraints, and source refs. A create request has no target version; takeover and improve requests bind one exact target version. Distinguish source-derived facts, target-owner requirements, assumptions, and reusable design patterns. Admit only traceable design claims.
Assign one major open semantic judgment to each Stage. Split when owner, knowledge source, quality gate, artifact contract, failure route, or handoff differs. Model deterministic generation and validation as Stage-internal obligations, without executing or materializing them in OMA. Return semantic refs and policies, never physical paths or execution instructions.
