@massa-ai/codex-plugin 1.60.1 → 1.62.0

package/skills/agents/test-engineer/SKILL.md

@@ -1,41 +1,49 @@
 ---
 name: test-engineer
-description: Testing strategy agent. Generate unit, integration, edge-case, negative-scenario, and acceptance-coverage test plans. Default read-only; writes only test files when explicitly scoped with a disjoint write set. Triggers when a workflow needs a test strategy or test plan. Focuses only on testing; no production code changes outside test files.
+description: Testing agent. Plan unit, integration, edge-case, negative-scenario, and acceptance-coverage tests, run the findings-only tests audit lens, and implement test fixes from a saved tests audit report. Mode is selected by the capability packet (plan, audit, or fix). Audit mode writes nothing; plan mode is read-only unless explicitly scoped to write test files; fix mode writes only test files, always with a disjoint write set. Focuses only on testing; no production code changes outside test files.
 license: MIT
 metadata:
   author: Luiz Massa
-  version: "1.0.0"
-  model_tier: standard
+  version: "2.0.0"
   permission: write
 ---
 
 # Test Engineer Agent Skill
 
 ## Mission
-Generate a testing strategy that covers unit, integration, edge cases, negative scenarios, and acceptance criteria, and that catches the five distinct error classes a test suite must cover: business-logic errors, code no test touched, hardcoded-example brittleness, built-the-wrong-thing, and drift over time.
+Make a test suite catch the five distinct error classes it must cover — business-logic errors, code no test touched, hardcoded-example brittleness, built-the-wrong-thing, and drift over time — by planning the tests, auditing the ones that exist, and implementing test fixes.
 
 ## Responsibilities
-- Define unit test cases for core logic.
-- Define integration test cases for boundaries.
-- Identify edge cases and negative scenarios.
+- Run exactly one mode per dispatch, selected by the packet `mode` field: `plan`, `audit`, or `fix`.
+- Map acceptance coverage to spec criteria.
 - Design variation/property-style test cases — vary inputs beyond the fixture example (bounds, parameter changes) — technique-level, library-neutral.
-- Produce a test plan aligned with acceptance criteria.
-- Ensure acceptance coverage maps to spec criteria.
 
 ## Restrictions
+- Unknown `mode`: return `Blocked` naming the valid modes `plan`, `audit`, `fix`; a missing `mode` takes the default in Inputs.
 - Focus only on testing.
 - No production code changes outside test files.
-- Write only when scoped with a disjoint write set (same constraint as builder).
-- Never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
-- A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
+- Write only in `fix` mode (or `plan` mode when explicitly scoped to write test files), always with a disjoint write set (same constraint as `builder`); `audit` mode writes nothing.
+- Never weaken, skip, or delete an existing test assertion to make a suite pass.
+- Never load the `massa-ai` router skill; the dispatching workflow owns routing.
 
 ## Inputs
-- `scope`: the feature, module, or spec to test.
-- `inputs`: acceptance criteria, recalled facts, existing test conventions.
-- `permissions`: read-only default; write test files only when explicitly scoped + disjoint.
+- `mode`: `plan` | `audit` | `fix` (defaults to `plan`).
+- `lens`: `audit` mode only — one of `tests` (the single lens this charter runs; optional).
+- `scope`: the feature, module, spec, audit target, or saved-report findings to handle.
+- `inputs`: acceptance criteria, recalled facts, existing test conventions, the saved tests audit report (`fix` mode).
+- `permissions`: read-only default; write test files only when explicitly scoped + disjoint, and never in `audit` mode.
 - `sensors`: test runner commands, coverage tools.
 
-## Outputs
+## Modes
+
+### Mode: `plan`
+Testing strategy before or after implementation.
+
+- Define unit test cases for core logic and integration test cases for boundaries.
+- Identify edge cases and negative scenarios.
+- Produce a test plan aligned with acceptance criteria.
+
+Output:
 - Status: Complete | Partial | Blocked
 - Scope: test plan or test files written
 - Evidence: test commands, coverage output, acceptance-criteria mapping
@@ -43,27 +51,53 @@ Generate a testing strategy that covers unit, integration, edge cases, negative
 - Risks and skipped checks
 - Exact next step
 
+### Mode: `audit`
+Findings-only tests lens: coverage, regression protection, assertion quality, fixture reliability, variation, and missing deterministic sensors in a concrete target. Shares `references/audit-scope.md` (scope rules) and `references/audit-report-io.md` (report format) with every audit lens; per-lens reference `workflows/tests/tests-audit.md`. Read-only; no fix actions are taken.
+
+Output:
+- Status: Complete | Partial | Blocked
+- Scope: area audited + tests lens
+- Evidence: `path:line` pointers, test-run and coverage results
+- Findings: ranked list (severity, location, problem, suggestion) in the project audit-report format
+- Risks and skipped checks
+- Exact next step
+
+### Mode: `fix`
+Implement the confirmed findings of a saved tests audit report inside test files only, per `workflows/tests/tests-fix.md`.
+
+Output:
+- Status: Complete | Partial | Blocked
+- Scope: test files changed, per finding ID
+- Evidence: test commands and results, proof each new or changed test fails without the behavior it guards
+- Findings: per-finding implementation summary
+- Risks and skipped checks
+- Exact next step
+
 ## Invocation
 ### Use when
-- A workflow needs a test strategy before or after implementation.
-- Acceptance criteria exist and need coverage mapping.
+- A workflow needs a test strategy before or after implementation, or acceptance criteria need coverage mapping (`plan`).
+- A workflow needs a findings-only tests audit (`audit`).
+- The `tests-fix` workflow closes saved tests audit findings (`fix`).
 - The user asks for a test plan or test cases.
 
 ### Do not use when
-- No acceptance criteria or spec exists.
+- No acceptance criteria, spec, or audit report exists.
 - The task is a docs-only change with no testable behavior.
+- The fix needs production code changes (route to `builder`).
 
 ## massa-ai Integration
-- Context Firewall: summarize test output; return the plan and coverage map, not raw logs.
+- Context Firewall: summarize test output; return the plan, coverage map, or findings, not raw logs.
 - Verification Ladder: behavioral (tests) and file-integrity (no validation assets weakened).
 - Massa-ai Memory: suggest durable test-pattern memories only when a testing convention is established; main agent persists.
-- Synapse: none (test planning is not a repeated-search task).
-- References (paths relative to the `massa-ai` skill directory): `references/verification-ladder.md`, `references/code-annotation.md`, `references/root-cause-scripts.md`.
+- Synapse: none (test work is not a repeated-search task).
+- References (paths relative to the `massa-ai` skill directory): `references/verification-ladder.md`, `references/code-annotation.md`, `references/root-cause-scripts.md`, `references/audit-scope.md`, `references/audit-report-io.md`.
 
 ## Validation Sensors
 - Every acceptance criterion maps to at least one test case.
 - Edge cases and negative scenarios are enumerated.
 - Test runner commands are named.
+- `audit`: every finding has a `path:line` pointer and follows `references/audit-report-io.md`; no file written.
+- `fix`: the diff stays inside test files and the assigned write set; no validation asset weakened.
 
 ## Memory Boundary
-Suggest durable memories only when a reusable testing convention or fixture pattern is established. The main agent persists. Do not persist one-off test plans.
+Suggest durable memories only when a reusable testing convention or fixture pattern is established. The main agent persists. Do not persist one-off test plans or audit results.

package/skills/bootstrap/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bootstrap
-description: Inspect or toggle the massa-ai startup-contract rules (caveman, massa-ai-router, persona-router, dedupe-guardrails, plan-challenge, conversation-feedback, indexing-hygiene, english-code, code-comments) that the installed MASSA-AI.md delivers to this host. Use when the user asks which startup rules are active, asks to turn one on or off, or asks why a rule is or is not being applied. Do NOT use for editing the rule text itself (that is a massa-ai repository change, not a runtime toggle) and do NOT claim a toggle is live before the user restarts the host session.
+description: Inspect or toggle the massa-ai startup-contract rules (caveman, massa-ai-router, dedupe-guardrails, plan-challenge, conversation-feedback, indexing-hygiene, english-code, code-comments) that the installed MASSA-AI.md delivers to this host. Use when the user asks which startup rules are active, asks to turn one on or off, or asks why a rule is or is not being applied. Do NOT use for editing the rule text itself (that is a massa-ai repository change, not a runtime toggle) and do NOT claim a toggle is live before the user restarts the host session.
 license: MIT
 metadata:
   author: Luiz Massa
@@ -33,11 +33,10 @@ Run `bootstrap list` before any toggle, so the reported change is against a stat
 `--target <dir>` exists for scratch homes and requires `--yes`; it redirects only where the contract is *rendered*. The preference itself is always persisted to `~/.config/massa-ai/config.json`, so under a redirected target the CLI names both paths on stderr. Do not pass `--target` unless the user asked for a specific directory.
 
 ## The Rule Ids
-Exactly nine ids exist, and only these are accepted. There is no protected subset — every one of them can be switched both ways, including `massa-ai-router`.
+Exactly eight ids exist, and only these are accepted. There is no protected subset — every one of them can be switched both ways, including `massa-ai-router`.
 
 - `caveman` — keep communication compressed while preserving technical accuracy. Default: enabled.
 - `massa-ai-router` — load the massa-ai skill as the workflow router before substantive work. Default: enabled.
-- `persona-router` — select one cataloged specialist persona after massa-ai context is available. Default: enabled.
 - `dedupe-guardrails` — reuse already-loaded massa-ai context instead of bulk-loading workflows or references. Default: enabled.
 - `plan-challenge` — run The Fool as a post-plan challenge gate per the configured policy. Default: enabled.
 - `conversation-feedback` — emit chat-visible status updates for massa-ai workflow progress. Default: enabled.
@@ -45,7 +44,7 @@ Exactly nine ids exist, and only these are accepted. There is no protected subse
 - `english-code` — write generated code, identifiers, comments, and commit-facing artifacts in English regardless of conversational language. Default: enabled.
 - `code-comments` — require API doc blocks and rationale comments on generated code. Default: **disabled**.
 
-Never invent an id. An unrecognised id is refused before anything is read or written, and the error names the id and lists all nine — relay that list rather than guessing what the user meant.
+Never invent an id. An unrecognised id is refused before anything is read or written, and the error names the id and lists all eight — relay that list rather than guessing what the user meant.
 
 Disabling `massa-ai-router` is allowed and is the user's call. Say plainly that it removes the router which reads the startup contract, and that the recovery is this same CLI (`massa-ai-config bootstrap enable massa-ai-router`), which is a binary and not a rule, so it stays reachable.
 
@@ -67,7 +66,7 @@ On a dry run, say so and that no files changed.
 
 ## Restrictions
 - Never use an MCP tool for this surface; none exists. The CLI must keep working with the MCP server unreachable.
-- Never invent, abbreviate, or pluralise a rule id; use only the nine ids above, exactly as the engine lists them.
+- Never invent, abbreviate, or pluralise a rule id; use only the eight ids above, exactly as the engine lists them.
 - Never hand-edit a delivered `MASSA-AI.md`, a host's `AGENTS.md`, or `~/.config/massa-ai/config.json` to satisfy a toggle request — the engine owns those bytes, and a hand edit is overwritten by the next apply.
 - Never edit the rule text itself to satisfy a toggle request; that is a massa-ai repository change owned by a different workflow.
 - Never claim a toggle is live before the affected host's session restarts.

package/skills/{adr.md → create-adr.md}

@@ -1,13 +1,13 @@
 ---
-description: "Use this workflow to record a finalized or being-finalized architecture decision; route open options to rfc and implementation planning to tdd. — explicit massa-ai 'adr' workflow"
+description: "Use this workflow to record a finalized or being-finalized architecture decision; route open options to create-rfc and implementation planning to create-tdd. — explicit massa-ai 'create-adr' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `adr`.
+Explicit massa-ai workflow invocation: `create-adr`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `adr` under routing precedence 1 (explicit route) —
+route to workflow `create-adr` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/skills/{to-prd.md → create-prd.md}

@@ -1,13 +1,13 @@
 ---
-description: "Turn the current conversation into a PRD. Use when the user asks to create, synthesize, or convert existing discussion and codebase context into a Product Requirements Document without another interview. Do NOT use for implementation plans, architecture design docs, RFCs, TDDs, or discovery interviews that require new product questioning. — explicit massa-ai 'to-prd' workflow"
+description: "Turn the current conversation into a PRD. Use when the user asks to create, synthesize, or convert existing discussion and codebase context into a Product Requirements Document without another interview. Do NOT use for implementation plans, architecture design docs, RFCs, TDDs, or discovery interviews that require new product questioning. — explicit massa-ai 'create-prd' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `to-prd`.
+Explicit massa-ai workflow invocation: `create-prd`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `to-prd` under routing precedence 1 (explicit route) —
+route to workflow `create-prd` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/skills/{rfc.md → create-rfc.md}

@@ -1,13 +1,13 @@
 ---
-description: "Use this workflow when a significant technical, process, product, vendor, tool, or policy decision is still open and stakeholders need a structured proposal before committing. — explicit massa-ai 'rfc' workflow"
+description: "Use this workflow when a significant technical, process, product, vendor, tool, or policy decision is still open and stakeholders need a structured proposal before committing. — explicit massa-ai 'create-rfc' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `rfc`.
+Explicit massa-ai workflow invocation: `create-rfc`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `rfc` under routing precedence 1 (explicit route) —
+route to workflow `create-rfc` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/skills/{tdd.md → create-tdd.md}

@@ -1,13 +1,13 @@
 ---
-description: "Use this workflow to write a Technical Design Document once one product direction is selected and no unresolved API, data, security, or rollout decision blocks implementation. — explicit massa-ai 'tdd' workflow"
+description: "Use this workflow to write a Technical Design Document once one product direction is selected and no unresolved API, data, security, or rollout decision blocks implementation. — explicit massa-ai 'create-tdd' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `tdd`.
+Explicit massa-ai workflow invocation: `create-tdd`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `tdd` under routing precedence 1 (explicit route) —
+route to workflow `create-tdd` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/skills/{ticket.md → create-ticket.md}

@@ -1,13 +1,13 @@
 ---
-description: "Use this workflow to draft, review, create, or resume creation of Jira Epics, issues, or sub-tasks through Atlassian MCP, the only tracker and mutation path. — explicit massa-ai 'ticket' workflow"
+description: "Use this workflow to draft, review, create, or resume creation of Jira Epics, issues, or sub-tasks through Atlassian MCP, the only tracker and mutation path. — explicit massa-ai 'create-ticket' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `ticket`.
+Explicit massa-ai workflow invocation: `create-ticket`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `ticket` under routing precedence 1 (explicit route) —
+route to workflow `create-ticket` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/skills/massa-ai/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: massa-ai
-description: Default memory-backed workflow router for every coding, planning-before-coding, debugging, code review, refactoring, or implementation conversation. Always load it once per new coding session, select specialized workflows first, and use the general fallback otherwise. Handles massa-ai recall/search, durable memory, context compaction, handoff, audits, specs, ADR/RFC/TDD, and evidence gates. Do NOT use for generic non-coding chat or bulk-loading every workflow/reference.
+description: Default memory-backed workflow router for every coding, planning-before-coding, debugging, code review, refactoring, or implementation conversation. Always load it once per new coding session, select specialized workflows first, and work under the Core Contract without a workflow file otherwise. Handles massa-ai recall/search, durable memory, context compaction, handoff, audits, specs, ADR/RFC/TDD, and evidence gates. Do NOT use for generic non-coding chat or bulk-loading every workflow/reference.
 license: MIT
 metadata:
   author: Luiz Massa
@@ -35,6 +35,9 @@ Before reading any massa-ai file:
 
 - Every coding/planning task uses one stable `projectId` and
   `workflowSessionId`.
+- Sub-agents are dispatched by bare charter name (`builder`, `code-reviewer`, ...).
+  On the Claude plugin route, dispatch the plugin-namespaced `massa-ai:<name>`
+  so a same-named user or project agent cannot intercept the dispatch.
 - Start with `recall` for relevant prior decisions/patterns.
 - Default startup/context recall is budgeted: use `limit <= 3`,
   `minImportance >= 0.7`, and `types=["critical","decision","pattern"]`
@@ -113,7 +116,7 @@ Examples:
 - `feature-user-onboarding`
 - `refactor-auth-module`
 - `spec-billing-workflow`
-- `adr-postgres-migration`
+- `create-adr-postgres-migration`
 
 Resolve `projectId`:
 
@@ -143,9 +146,6 @@ current context already contains it.
 | `security-fix` | fix security audit report findings | `workflows/security/security-fix.md` |
 | `requirements-audit` | requirements/spec/acceptance/scope alignment findings | `workflows/requirements/requirements-audit.md` |
 | `requirements-fix` | fix requirements audit report findings | `workflows/requirements/requirements-fix.md` |
-| `maestro` | implement new Maestro mobile E2E flows | `workflows/maestro/maestro.md` |
-| `maestro-audit` | run and audit existing Maestro mobile E2E flows | `workflows/maestro/maestro-audit.md` |
-| `maestro-fix` | child-only fix for saved Maestro audit findings | `workflows/maestro/maestro-fix.md` |
 | `tests-audit` | test coverage/regression/assertion/flakiness findings | `workflows/tests/tests-audit.md` |
 | `tests-fix` | fix tests audit report findings | `workflows/tests/tests-fix.md` |
 | `bugs-audit` | findings-only bug discovery | `workflows/bugs/bugs-audit.md` |
@@ -159,34 +159,33 @@ current context already contains it.
 | `mobile-figma-audit` | compare an Android, iOS, or KMP UI implementation with a Figma design | `workflows/mobile-figma/mobile-figma-audit.md` |
 | `mobile-figma-fix` | fix saved mobile Figma findings | `workflows/mobile-figma/mobile-figma-fix.md` |
 | `refactor` | behavior-preserving structural cleanup | `workflows/refactor.md` |
-| `adr` | record a finalized decision | `workflows/adr.md` |
-| `rfc` | propose a significant change | `workflows/rfc.md` |
-| `tdd` | technical design / implementation plan | `workflows/tdd.md` |
-| `ticket` | draft and create Jira Epics, issues, and sub-tasks through Atlassian MCP | `workflows/ticket.md` |
+| `create-adr` | record a finalized decision | `workflows/create-adr.md` |
+| `create-rfc` | propose a significant change | `workflows/create-rfc.md` |
+| `create-tdd` | technical design / implementation plan | `workflows/create-tdd.md` |
+| `create-ticket` | draft and create Jira Epics, issues, and sub-tasks through Atlassian MCP | `workflows/create-ticket.md` |
 | `commit` | draft or create safe Conventional Commits with Jira branch prefixes and audit report exclusions | `workflows/commit.md` |
 | `the-fool` | direct challenge, red-team, pre-mortem, evidence audit | `workflows/the-fool.md` |
 | `judge-with-debate` | standalone multi-judge debate evaluation of user-supplied artifacts | `workflows/judge-with-debate.md` |
 | `pr-review` | review a hosted GitHub PR / GitLab MR and post findings via `gh`/`glab` | `workflows/pr-review.md` |
-| `discovery` | product brainstorming / problem-space thinking partner | `workflows/discovery.md` |
-| `to-prd` | turn the current conversation into a PRD without a new interview | `workflows/to-prd.md` |
+| `product-discovery` | product brainstorming / problem-space thinking partner | `workflows/product-discovery.md` |
+| `create-prd` | turn the current conversation into a PRD without a new interview | `workflows/create-prd.md` |
 | `skill-architect` | design and build a new skill through structured conversation | `workflows/skill-architect.md` |
 | `furps-refinement` | FURPS+ refinement of a PRD and/or ADR before implementation, with The Fool pre-validation and DoR coverage | `workflows/refinement/furps-refinement.md` |
-| `general` | coding work with no more specific workflow | `workflows/general.md` |
 
 Explicitly requested workflows win. Otherwise choose the most specific matching
 workflow. Use `exploration` only for explicitly read-only understanding or flow
-mapping; route to `general` when no route's precedence key above matches. Ask
+mapping; when no route's precedence key above matches, load no workflow file. Ask
 the user only when two or more routes match the same precedence tier; a single
 match or no match is resolved deterministically without asking.
 
 Deterministic routing precedence, first match wins:
 
 1. **Explicit route:** user names a massa-ai workflow, report family, saved finding type, or asks for a direct challenge.
-2. **Requested artifact:** ADR, RFC, TDD, Jira ticket, commit, session guide, audit report, implementation audit report, mobile Figma report, FURPS refinement report, PRD synthesized from the current conversation -> `to-prd` (explicit request only; refining an existing PRD stays `furps-refinement`), or new SKILL.md / skill design -> `skill-architect`.
-3. **Target type:** broken behavior/error -> `debug`; hosted PR/MR reference (number or URL) to review with posted findings -> `pr-review` (local working diff stays with audit routes); saved audit finding -> matching `*-fix`; implementation scope review -> `implementation-audit`; Maestro E2E/device automation target -> `maestro`, `maestro-audit`, or child-only `maestro-fix` before generic tests workflows; security/privacy/auth finding -> security workflow; tests/flakes/coverage finding -> tests workflow; supplied Figma/screenshot mobile UI design -> `design`; mobile Figma compare/audit -> `mobile-figma-audit`; saved `MFM-*` findings -> `mobile-figma-fix`.
-4. **Primary verb:** create/add/implement -> `feature` unless the concrete target is new Maestro flow work, which routes to `maestro`; restructure without behavior change -> `refactor`; inspect/understand only -> `exploration`; brainstorm/explore a product problem, idea, or direction with no concrete code target -> `discovery`; record selected decision -> `adr`; compare open options -> `rfc`; design settled implementation -> `tdd`; refine/quality-check an existing PRD or ADR document (not implementation auditing) -> `furps-refinement`.
+2. **Requested artifact:** ADR, RFC, TDD, Jira ticket, commit, session guide, audit report, implementation audit report, mobile Figma report, FURPS refinement report, PRD synthesized from the current conversation -> `create-prd` (explicit request only; refining an existing PRD stays `furps-refinement`), or new SKILL.md / skill design -> `skill-architect`.
+3. **Target type:** broken behavior/error -> `debug`; hosted PR/MR reference (number or URL) to review with posted findings -> `pr-review` (local working diff stays with audit routes); saved audit finding -> matching `*-fix`; implementation scope review -> `implementation-audit`; security/privacy/auth finding -> security workflow; tests/flakes/coverage finding -> tests workflow; supplied Figma/screenshot mobile UI design -> `design`; mobile Figma compare/audit -> `mobile-figma-audit`; saved `MFM-*` findings -> `mobile-figma-fix`.
+4. **Primary verb:** create/add/implement -> `feature`; restructure without behavior change -> `refactor`; inspect/understand only -> `exploration`; brainstorm/explore a product problem, idea, or direction with no concrete code target -> `product-discovery`; record selected decision -> `create-adr`; compare open options -> `create-rfc`; design settled implementation -> `create-tdd`; refine/quality-check an existing PRD or ADR document (not implementation auditing) -> `furps-refinement`.
 5. **Risk domain escalation:** migrations, irreversible operations, auth/privacy, cross-service contracts, public compatibility, or work over 10 files routes to `spec-driven` unless the user explicitly requests a narrower workflow and accepts the containment.
-6. **General fallback:** use `general` only after a one-line General fallback preflight names the specialized workflow considered, rejected reason, and why fallback does not change verification or mutation behavior.
+6. **No match:** proceed without loading a workflow file. The main agent works under the Core Contract above (recall, verify, Evidence Gate) and states in one line which specialized workflow it considered and why none applies.
 
 Mobile is a context modifier, not a workflow. Route by primary intent first.
 Load `references/mobile-context.md` for non-debug mobile work, or
@@ -199,8 +198,8 @@ Read and apply the canonical Plan Challenge Policy from the installed
 `AGENTS.md` bootstrap block (single source: `skills/AGENTS.md`). Prompt-level
 user instructions override that policy for the current turn.
 
-For a low-risk plan that receives the lite gate, attempt a read-only
-`massa-ai-plan-critic` subagent with a bounded checklist packet instead of
+For a low-risk plan that receives the lite gate, attempt a
+`judge` subagent in `plan-critique` mode (it writes nothing in that mode) with a bounded checklist packet instead of
 running the checklist in the main agent. The packet includes the proposed plan, scope,
 constraints, compact recalled facts/evidence, known risks, verification recipe,
 parent identifiers, and this output requirement:
@@ -214,19 +213,19 @@ Lite preserves progressive disclosure: do not load The Fool mode references
 unless the lite critique escalates to full.
 
 Low-risk `feature` and `refactor` plans receive the lite gate first. Full The
-Fool stays for `spec-driven`, `design`, `adr`, `rfc`, `tdd`, explicit challenge
+Fool stays for `spec-driven`, `design`, `create-adr`, `create-rfc`, `create-tdd`, explicit challenge
 requests, high-risk domains, or plans touching more than 5 files/classes/modules.
 When the policy selects the full gate, or lite escalates, load
 `workflows/the-fool.md`, select the mode in the main agent, load only the
-selected The Fool references, and attempt a read-only `massa-ai-plan-critic`
-subagent with selected mode context and a bounded critique packet. Subagents inherit
+selected The Fool references, and attempt a `judge` subagent in `plan-critique` mode with the selected mode passed as `fool_mode`
+and a bounded critique packet. Subagents inherit
 `projectId`, parent `workflowSessionId`, workflow name, entity, and compact
 evidence; they do not receive full conversation context.
 
 If the policy file is unavailable, use the conservative fallback: run the full
 gate for high-risk domains, broad multi-module plans, explicit challenge
 requests, and planning workflows that commit to a feature, refactor, ADR, RFC,
-or TDD. If the `massa-ai-plan-critic` agent is unavailable for any reason —
+or TDD. If the `judge` agent is unavailable for any reason —
 spawning forbidden, plugin not installed, unknown `subagent_type` — run a strict
 standalone fresh-eyes local critique against the same output contract and report
 the skipped delegation reason. Do not retry under a different agent name. Reuse
@@ -282,7 +281,7 @@ Load only when a selected workflow asks for them:
 - `references/agent-orchestration.md`
 - `references/subagent-design.md`
 - `references/code-reuse-scan.md`
-- `references/adr-authoring.md`
+- `references/create-adr.md`
 - `references/audit-scope.md`
 - `references/audit-report-io.md`
 - `references/hook-enforcement.md`
@@ -311,12 +310,10 @@ Load only when a selected workflow asks for them:
 - `references/repo-rules-discovery.md`
 - `references/root-cause-scripts.md`
 - `references/conversation-feedback.md`
-- `references/maestro.md`
-- `references/maestro/`
 - `references/synapse-policy.md`
-- `references/tdd/`
-- `references/rfc/`
-- `references/ticket/`
+- `references/create-tdd/`
+- `references/create-rfc/`
+- `references/create-ticket/`
 - `references/spec-driven/`
 - `references/furps/`