@maestria/codex 0.3.2 → 0.4.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "maestria",
3
- "version": "0.3.2",
3
+ "version": "0.4.1",
4
4
  "description": "Maestria methodology for Codex CLI: specialist workflow skills, orchestration, and review contracts",
5
5
  "author": {
6
6
  "name": "agustinusnathaniel"
@@ -12,7 +12,7 @@
12
12
  "interface": {
13
13
  "displayName": "Maestria",
14
14
  "shortDescription": "Specialist workflow skills for Codex CLI",
15
- "longDescription": "A skills-only projection of Maestria's canonical agent methodology for Codex CLI. It provides specialist workflows, orchestration guidance, handoffs, bounded repair, and review contracts without claiming runtime enforcement.",
15
+ "longDescription": "Maestria's Codex CLI integration: namespaced specialist skills, native custom-agent roles, automatic orchestration guidance, handoffs, bounded repair, and review contracts. The host retains runtime and permission enforcement.",
16
16
  "developerName": "agustinusnathaniel",
17
17
  "category": "Developer Tools",
18
18
  "capabilities": ["Skills"],
package/CHANGELOG.md CHANGED
@@ -1,5 +1,25 @@
1
1
  # @maestria/codex
2
2
 
3
+ ## 0.4.1
4
+
5
+ ### Patch Changes
6
+
7
+ - [#269](https://github.com/agustinusnathaniel/maestria/pull/269) [`ef07bf7`](https://github.com/agustinusnathaniel/maestria/commit/ef07bf78a8e5f676c76b55680301bc7c839b68a9) Thanks [@agustinusnathaniel](https://github.com/agustinusnathaniel)! - Add conditional visual-evidence guidance for PR delivery: confirm the project targets GitHub with authenticated gh --attach support and an available capture tool before attaching a screenshot or short video for visual or behavioral changes. Vision is optional verification only, not a precondition.
8
+
9
+ - [#269](https://github.com/agustinusnathaniel/maestria/pull/269) [`ef07bf7`](https://github.com/agustinusnathaniel/maestria/commit/ef07bf78a8e5f676c76b55680301bc7c839b68a9) Thanks [@agustinusnathaniel](https://github.com/agustinusnathaniel)! - Add a global testing-judgment rule (test artifacts are opt-in, behavior over implementation shape, mocks only at external seams) and align reviewer and diagnose guidance with it.
10
+
11
+ ## 0.4.0
12
+
13
+ ### Minor Changes
14
+
15
+ - [#248](https://github.com/agustinusnathaniel/maestria/pull/248) [`93ff292`](https://github.com/agustinusnathaniel/maestria/commit/93ff292b83f5659b67af4889848de454d1661206) Thanks [@agustinusnathaniel](https://github.com/agustinusnathaniel)! - Add native Codex custom-agent templates, direct native marketplace installation, automatic primary-session orchestration guidance, CLI-managed model configuration, and safe update/uninstall handling.
16
+
17
+ ## Unreleased
18
+
19
+ - Add seven native `maestria-*` custom-agent TOML templates. The Maestria CLI installs them into Codex's native agents directory and preserves user model, reasoning, and service-tier settings across updates.
20
+ - Add an idempotent, marker-managed global Codex instruction block so the host-owned primary session activates the Maestria orchestrator and delegates through native roles automatically.
21
+ - Align the orchestrator guidance with Codex's native `agent_type` role selection.
22
+
3
23
  ## 0.3.2
4
24
 
5
25
  ### Patch Changes
package/INSTALL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Installing @maestria/codex
2
2
 
3
- > This package is a provisional projection spike, not a production support promise. It was verified against `codex 0.145.0` on 2026-08-13.
3
+ > Codex CLI support was verified against `codex 0.145.0` on 2026-08-26. This package targets Codex CLI plugin skills and native CLI installation; Codex desktop parity and runtime tool enforcement remain outside its scope.
4
4
 
5
5
  ## Prerequisites
6
6
 
@@ -27,7 +27,7 @@ Install the published projection and register it with Codex's native plugin mana
27
27
  npx maestria install codex
28
28
  ```
29
29
 
30
- The CLI downloads `@maestria/codex` from npm, creates a local marketplace under `~/.cache/maestria/codex-marketplace`, and runs `codex plugin add maestria@maestria`. Codex owns the installed plugin cache and enabled state.
30
+ The CLI downloads `@maestria/codex` from npm, creates a local marketplace under `~/.cache/maestria/codex-marketplace`, and runs `codex plugin add maestria@maestria`. Codex owns the installed plugin cache and enabled state. The CLI also installs the bundled native custom agents as `maestria-*.toml` under `$CODEX_HOME/agents/` (normally `~/.codex/agents/`) and adds a marked orchestration block to the active global `$CODEX_HOME/AGENTS.md` or `$CODEX_HOME/AGENTS.override.md` file. Existing instructions remain intact.
31
31
 
32
32
  Update or remove it with:
33
33
 
@@ -36,7 +36,22 @@ npx maestria update codex
36
36
  npx maestria uninstall codex
37
37
  ```
38
38
 
39
- The update path refreshes the npm package and reinstalls it because Codex CLI does not expose a separate plugin update command. Exact version pinning is not supported for this adapter.
39
+ The update path refreshes the npm package and reinstalls it because Codex CLI does not expose a separate plugin update command. It also refreshes the native agent TOMLs while preserving configured model, reasoning, and service-tier settings. Exact version pinning is not supported for this adapter.
40
+
41
+ ## Direct installation through Codex
42
+
43
+ The repository also publishes a Codex marketplace entry whose plugin source is the npm package. Install it with Codex's native marketplace and plugin commands:
44
+
45
+ ```bash
46
+ codex plugin marketplace add agustinusnathaniel/maestria
47
+ codex plugin add maestria@maestria
48
+ ```
49
+
50
+ This direct path installs the published plugin and its skills. `codex plugin add` consumes a `PLUGIN@MARKETPLACE` selector; it does not accept `@maestria/codex` as a bare npm argument. The Maestria CLI remains the full setup path because it additionally copies the bundled native agent TOMLs into `$CODEX_HOME/agents/` and manages the global orchestration instruction block. A direct Codex uninstall removes only the plugin:
51
+
52
+ ```bash
53
+ codex plugin remove maestria@maestria
54
+ ```
40
55
 
41
56
  ## Loading and testing
42
57
 
@@ -49,9 +64,28 @@ Codex loads plugins through a configured marketplace. Install the package from t
49
64
 
50
65
  These skills are advisory. The Codex runtime may still expose write-capable tools while a read-only specialist skill is active; do not treat the skill as a permission boundary.
51
66
 
67
+ 5. **Use native specialist agents**
68
+
69
+ The CLI-installed native roles are `maestria-adventurer`, `maestria-architect`, `maestria-builder`, `maestria-diagnose`, `maestria-planner`, `maestria-reviewer`, and `maestria-writer`. Ask Codex to delegate with the matching `agent_type`, for example `agent_type: "maestria-builder"`. Read-only roles use Codex's native `sandbox_mode = "read-only"`.
70
+
71
+ 6. **Automatic primary-session routing**
72
+
73
+ After `maestria install codex`, start a new Codex session. The managed global instruction block tells Codex's host-owned primary agent to use `$maestria:orchestrator`, load `$maestria:global-rules`, and delegate to the native `maestria-*` roles when appropriate. You can still invoke `$maestria:orchestrator` explicitly for a visible route, or use `$maestria:fein`, `$maestria:sonar`, and `$maestria:blitz` for workflow modes.
74
+
75
+ ## Native model configuration
76
+
77
+ The plugin manifest declares skills, while the Maestria CLI configures the native custom-agent model files and managed global orchestration instructions it installs:
78
+
79
+ ```bash
80
+ npx maestria configure codex --global --set builder=gpt-5.6-terra
81
+ npx maestria configure codex --project --set reviewer=gpt-5.6-luna
82
+ ```
83
+
84
+ Global files are written under `~/.codex/agents/`; project files are written under `.codex/agents/`. Existing TOML is edited surgically. Read-only roles also receive Codex's native `sandbox_mode = "read-only"` when a new custom-agent file is created.
85
+
52
86
  ## Scope deliberately excluded
53
87
 
54
- This projection does not write Codex configuration, register a model, add MCP, or ship lifecycle hooks. It also does not claim Codex desktop parity.
88
+ The plugin manifest does not itself declare agents, write `config.toml`, register a model, add MCP, or ship lifecycle hooks. The CLI installs native agent files, manages a marked block in Codex's global instruction file, and exposes model configuration as an explicit separate operation. The package also does not claim Codex desktop parity.
55
89
 
56
90
  ## Updating generated content
57
91
 
package/README.md CHANGED
@@ -1,12 +1,12 @@
1
1
  # @maestria/codex
2
2
 
3
- A provisional Codex CLI package that ships Maestria's agent methodology as namespaced `$maestria:*` skills.
3
+ A Codex CLI package that ships Maestria's agent methodology as namespaced `$maestria:*` skills and native custom-agent roles.
4
4
 
5
5
  > This package is part of the Maestria project. See [VISION.md](https://github.com/agustinusnathaniel/maestria/blob/main/VISION.md) for the project vision, motivation, and scope.
6
6
 
7
7
  ## Status / Support Boundary
8
8
 
9
- `Provisional` - verified against Codex CLI 0.145.0 on 2026-08-13; not a production support promise, and no Codex desktop parity is claimed. Reverify host marketplace and skills behavior when upgrading Codex.
9
+ Verified against Codex CLI 0.145.0 on 2026-08-26. This package targets Codex CLI plugin skills and native CLI installation. Codex desktop parity and runtime tool enforcement remain outside this package.
10
10
 
11
11
  ## Installation
12
12
 
@@ -20,17 +20,29 @@ npx maestria uninstall codex
20
20
 
21
21
  The CLI installs and updates the plugin through Codex's `plugin add` flow. Codex CLI exposes no plugin update command, so `maestria update codex` removes and re-adds the plugin. Exact version pinning is not available. See [INSTALL.md](https://github.com/agustinusnathaniel/maestria/blob/main/packages/codex/INSTALL.md) for the full checklist and verification.
22
22
 
23
+ The published package is also available through the repository's native Codex marketplace:
24
+
25
+ ```bash
26
+ codex plugin marketplace add agustinusnathaniel/maestria
27
+ codex plugin add maestria@maestria
28
+ ```
29
+
30
+ That direct path installs the plugin and skills. Use `npx maestria install codex` when you also want the native agent TOMLs and automatic global orchestration setup.
31
+
23
32
  ## What It Provides
24
33
 
25
34
  - **14 namespaced skills** - `$maestria:global-rules`, `$maestria:orchestrator`, the 7 specialists (adventurer, architect, builder, diagnose, planner, reviewer, writer), `$maestria:handoff`, `$maestria:iteration-limits`, and the workflow modes `$maestria:fein`, `$maestria:sonar`, `$maestria:blitz`.
35
+ - **7 native custom agents** - the Maestria CLI installs `maestria-*` agent TOMLs into Codex's native `$CODEX_HOME/agents/` directory, with read-only sandbox settings for reconnaissance, architecture, planning, and review roles.
36
+ - **Automatic orchestration** - the Maestria CLI installs a marked global Codex instruction block that activates the orchestrator workflow in the primary session and routes specialist work to the native roles.
26
37
  - **Maestria CLI compatibility** - install, status, check, update, and uninstall through the CLI.
38
+ - **Native model configuration** - `maestria configure codex` can create or update Codex custom-agent TOML files without overwriting unrelated agent settings.
27
39
 
28
40
  ## Support / Platform Notes
29
41
 
30
42
  - Workflow modes ship as skills, not slash commands.
31
43
  - Read-only specialist boundaries are documented guidance, not tool enforcement; Codex's own sandbox, approvals, and hook trust controls remain the host boundary.
32
- - Ships no hooks, MCP servers, model configuration, or `AGENTS.md` writer.
33
- - Support remains provisional until the pinned Codex CLI behavior and the marketplace/plugin install flow are reverified.
44
+ - The plugin manifest declares skills; the companion CLI installs native agent TOMLs and a marked global instruction block, preserves model/reasoning/service-tier settings across updates, and removes only Maestria-owned content on uninstall.
45
+ - `maestria install codex` provides automatic routing for normal sessions. Direct plugin installation still supports explicit `$maestria:orchestrator` activation but does not modify global instructions.
34
46
 
35
47
  ## Documentation and Changelog
36
48
 
@@ -0,0 +1,7 @@
1
+ name = "maestria-adventurer"
2
+ description = "Maestria codebase reconnaissance specialist for mapping unfamiliar code and tracing execution paths."
3
+ developer_instructions = """
4
+ Load the $maestria:adventurer skill before acting.
5
+ Stay in exploration mode: gather verified context, trace the real execution path, and return a concise evidence-backed handoff to the parent agent. Do not implement or edit files.
6
+ """
7
+ sandbox_mode = "read-only"
@@ -0,0 +1,7 @@
1
+ name = "maestria-architect"
2
+ description = "Maestria architecture specialist for comparing approaches, boundaries, and trade-offs."
3
+ developer_instructions = """
4
+ Load the $maestria:architect skill before acting.
5
+ Evaluate viable approaches with explicit trade-offs and record the decision inputs. Return a concise recommendation and implementation handoff. Do not implement or edit files.
6
+ """
7
+ sandbox_mode = "read-only"
@@ -0,0 +1,6 @@
1
+ name = "maestria-builder"
2
+ description = "Maestria focused implementation specialist for one atomic, verifiable unit of work."
3
+ developer_instructions = """
4
+ Load the $maestria:builder skill before acting.
5
+ Implement the requested atomic change, keep unrelated files untouched, validate the changed behavior, and return a concise evidence-backed handoff.
6
+ """
@@ -0,0 +1,6 @@
1
+ name = "maestria-diagnose"
2
+ description = "Maestria diagnosis specialist for tracing regressions from symptoms to root cause and prevention."
3
+ developer_instructions = """
4
+ Load the $maestria:diagnose skill before acting.
5
+ Reproduce and minimize the failure, trace the owning path, identify the root cause, and add or describe regression evidence before proposing a bounded repair.
6
+ """
@@ -0,0 +1,7 @@
1
+ name = "maestria-planner"
2
+ description = "Maestria planning specialist for sequencing complex work with verification and rollback criteria."
3
+ developer_instructions = """
4
+ Load the $maestria:planner skill before acting.
5
+ Produce a phased, implementation-ready plan with dependencies, acceptance evidence, and rollback points. Do not implement or edit files.
6
+ """
7
+ sandbox_mode = "read-only"
@@ -0,0 +1,7 @@
1
+ name = "maestria-reviewer"
2
+ description = "Maestria independent reviewer for correctness, security, performance, and missing-test risks."
3
+ developer_instructions = """
4
+ Load the $maestria:reviewer skill before acting.
5
+ Review independently after implementation, lead with concrete material findings, and return a verdict with evidence. Do not fix issues or edit files.
6
+ """
7
+ sandbox_mode = "read-only"
@@ -0,0 +1,6 @@
1
+ name = "maestria-writer"
2
+ description = "Maestria documentation specialist for READMEs, API docs, architecture records, and changelogs."
3
+ developer_instructions = """
4
+ Load the $maestria:writer skill before acting.
5
+ Write clear, structured documentation grounded in the code and project conventions, then return a concise handoff with the files and validation performed.
6
+ """
@@ -0,0 +1,18 @@
1
+ <!-- maestria:codex-orchestrator:start -->
2
+
3
+ ## Maestria orchestration
4
+
5
+ For software-engineering tasks, use `$maestria:orchestrator` as the workflow dispatcher. Treat this Codex session as the orchestrator: load `$maestria:global-rules` once, choose the smallest safe route, and delegate specialist work when another perspective or parallel work materially improves the result.
6
+
7
+ Use the native Maestria custom agents when they are installed. Delegate with the matching `agent_type`:
8
+
9
+ - `maestria-adventurer`: codebase reconnaissance
10
+ - `maestria-architect`: architecture and boundary decisions
11
+ - `maestria-builder`: atomic implementation
12
+ - `maestria-diagnose`: root-cause analysis
13
+ - `maestria-planner`: phased implementation planning
14
+ - `maestria-reviewer`: independent review after meaningful implementation
15
+ - `maestria-writer`: documentation
16
+
17
+ Keep maker/checker separation explicit. Route simple, low-risk requests directly, and do not add ceremony when it does not improve the outcome. User instructions and repository-local instructions take precedence over this workflow.
18
+ <!-- maestria:codex-orchestrator:end -->
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@maestria/codex",
3
- "version": "0.3.2",
3
+ "version": "0.4.1",
4
4
  "private": false,
5
- "description": "Provisional Maestria skills projection for Codex CLI",
5
+ "description": "Maestria skills and native agent integration for Codex CLI",
6
6
  "keywords": [
7
7
  "ai",
8
8
  "codex",
@@ -24,6 +24,8 @@
24
24
  },
25
25
  "files": [
26
26
  ".codex-plugin",
27
+ "agents",
28
+ "instructions",
27
29
  "skills",
28
30
  "CHANGELOG.md",
29
31
  "INSTALL.md",
@@ -38,7 +40,7 @@
38
40
  "devDependencies": {
39
41
  "@types/node": "^26.2.0",
40
42
  "typescript": "^7.0.2",
41
- "vite-plus": "0.2.9",
43
+ "vite-plus": "0.3.0",
42
44
  "vitest": "4.1.11"
43
45
  },
44
46
  "engines": {
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: adventurer
3
2
  description: Codebase reconnaissance workflow for mapping unfamiliar code, tracing call chains, and reporting verified context without implementing changes.
3
+ name: adventurer
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: architect
3
2
  description: Architecture decision workflow for comparing implementation approaches, boundaries, threat models, and ADR decisions.
3
+ name: architect
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: blitz
3
2
  description: Fast capability-aware Maestria route that skips optional ceremony without waiving safety or review.
3
+ name: blitz
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: builder
3
2
  description: Focused implementation workflow for one atomic, verifiable feature, fix, test, or refactor.
3
+ name: builder
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: diagnose
3
2
  description: Systematic regression-tracing workflow from symptom and error evidence to root cause, fix, and prevention.
3
+ name: diagnose
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -63,7 +63,7 @@ Fix the root cause with minimal changes:
63
63
 
64
64
  Prevent similar bugs:
65
65
 
66
- - Add/update regression tests
66
+ - Consider regression tests where a durable contract or plausible recurrence justifies them (per Global Rules testing judgment)
67
67
  - Consider linting rules to catch the pattern
68
68
  - Document the lesson in a knowledge artifact for future reference
69
69
 
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: fein
3
2
  description: "Full Maestria pipeline: reconnaissance, design, implementation, and independent review."
3
+ name: fein
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: global-rules
3
2
  description: Universal Maestria rules for evidence, safety, authorization, delegation, review, bounded repair, and branch discipline.
3
+ name: global-rules
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -18,6 +18,7 @@ Cross-platform behavior contract for outcomes, evidence, safety, delegation, rev
18
18
  - **!!! Match effort to stakes.** Use the smallest route, investigation, test set, and review depth that establishes acceptance; escalate only when uncertainty, impact, or complexity warrants it.
19
19
  - **!!! Prefer reuse over reinvention.** Check existing project code, dependencies, framework capabilities, and mature ecosystem solutions before custom infrastructure; weigh fit, maintenance, compatibility, security, and total cost when material.
20
20
  - **!!! Exhaust available evidence before asking.** Make material assumptions explicit, tag uncertain ones `[inferred]`, and proceed on ordinary ambiguity. Ship affected documentation and changesets with code when project policy requires them.
21
+ - **!!! Exercise testing judgment, not coverage.** New test files, fixtures, mocks, and test-only helpers are opt-in, never automatic: reuse existing suites first and prefer the cheapest verification that establishes acceptance (typecheck, lint, runtime or browser checks). Add tests only for durable contracts and plausible regressions; assert observable behavior, not implementation shape; mock only genuinely external seams (network, clock, randomness).
21
22
  - **!!! Keep output self-contained and professional.** Understand existing systems before adapting or deleting them, and never claim isolation, enforcement, or lifecycle control the runtime does not provide.
22
23
  - **!!! Human-facing output.** In all agent-authored text (responses, status updates, briefs, comments/docstrings, commit messages, PR titles/descriptions, and documentation), never emit Unicode U+2014 EM DASH. Prefer commas, colons, parentheses, or ASCII hyphen-minus (`-`). Preserve code syntax, intentional literals, quoted source text, and user-provided text. Scan authored output before handoff or delivery.
23
24
 
@@ -49,7 +50,7 @@ Default to one independent review and, only when blockers exist, one repair/re-r
49
50
 
50
51
  Safety and authorization override user intent, methodology, and brevity. Security, authentication, and permission boundaries are mandatory stops. Stop and obtain applicable authorization before changes that alter them, involve data migration or possible loss, impact production, are irreversible, create external side effects outside delegated scope, or involve consequential ambiguity after evidence is exhausted. Ordinary in-scope security defects may be repaired autonomously.
51
52
 
52
- The orchestrator owns continuation for implementation and delivery work until the outcome reaches its terminal artifact; incomplete todos, pending handoffs, or specialist messages saying "continue if needed" are not a user checkpoint. Routine delivery is autonomous. For implementation work, continue through validation, review, and delivery: when repository, branch, remote, ownership, and host capabilities support it, create or use a non-protected feature branch and continue through commit, push, and PR without asking whether to perform those steps - these are delivery mechanics, not approval checkpoints. Where supported, create a reviewable PR without ceremonial approval rather than stopping at a verified working tree; a delegated implementation outcome is complete only at its delivered state - reviewed changes on a pushed feature branch with an open PR. Never commit or push protected branches; inspect status, stage only intended files, and use logical conventional commits. Merge, release, and production operations remain separate authorization boundaries. Track task-owned background processes and stop and verify them before completion unless intentionally part of the requested result; never broadly kill unrelated or user-owned processes outside platform lifecycle controls. An explicitly authorized checkpoint may preserve unreviewed work but never authorizes shipping.
53
+ The orchestrator owns continuation for implementation and delivery work until the outcome reaches its terminal artifact; incomplete todos, pending handoffs, or specialist messages saying "continue if needed" are not a user checkpoint. Routine delivery is autonomous. For implementation work, continue through validation, review, and delivery: when repository, branch, remote, ownership, and host capabilities support it, create or use a non-protected feature branch and continue through commit, push, and PR without asking whether to perform those steps - these are delivery mechanics, not approval checkpoints. Where supported, create a reviewable PR without ceremonial approval rather than stopping at a verified working tree; a delegated implementation outcome is complete only at its delivered state - reviewed changes on a pushed feature branch with an open PR. Never commit or push protected branches; inspect status, stage only intended files, and use logical conventional commits. Before attaching visual PR evidence, confirm both preconditions: the project targets GitHub (GitHub remote with authenticated gh that supports media attachments, for example gh v2.99.0+ repeatable --attach on pr create, edit, and comment) and a capture tool is available (screenshot, screen-capture, or browser tool). When both hold and the change is visual or behavioral, capture a screenshot or short video at reasonable cost and attach it, preferring referenced paths with alt text (for example, --attach './after.png#Short alt text') within host size limits; skip when either check fails, when no display is available, or when review value is low. Vision is not required: when present, use it to verify the capture shows the intended state, otherwise describe the capture from the action taken and leave visual verification to the reviewer. Merge, release, and production operations remain separate authorization boundaries. Track task-owned background processes and stop and verify them before completion unless intentionally part of the requested result; never broadly kill unrelated or user-owned processes outside platform lifecycle controls. An explicitly authorized checkpoint may preserve unreviewed work but never authorizes shipping.
53
54
 
54
55
  ## Canonical Source Invariant
55
56
 
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: handoff
3
2
  description: Concise handoff contract for passing outcome, constraints, evidence, blockers, and next steps between workflow stages.
3
+ name: handoff
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: iteration-limits
3
2
  description: Verifiable termination and bounded repair guidance for loops, reviews, and repeated implementation attempts.
3
+ name: iteration-limits
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: orchestrator
3
2
  description: "Maestria workflow dispatcher for Codex CLI: route work, use specialist skills, preserve handoffs, and keep independent review explicit."
3
+ name: orchestrator
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -72,7 +72,7 @@ Modes are case-insensitive and per-turn.
72
72
 
73
73
  For implementation work, own the delivery path: inspect -> plan -> implement -> validate -> one independent review -> repair material blockers only when required -> targeted validation of repaired scope -> final verification -> commit -> push -> PR.
74
74
 
75
- **Routine delivery is autonomous.** When repository, branch, remote, ownership, and host capabilities support PR delivery, do not ask whether to create or use a feature branch, commit, push, or create a PR; complete the lifecycle without ceremonial approval. A delegated implementation outcome reaches its terminal artifact only when delivered: reviewed changes on a pushed feature branch with an open PR. Do not stop at a local diff, commit, pushed branch, or `PR pending`, and never treat "not requested" as a reason to withhold routine delivery. Merge, release, and production actions remain separate authorization boundaries.
75
+ **Routine delivery is autonomous.** When repository, branch, remote, ownership, and host capabilities support PR delivery, do not ask whether to create or use a feature branch, commit, push, or create a PR; complete the lifecycle without ceremonial approval. A delegated implementation outcome reaches its terminal artifact only when delivered: reviewed changes on a pushed feature branch with an open PR. Do not stop at a local diff, commit, pushed branch, or `PR pending`, and never treat "not requested" as a reason to withhold routine delivery. When the change is visual or behavioral, attach a screenshot or short video only after confirming both preconditions: the project targets GitHub (GitHub remote with authenticated gh that supports --attach) and a capture tool is available (screenshot, screen-capture, or browser tool); skip when either check fails, when no display is available, or when cost outweighs review value. Vision is not required: use it to verify the capture when present, otherwise describe the capture from the action taken. Merge, release, and production actions remain separate authorization boundaries.
76
76
 
77
77
  The parent session owns continuation until the selected implementation outcome reaches its terminal artifact. Incomplete todos or specialist handoffs are not user checkpoints: take or delegate the next bounded action. A failed or cancelled delegation is transport trouble, not a verdict - retry once with an adjusted brief before reporting a structured blocker; user-initiated or intentional platform cancellation is terminal. Research-only, planning-only, explicitly read-only, `sonar`, and host-blocked routes terminate at their requested artifact or exact blocker. Safety, authorization, ambiguity, and host-capability boundaries always take precedence.
78
78
 
@@ -101,7 +101,11 @@ Use the namespaced skills below as the specialist workflow profiles:
101
101
  | `$maestria:reviewer` | Independent quality review | post-implementation validation or explicit review |
102
102
  | `$maestria:writer` | Documentation | README, changelog, API docs, or structured prose |
103
103
 
104
- Codex supports subagent workflows, but a skill does not create or enforce a custom subagent role. Ask Codex to delegate when parallel or independent work benefits from it, and keep the maker/checker boundary explicit in the prompts.
104
+ Codex supports subagent workflows. Skills provide the methodology, while the companion native agent pack provides role definitions with the `agent_type` names below. Keep the maker/checker boundary explicit in every handoff.
105
+
106
+ ### Native custom agents
107
+
108
+ The Maestria CLI installs the bundled native agent TOMLs into `$CODEX_HOME/agents/` using collision-resistant names: `maestria-adventurer`, `maestria-architect`, `maestria-builder`, `maestria-diagnose`, `maestria-planner`, `maestria-reviewer`, and `maestria-writer`. Use the corresponding `agent_type` when spawning a specialist, for example `agent_type: "maestria-builder"`. `maestria configure codex` updates their model settings without changing the role instructions. If the native pack is not installed, use the namespaced skills with Codex's built-in agents or explicit delegation prompts.
105
109
 
106
110
  ### Workflow-mode skills
107
111
 
@@ -109,4 +113,4 @@ Use `$maestria:fein` for the full route, `$maestria:sonar` for research-only wor
109
113
 
110
114
  ### Platform boundary
111
115
 
112
- This package contains no hooks, MCP server, installer, model configuration, or AGENTS.md writer. Skills and plugin loading are advisory capabilities, not security enforcement. Do not claim that this projection makes a role read-only, guarantees delegation, or enforces the Maestria methodology.
116
+ The Codex plugin manifest declares skills only; the companion Maestria CLI installs the package's native custom-agent TOML files, manages their model settings, and adds a marked global orchestration block to Codex's active AGENTS.md instructions. The package contains no hooks or MCP server. Skills and instruction guidance are advisory capabilities, not security enforcement; native custom-agent sandbox settings are the host's boundary. Do not claim that this integration overrides Codex's primary agent or enforces the Maestria methodology.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: planner
3
2
  description: Phased implementation planning workflow with dependencies, verification criteria, timelines, and rollback points.
3
+ name: planner
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: reviewer
3
2
  description: Independent code review workflow covering correctness, security, performance, maintainability, and quality gates.
3
+ name: reviewer
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -63,9 +63,9 @@ The initial general reviewer must give a verdict for every category. A specializ
63
63
 
64
64
  ### 7. Test Coverage
65
65
 
66
- - Are tests present for new functionality?
67
- - Do tests cover edge cases and error paths?
68
- - Are tests meaningful (not just checking implementation details)?
66
+ - Is meaningful regression risk covered proportionate to stakes (per Global Rules testing judgment)?
67
+ - Do tests cover edge cases and error paths where the contract demands it?
68
+ - Are tests meaningful (observable behavior, not implementation details)?
69
69
 
70
70
  ### 8. Assumption Validation
71
71
 
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: sonar
3
2
  description: Research-only Maestria route using read-only specialist skills, then stop before implementation.
3
+ name: sonar
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.
@@ -1,6 +1,6 @@
1
1
  ---
2
- name: writer
3
2
  description: Structured documentation workflow for READMEs, API docs, architecture documents, changelogs, and decision records.
3
+ name: writer
4
4
  ---
5
5
 
6
6
  <!-- Auto-generated from @maestria/core. Do not edit directly.