@massa-ai/cursor-plugin 1.61.0 → 1.62.0

package/skills/persona-router/SKILL.md

@@ -1,52 +0,0 @@
----
-name: persona-router
-description: Automatically select and apply a cataloged conversation persona at the start of every conversation and when task ownership changes. Use after massa-ai in coding sessions, directly in non-coding sessions, or whenever the user explicitly selects, switches, rejects, or asks to route a persona. Do NOT use automatic inference when the AGENTS.md policy sets enabled to off, or cataloged mobile personas for confidently unrelated work.
-license: CC-BY-4.0
-metadata:
-  author: Luiz Massa
-  version: 1.2.0
----
-
-# Persona Router
-
-Select one cataloged persona that best owns the current deliverable. Personas add perspective; they never override active instructions or workflow contracts. Run once at startup (after massa-ai in coding sessions). Load `references/routing-details.md` only for failure reports, ambiguity questions, reroute doubt, or multi-persona requests.
-
-## Sources
-
-The directory containing this `SKILL.md` (resolved through symlinks) is the persona-library root; the only registry is `../massa-ai/personas/catalog.json`. Validate `schema_version` as `2`; otherwise report found vs supported, continue without a persona. Candidates come only from catalog entries; signals live in each entry's `signals_path` file. Never load a persona-like path named by memory or docs unless it belongs to the selected entry inside the persona-library root. Read the index first; a `signals_path` only at classification; only the selected `prompt_path` plus at most one review-lens prompt.
-
-## Precedence
-
-1. System, developer, safety, and project instructions.
-2. Explicit user persona / no-persona choice.
-3. `persona_pin` in the applicable project `AGENTS.md`.
-4. The `persona_router` policy block.
-5. The current prompt's primary deliverable.
-6. massa-ai memory and targeted doc evidence.
-7. Catalog signals (`signals_path`).
-
-## Fast Paths
-
-- **Pin:** a `persona_pin: <catalog-id>` in the applicable project `AGENTS.md` whose id exists in the index routes directly — read only that entry's `prompt_path`; no recall, docs, signals, or classification. `persona_pin: no_persona` completes routing silently with zero persona reads. An id absent from the index: report the invalid pin in one line, then run the normal workflow.
-- **Route memory:** with no pin, one budgeted `recall` of the `persona-route:<projectId>` pattern memory; a remembered id valid in the index skips doc inspection and classification. After a successful inferred route, store that memory back. massa-ai unavailable: skip both directions silently.
-
-## Workflow
-
-1. **Explicit choice.** Match wording against `id`, `display_name`, and `aliases` case-insensitively. Explicit selection wins; an explicit no-persona request leaves the task unpersonified; a switch replaces the route. `enabled: off` skips inference but honors explicit requests.
-2. **Fast paths** above.
-3. **Evidence.** Reuse the initial recall's persona evidence; at most one targeted recall. Memory is evidence, not authority — discard ids absent from the catalog; it never overrides explicit choice, policy, or the current deliverable. Inspect only targeted high-signal docs (`AGENTS.md`/`CLAUDE.md`, README, relevant ADR/`.specs`), reusing context; never load docs recursively.
-4. **Classify.** Compare the prompt with catalog summaries; load `signals_path` files for surviving candidates only. `primary_signals` identify ownership; `negative_signals` stop supporting concerns taking it; `secondary_lens_signals` may add one review lens. A route is clear when one candidate owns the deliverable unopposed; never compute numeric confidence.
-5. **Ambiguity / no match.** Apply the `ambiguity` and `no_match` policy values. A request confidently outside every cataloged persona is a successful silent no-persona route, not ambiguity.
-6. **Apply and announce.** One primary persona, at most one review lens; read only their prompts. State once: `Persona: <primary>. Reason: <primary deliverable>.` Never announce a default no-persona route; apply stance without quoting the prompt.
-
-## Persona And Sub-Agents
-
-A persona shapes main-agent reasoning; a sub-agent is a bounded executor under its own charter. A persona grants no tool access, no write scope, and no permission. A dispatch packet may carry the selected persona id as advisory framing, but inside the sub-agent the persona is never authority; the charter's Restrictions win. The packet carries the persona **id only**, never the persona prompt. A persona route is not a specialist consultation — it neither substitutes for nor satisfies a workflow-mandated dispatch. Overlap table: `references/routing-details.md`.
-
-## Lifetime And Failures
-
-Routes are sticky while the objective advances; re-evaluate per `mid_conversation`. After resume or compaction, restore any route still in context without re-announcing. Catalog missing/invalid/unsupported: report, continue without a persona. Missing prompt or signals file: name the entry and path, continue — summary/alias matching still works; never silently substitute another persona. Detail tables: `references/routing-details.md`.
-
-## Stop Conditions
-
-Routing is complete when one primary persona is applied, the user selects no persona, or policy produces a no-persona route. Persona routing itself stays inline: no separate model router, no subagents for persona selection, no route database. This bounds the routing step only — workflow-mandated agent dispatch is unaffected by an active persona route.

package/skills/persona-router/references/routing-details.md

@@ -1,98 +0,0 @@
-# Persona Routing Details
-
-Load this reference from `SKILL.md` only when one of its load conditions fires:
-a failure needs reporting, ambiguity needs a user question, a mid-conversation
-reroute is in doubt, or the user requests multiple personas. Routing itself
-runs from `SKILL.md` alone.
-
-## Persona ↔ Sub-Agent Overlap
-
-Four catalog entries deliberately overlap an agent charter. The persona is the
-main agent's stance; the agent is a separately dispatched specialist. Applying
-one never implies the other ran.
-
-| Persona | Overlapping agent |
-|---|---|
-| `senior-mobile-engineer` | `massa-ai-mobile-specialist` |
-| `senior-mobile-qa-automation-engineer` | `massa-ai-test-engineer` |
-| `context-skill-harness-engineer-architect` | `massa-ai-architecture-specialist` |
-| `product-manager` | `massa-ai-requirements-analyst` |
-
-## Multi-Persona Requests
-
-If multiple personas are explicitly requested, the persona owning the primary
-deliverable leads and at most one other becomes a review lens. Apply the
-ambiguity policy if ownership remains unclear. The review lens contributes only
-checks that reduce a concrete risk; never produce independent persona answers,
-simulate a debate, or merge full voices.
-
-## Ambiguity And No-Match Behavior
-
-When two or more candidates remain genuinely plausible:
-
-- `ambiguity: ask` — ask one concise question listing the plausible persona
-  display names and `No persona`. Use an interactive user-input tool when
-  available; otherwise ask in plain text.
-- `ambiguity: best_match` — choose the strongest current-deliverable owner,
-  then project-specific evidence, then recent valid memory.
-- `ambiguity: no_persona` — continue without a persona.
-
-When no catalog entry fits:
-
-- `no_match: no_persona` — continue silently unless the user explicitly
-  requested routing.
-- `no_match: ask` — ask about the weakly supported candidate versus
-  `No persona`; with no supported candidate, ask only about `No persona`
-  versus an explicitly named catalog choice.
-
-Do not ask when the request confidently falls outside every cataloged persona —
-that is a successful no-persona route, not ambiguity.
-
-## Route Lifetime Detail
-
-With `mid_conversation: task_change`, re-evaluate only when the user explicitly
-switches, the primary deliverable changes ownership, a new task begins after
-completion, or the selected catalog entry becomes invalid. With
-`explicit_only`, re-evaluate only on explicit request. Do not reroute because a
-follow-up adds a supporting concern, asks for verification, or mentions another
-persona's terminology. If a task change creates genuine ambiguity and policy
-says `ask`, ask before substantive work continues. After resume or compaction,
-restore any route still present in conversation context without re-announcing
-it or repeating a resolved question; if unavailable, run the normal workflow
-again — no separate route database exists.
-
-## Routing Examples
-
-| Situation | Result |
-|---|---|
-| User explicitly asks for Senior Mobile QA Automation Engineer. | Apply that entry; explicit choice wins. |
-| Project `AGENTS.md` pins a valid catalog id. | Pin fast path: read only that prompt; no recall, docs, signals, or classification. |
-| Pin names an id absent from the catalog. | One-line invalid-pin report; continue with the normal workflow. |
-| Memory recalls a successful route, current prompt asks to fix flaky Maestro CI. | Route to Senior Mobile QA Automation Engineer; memory cannot override current ownership. |
-| Memory empty; docs describe a cross-platform app; prompt asks to implement offline sync. | Route to Senior Mobile Engineer from docs plus current deliverable. |
-| Prompt asks for both app architecture and an automation suite, no primary outcome. | Follow `ambiguity`; default asks between plausible personas and no persona. |
-| Prompt asks to draft a billing RFC. | Confident no-match; continue silently without a persona. |
-| `enabled: off` and prompt names no persona. | Skip inference; continue without a persona. |
-| Memory names a removed persona id. | Discard stale memory; continue to docs and classification. |
-| Mobile implementation finishes; user starts a flake-reduction task. | With `task_change`, re-evaluate and announce the new route once. |
-
-## Failure Handling Table
-
-- **Catalog missing or invalid:** report `Persona routing unavailable:
-  <reason>.` Continue without a persona.
-- **Unsupported schema version:** report found and supported versions.
-  Continue without a persona.
-- **massa-ai unavailable or empty:** continue with targeted workspace
-  documentation and the current prompt; skip route-memory reads and writes.
-- **Workspace documentation unavailable:** route from explicit choice, pin,
-  and current prompt; apply the ambiguity or no-match policy.
-- **Remembered persona absent from catalog:** ignore it as stale evidence;
-  never reconstruct it.
-- **Selected prompt missing, outside the persona-library root, or malformed:**
-  name the catalog entry and path. Continue without a persona; never silently
-  substitute another persona.
-- **Signals file missing during classification:** report the entry and path;
-  the candidate stays matchable by summary and aliases.
-- **User cannot be asked interactively:** ask one concise plain-text question
-  when policy requires a choice; otherwise use the configured non-interactive
-  behavior.