Agent Plugin Architect
Design or audit the smallest coherent packaged-plugin control plane for Codex
and Claude Code. Treat Codex as the first-class target and preserve a single
shared Skill tree when both hosts can discover it without weakening Codex.
Route The Work
- Confirm that the request explicitly concerns packaged agent-plugin
architecture. Repo-local
AGENTS.md or .agents/skills work belongs to
agents-architect; ordinary plugin code or documentation has no Axiom
route solely because it lives in a plugin repository.
- Inventory the package before editing. Read
references/package-inventory.md.
- For a read-only audit of one packaged release candidate, read
references/release-readiness.md. It classifies impact, version and runtime
identity, local and remote evidence, and the one next decision, then stops
before every mutation phase.
- Define route ownership and trigger boundaries with
references/route-and-trigger-contracts.md.
- For shared Skill structure and direct discovery, read
references/packaged-skill-architecture.md.
- For startup hooks, untrusted content, credentials, or runtime effects, read
references/hooks-and-trust-boundaries.md.
- For manifests, wrappers, and Codex/Claude Code parity, read
references/cross-host-packaging.md.
- For routing cases, context cost, or host observations, read
references/evaluation-and-evidence.md.
- Before completion, read
references/validation-reporting.md.
Load only references needed for the active phase. A request may compose this
route with at most one other Axiom route when both contracts are independently
necessary. An explicit usage-cost goal may add optimize-codex-usage;
retrospective review may add review-axiom-task. Git submission, installation,
publication, deployment, and consequential external effects remain separate
active phases and select their owning route instead of inheriting authority
from this Skill.
Deliverable
Return the package inventory, route and trust decisions, changed surfaces,
validation evidence, compatibility class, and every host or lifecycle check
that is NOT-RUN or UNAVAILABLE. File presence and static parity are not
host execution evidence.
1---2name: agent-plugin-architect3description: Design, initialize, audit, migrate, maintain, or evaluate a packaged Codex or Claude Code plugin's shared Skills, route ownership, manifests, marketplace wrappers, hooks, and version-bound compatibility evidence. Use only for explicit packaged agent-plugin architecture work. Do not use for repository-local AGENTS.md or .agents/skills systems, ordinary source-code or documentation work merely because it is in a plugin repository, host installation, publication, deployment, or Git submission.4---56# Agent Plugin Architect78Design or audit the smallest coherent packaged-plugin control plane for Codex9and Claude Code. Treat Codex as the first-class target and preserve a single10shared Skill tree when both hosts can discover it without weakening Codex.1112## Route The Work13141. Confirm that the request explicitly concerns packaged agent-plugin15 architecture. Repo-local `AGENTS.md` or `.agents/skills` work belongs to16 `agents-architect`; ordinary plugin code or documentation has no Axiom17 route solely because it lives in a plugin repository.182. Inventory the package before editing. Read19 `references/package-inventory.md`.203. For a read-only audit of one packaged release candidate, read21 `references/release-readiness.md`. It classifies impact, version and runtime22 identity, local and remote evidence, and the one next decision, then stops23 before every mutation phase.244. Define route ownership and trigger boundaries with25 `references/route-and-trigger-contracts.md`.265. For shared Skill structure and direct discovery, read27 `references/packaged-skill-architecture.md`.286. For startup hooks, untrusted content, credentials, or runtime effects, read29 `references/hooks-and-trust-boundaries.md`.307. For manifests, wrappers, and Codex/Claude Code parity, read31 `references/cross-host-packaging.md`.328. For routing cases, context cost, or host observations, read33 `references/evaluation-and-evidence.md`.349. Before completion, read `references/validation-reporting.md`.3536Load only references needed for the active phase. A request may compose this37route with at most one other Axiom route when both contracts are independently38necessary. An explicit usage-cost goal may add `optimize-codex-usage`;39retrospective review may add `review-axiom-task`. Git submission, installation,40publication, deployment, and consequential external effects remain separate41active phases and select their owning route instead of inheriting authority42from this Skill.4344## Deliverable4546Return the package inventory, route and trust decisions, changed surfaces,47validation evidence, compatibility class, and every host or lifecycle check48that is `NOT-RUN` or `UNAVAILABLE`. File presence and static parity are not49host execution evidence.
wheakerd