@massa-ai/cursor-plugin 1.6.0 → 1.7.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.
Files changed (51) hide show
  1. package/.cursor-plugin/plugin.json +1 -1
  2. package/agents/massa-ai-architecture-specialist.md +2 -1
  3. package/agents/massa-ai-audit-specialist.md +2 -1
  4. package/agents/massa-ai-builder.md +2 -1
  5. package/agents/massa-ai-context-curator.md +2 -1
  6. package/agents/massa-ai-documentation-agent.md +2 -1
  7. package/agents/massa-ai-furps-analyst.md +2 -1
  8. package/agents/massa-ai-investigator.md +2 -1
  9. package/agents/massa-ai-mobile-specialist.md +2 -1
  10. package/agents/massa-ai-navigator.md +2 -1
  11. package/agents/massa-ai-plan-critic.md +2 -1
  12. package/agents/massa-ai-planner.md +2 -1
  13. package/agents/massa-ai-requirements-analyst.md +2 -1
  14. package/agents/massa-ai-reviewer.md +2 -1
  15. package/agents/massa-ai-test-engineer.md +2 -1
  16. package/agents/massa-ai-verification-agent.md +2 -1
  17. package/package.json +1 -1
  18. package/skills/agents/architecture-specialist/SKILL.md +2 -1
  19. package/skills/agents/audit-specialist/SKILL.md +2 -1
  20. package/skills/agents/builder/SKILL.md +2 -1
  21. package/skills/agents/context-curator/SKILL.md +2 -1
  22. package/skills/agents/documentation-agent/SKILL.md +2 -1
  23. package/skills/agents/furps-analyst/SKILL.md +2 -1
  24. package/skills/agents/investigator/SKILL.md +2 -1
  25. package/skills/agents/mobile-specialist/SKILL.md +2 -1
  26. package/skills/agents/navigator/SKILL.md +2 -1
  27. package/skills/agents/plan-critic/SKILL.md +2 -1
  28. package/skills/agents/planner/SKILL.md +2 -1
  29. package/skills/agents/requirements-analyst/SKILL.md +2 -1
  30. package/skills/agents/reviewer/SKILL.md +2 -1
  31. package/skills/agents/test-engineer/SKILL.md +2 -1
  32. package/skills/agents/verification-agent/SKILL.md +2 -1
  33. package/skills/massa-ai/references/agent-orchestration.md +1 -0
  34. package/skills/massa-ai/references/subagent-design.md +1 -0
  35. package/skills/massa-ai/workflows/architecture/architecture-audit.md +2 -0
  36. package/skills/massa-ai/workflows/architecture/architecture-fix.md +2 -0
  37. package/skills/massa-ai/workflows/bugs/bugs-audit.md +1 -0
  38. package/skills/massa-ai/workflows/bugs/bugs-fix.md +2 -0
  39. package/skills/massa-ai/workflows/code-quality/code-quality-audit.md +1 -0
  40. package/skills/massa-ai/workflows/code-quality/code-quality-fix.md +2 -0
  41. package/skills/massa-ai/workflows/exploration.md +1 -0
  42. package/skills/massa-ai/workflows/implementation/implementation-audit.md +1 -0
  43. package/skills/massa-ai/workflows/implementation/implementation-fix.md +2 -0
  44. package/skills/massa-ai/workflows/requirements/requirements-audit.md +1 -0
  45. package/skills/massa-ai/workflows/requirements/requirements-fix.md +2 -0
  46. package/skills/massa-ai/workflows/security/security-audit.md +1 -0
  47. package/skills/massa-ai/workflows/security/security-fix.md +2 -0
  48. package/skills/massa-ai/workflows/spec-driven.md +1 -0
  49. package/skills/massa-ai/workflows/tests/tests-audit.md +1 -0
  50. package/skills/massa-ai/workflows/tests/tests-fix.md +2 -0
  51. package/skills/persona-router/SKILL.md +19 -1
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "name": "massa-ai",
3
- "version": "1.6.0",
3
+ "version": "1.7.1",
4
4
  "description": "massa-ai — semantic code search, memory, and context compression for Cursor"
5
5
  }
@@ -20,7 +20,8 @@ Provide architectural guidance by evaluating structure, suggesting boundaries, a
20
20
  ## Restrictions
21
21
  - Never implement.
22
22
  - Never rewrite code.
23
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
23
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
24
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
24
25
 
25
26
  ## Inputs
26
27
  - `scope`: the module, service, or area under evaluation.
@@ -19,7 +19,8 @@ Execute a specialized audit through one configurable lens and return findings-on
19
19
  ## Restrictions
20
20
  - Never modify implementation.
21
21
  - One lens per dispatch; do not mix lenses in one run.
22
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
22
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
23
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
23
24
 
24
25
  ## Lenses
25
26
 
@@ -21,7 +21,8 @@ Implement an approved plan or task by modifying source code with a disjoint writ
21
21
  - Never perform reviews.
22
22
  - Never generate implementation plans.
23
23
  - Never write outside the assigned disjoint write set.
24
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
24
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
25
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
25
26
 
26
27
  ## Inputs
27
28
  - `scope`: exact files and modules to modify (disjoint write set).
@@ -22,7 +22,8 @@ Prepare the minimum high-quality Context Packet required for another agent to do
22
22
  - Never implement.
23
23
  - Never review.
24
24
  - Never plan.
25
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
25
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
26
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
26
27
 
27
28
  ## Inputs
28
29
  - `scope`: the next agent's task and target area.
@@ -20,7 +20,8 @@ Generate engineering documentation artifacts (README, ADR, RFC, changelog, KDoc,
20
20
  ## Restrictions
21
21
  - Never modify implementation.
22
22
  - Write only when scoped with a disjoint write set (same constraint as builder).
23
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
23
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
24
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
24
25
 
25
26
  ## Inputs
26
27
  - `scope`: the doc artifact type and target area.
@@ -21,7 +21,8 @@ Analyze exactly one FURPS+ dimension of a PRD or ADR against its checklist secti
21
21
  - Never analyze a dimension other than the assigned one; flag cross-dimension gaps instead of expanding into them.
22
22
  - Never write files, never mutate Atlassian issues, never write memory.
23
23
  - Never return raw document dumps.
24
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
24
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
25
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
25
26
  - Do not use this role for The Fool critique (use `plan-critic`) or for code claims (use `investigator` / `verification-agent`).
26
27
 
27
28
  ## Inputs
@@ -21,7 +21,8 @@ Read and understand the codebase to answer engineering questions without modifyi
21
21
  - Never modify code.
22
22
  - Never generate implementation.
23
23
  - Never perform reviews.
24
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
24
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
25
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
25
26
 
26
27
  ## Inputs
27
28
  - `scope`: files, modules, symbols, or questions to investigate.
@@ -20,7 +20,8 @@ Provide mobile-specific expertise (Android, iOS, KMP) when the workflow detects
20
20
  ## Restrictions
21
21
  - Refuse non-mobile targets (no `build.gradle`, `Podfile`, `*.kt`, `*.swift`, `ios/`, `android/`).
22
22
  - Never implement (read-only guidance only).
23
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
23
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
24
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
24
25
 
25
26
  ## Topics
26
27
 
@@ -28,7 +28,8 @@ The user's codebase is **already indexed** by massa-ai. The first move on any qu
28
28
  - Never scan directories exhaustively or read whole trees to answer a narrow question.
29
29
  - Never paste long code; summarize and cite.
30
30
  - Never call `reset_project`, `index`, or `reindex`; report the needed reindex to the parent agent instead.
31
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
31
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
32
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
32
33
 
33
34
  ## Inputs
34
35
  - `question`: the exploration question to answer.
@@ -22,7 +22,8 @@ Challenge a plan that already exists so its weakest assumption is exposed before
22
22
  - Never implement, refactor, or run mutating commands.
23
23
  - Never expand scope beyond the plan packet received.
24
24
  - Never request or reconstruct full conversation history.
25
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
25
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
26
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
26
27
 
27
28
  ## Inputs
28
29
  - `plan`: the concrete proposed plan text.
@@ -20,7 +20,8 @@ Transform an engineering request into a structured implementation plan.
20
20
  ## Restrictions
21
21
  - Never implement.
22
22
  - Never review code.
23
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
23
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
24
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
24
25
 
25
26
  ## Inputs
26
27
  - `scope`: the request, target area, and known constraints.
@@ -20,7 +20,8 @@ Analyze requirements before implementation to surface ambiguity, gaps, contradic
20
20
  ## Restrictions
21
21
  - Never implement.
22
22
  - Never silently drop a requirement; flag every gap for user acceptance or record as an assumption.
23
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
23
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
24
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
24
25
 
25
26
  ## Inputs
26
27
  - `scope`: the requirement set, PRD, or spec under analysis.
@@ -21,7 +21,8 @@ Review implementation quality by analyzing the diff and flagging bugs, regressio
21
21
  - Never implement.
22
22
  - Never rewrite files.
23
23
  - Never plan features.
24
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
24
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
25
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
25
26
 
26
27
  ## Inputs
27
28
  - `scope`: the diff, changed files, or PR to review.
@@ -21,7 +21,8 @@ Generate a testing strategy that covers unit, integration, edge cases, negative
21
21
  - Focus only on testing.
22
22
  - No production code changes outside test files.
23
23
  - Write only when scoped with a disjoint write set (same constraint as builder).
24
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
24
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
25
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
25
26
 
26
27
  ## Inputs
27
28
  - `scope`: the feature, module, or spec to test.
@@ -20,7 +20,8 @@ Centralize Verification Ladder logic and validate that a task's output meets its
20
20
  ## Restrictions
21
21
  - Never modify implementation.
22
22
  - Never skip a verification level without recording a concrete reason.
23
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
23
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
24
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
24
25
 
25
26
  ## Inputs
26
27
  - `scope`: the task, its acceptance criteria, and the files changed.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@massa-ai/cursor-plugin",
3
- "version": "1.6.0",
3
+ "version": "1.7.1",
4
4
  "description": "massa-ai plugin for Cursor — semantic code search, memory, and context compression",
5
5
  "files": [
6
6
  "agents",
@@ -24,7 +24,8 @@ Provide architectural guidance by evaluating structure, suggesting boundaries, a
24
24
  ## Restrictions
25
25
  - Never implement.
26
26
  - Never rewrite code.
27
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
27
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
28
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
28
29
 
29
30
  ## Inputs
30
31
  - `scope`: the module, service, or area under evaluation.
@@ -23,7 +23,8 @@ Execute a specialized audit through one configurable lens and return findings-on
23
23
  ## Restrictions
24
24
  - Never modify implementation.
25
25
  - One lens per dispatch; do not mix lenses in one run.
26
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
26
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
27
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
27
28
 
28
29
  ## Lenses
29
30
 
@@ -25,7 +25,8 @@ Implement an approved plan or task by modifying source code with a disjoint writ
25
25
  - Never perform reviews.
26
26
  - Never generate implementation plans.
27
27
  - Never write outside the assigned disjoint write set.
28
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
28
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
29
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
29
30
 
30
31
  ## Inputs
31
32
  - `scope`: exact files and modules to modify (disjoint write set).
@@ -26,7 +26,8 @@ Prepare the minimum high-quality Context Packet required for another agent to do
26
26
  - Never implement.
27
27
  - Never review.
28
28
  - Never plan.
29
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
29
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
30
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
30
31
 
31
32
  ## Inputs
32
33
  - `scope`: the next agent's task and target area.
@@ -24,7 +24,8 @@ Generate engineering documentation artifacts (README, ADR, RFC, changelog, KDoc,
24
24
  ## Restrictions
25
25
  - Never modify implementation.
26
26
  - Write only when scoped with a disjoint write set (same constraint as builder).
27
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
27
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
28
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
28
29
 
29
30
  ## Inputs
30
31
  - `scope`: the doc artifact type and target area.
@@ -25,7 +25,8 @@ Analyze exactly one FURPS+ dimension of a PRD or ADR against its checklist secti
25
25
  - Never analyze a dimension other than the assigned one; flag cross-dimension gaps instead of expanding into them.
26
26
  - Never write files, never mutate Atlassian issues, never write memory.
27
27
  - Never return raw document dumps.
28
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
28
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
29
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
29
30
  - Do not use this role for The Fool critique (use `plan-critic`) or for code claims (use `investigator` / `verification-agent`).
30
31
 
31
32
  ## Inputs
@@ -25,7 +25,8 @@ Read and understand the codebase to answer engineering questions without modifyi
25
25
  - Never modify code.
26
26
  - Never generate implementation.
27
27
  - Never perform reviews.
28
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
28
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
29
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
29
30
 
30
31
  ## Inputs
31
32
  - `scope`: files, modules, symbols, or questions to investigate.
@@ -24,7 +24,8 @@ Provide mobile-specific expertise (Android, iOS, KMP) when the workflow detects
24
24
  ## Restrictions
25
25
  - Refuse non-mobile targets (no `build.gradle`, `Podfile`, `*.kt`, `*.swift`, `ios/`, `android/`).
26
26
  - Never implement (read-only guidance only).
27
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
27
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
28
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
28
29
 
29
30
  ## Topics
30
31
 
@@ -33,7 +33,8 @@ The user's codebase is **already indexed** by massa-ai. The first move on any qu
33
33
  - Never scan directories exhaustively or read whole trees to answer a narrow question.
34
34
  - Never paste long code; summarize and cite.
35
35
  - Never call `reset_project`, `index`, or `reindex`; report the needed reindex to the parent agent instead.
36
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
36
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
37
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
37
38
 
38
39
  ## Inputs
39
40
  - `question`: the exploration question to answer.
@@ -26,7 +26,8 @@ Challenge a plan that already exists so its weakest assumption is exposed before
26
26
  - Never implement, refactor, or run mutating commands.
27
27
  - Never expand scope beyond the plan packet received.
28
28
  - Never request or reconstruct full conversation history.
29
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
29
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
30
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
30
31
 
31
32
  ## Inputs
32
33
  - `plan`: the concrete proposed plan text.
@@ -24,7 +24,8 @@ Transform an engineering request into a structured implementation plan.
24
24
  ## Restrictions
25
25
  - Never implement.
26
26
  - Never review code.
27
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
27
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
28
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
28
29
 
29
30
  ## Inputs
30
31
  - `scope`: the request, target area, and known constraints.
@@ -24,7 +24,8 @@ Analyze requirements before implementation to surface ambiguity, gaps, contradic
24
24
  ## Restrictions
25
25
  - Never implement.
26
26
  - Never silently drop a requirement; flag every gap for user acceptance or record as an assumption.
27
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
27
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
28
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
28
29
 
29
30
  ## Inputs
30
31
  - `scope`: the requirement set, PRD, or spec under analysis.
@@ -25,7 +25,8 @@ Review implementation quality by analyzing the diff and flagging bugs, regressio
25
25
  - Never implement.
26
26
  - Never rewrite files.
27
27
  - Never plan features.
28
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
28
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
29
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
29
30
 
30
31
  ## Inputs
31
32
  - `scope`: the diff, changed files, or PR to review.
@@ -25,7 +25,8 @@ Generate a testing strategy that covers unit, integration, edge cases, negative
25
25
  - Focus only on testing.
26
26
  - No production code changes outside test files.
27
27
  - Write only when scoped with a disjoint write set (same constraint as builder).
28
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
28
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
29
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
29
30
 
30
31
  ## Inputs
31
32
  - `scope`: the feature, module, or spec to test.
@@ -24,7 +24,8 @@ Centralize Verification Ladder logic and validate that a task's output meets its
24
24
  ## Restrictions
25
25
  - Never modify implementation.
26
26
  - Never skip a verification level without recording a concrete reason.
27
- - Never spawn subagents and never load the `massa-ai` router; the dispatching workflow owns routing.
27
+ - Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
28
+ - A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
28
29
 
29
30
  ## Inputs
30
31
  - `scope`: the task, its acceptance criteria, and the files changed.
@@ -112,6 +112,7 @@ When dispatching a subagent, send a compact capability packet rather than a loos
112
112
  - output: the exact output contract
113
113
  - firewall: raw logs, diffs, snapshots, reports, or research that must be summarized
114
114
  - memory boundary: whether the subagent may suggest memories and who persists them
115
+ - `persona`: optional. The cataloged persona id in effect for the parent conversation, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions. Pass the id alone, never the persona prompt.
115
116
  - exact next step: what the main agent should do with the result
116
117
 
117
118
  ## Prompt Contract
@@ -103,6 +103,7 @@ When a workflow dispatches a reusable role, send a capability packet rather than
103
103
  - `output`: the exact output contract
104
104
  - `firewall`: raw logs, diffs, snapshots, or research that must be summarized
105
105
  - `memory`: whether the subagent may suggest memory and who persists it
106
+ - `persona`: optional. The cataloged persona id in effect for the parent conversation, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions. Pass the id alone, never the persona prompt.
106
107
 
107
108
  ## Quality Checklist
108
109
 
@@ -90,6 +90,7 @@ This workflow is findings-only. Do not edit code unless the user separately asks
90
90
  > - output: findings with lens-specific evidence, provisional severity, tradeoff, and what would disprove it
91
91
  > - firewall: raw dependency graphs, generated reports, and broad search output summarized, not returned raw
92
92
  > - memory: suggest-only; main agent persists accepted constraints/rejected refactors
93
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
93
94
 
94
95
  > **Dispatch: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
95
96
  > - trigger: independent verification of a high-impact architecture finding
@@ -100,6 +101,7 @@ This workflow is findings-only. Do not edit code unless the user separately asks
100
101
  > - output: confirmed/disproven verdict with evidence; skipped-check reason if the sensor cannot run
101
102
  > - firewall: raw logs/snapshots summarized
102
103
  > - memory: suggest-only; main agent persists reusable verification recipes
104
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
103
105
  13. Severity rules (apply the countable threshold first, then the qualitative clause):
104
106
  - `critical`: architecture issue likely causes data loss, auth/privacy break, production outage, irreversible corruption, OR affects >10 files; otherwise use the qualitative clause below.
105
107
  - `high`: strong coupling with high volatility, boundary violation, dependency inversion break, or shallow module design likely to cause major change friction or regression.
@@ -66,6 +66,7 @@ Do not use this workflow for findings-only architecture review; route that to `w
66
66
  > - output: implementation summary, commands run, test counts, deviations
67
67
  > - firewall: raw diffs/logs summarized
68
68
  > - memory: suggest-only; main agent persists reusable architecture patterns
69
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
69
70
 
70
71
  > **Dispatch: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
71
72
  > - trigger: independent verification of a high-risk or multi-file architecture fix
@@ -76,6 +77,7 @@ Do not use this workflow for findings-only architecture review; route that to `w
76
77
  > - output: confirmed/disproven closure verdict with evidence
77
78
  > - firewall: raw test output/logs summarized
78
79
  > - memory: suggest-only; main agent persists reusable verification recipes
80
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
79
81
  11. Verify each completed finding:
80
82
  - If verification found a reusable signal (`ac_gap`, `surviving_mutant`, `spec_precision_gap`, `spec_deviation`, `gate_fail`), record it via `references/lessons.md`:
81
83
  `python3 skills/massa-ai/scripts/lessons.py --root . add --feature "<slug>" --signal "<signal>" --source "<ref>" --text "<one terse lesson>"`
@@ -66,6 +66,7 @@ This workflow is findings-only. Do not edit code unless the user separately asks
66
66
  > - output: findings with bug category, location, evidence, trigger, severity, confidence, simplest fix direction, verification suggestion
67
67
  > - firewall: raw diffs/logs/search output summarized, not returned raw
68
68
  > - memory: suggest-only; main agent persists reusable bug patterns
69
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
69
70
 
70
71
  - Trace input -> transformation -> output for each suspicious path.
71
72
  - Check diffs, surrounding code, callers and callees, tests, config, migrations, schemas, and recalled project patterns.
@@ -55,6 +55,7 @@ Do not use this workflow for findings-only bug discovery; route that to `workflo
55
55
  > - output: implementation summary, commands run, test counts, deviations
56
56
  > - firewall: raw diffs/logs summarized
57
57
  > - memory: suggest-only; main agent persists reusable bug patterns
58
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
58
59
 
59
60
  > **Dispatch: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
60
61
  > - trigger: independent verification of a high-risk bug fix
@@ -65,6 +66,7 @@ Do not use this workflow for findings-only bug discovery; route that to `workflo
65
66
  > - output: confirmed/disproven closure verdict with evidence
66
67
  > - firewall: raw test output/logs summarized
67
68
  > - memory: suggest-only; main agent persists reusable verification recipes
69
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
68
70
  - Main agent owns report parsing, prioritization, memory writes, final synthesis, and Evidence Gate.
69
71
  10. Verify each completed finding:
70
72
  - If verification found a reusable signal (`ac_gap`, `surviving_mutant`, `spec_precision_gap`, `spec_deviation`, `gate_fail`), record it via `references/lessons.md`:
@@ -80,6 +80,7 @@ This workflow is findings-only. Do not edit code unless the user separately asks
80
80
  > - output: findings with smell category, location, evidence, severity, confidence, and simplest fix direction
81
81
  > - firewall: raw diffs/logs/search output summarized, not returned raw
82
82
  > - memory: suggest-only; main agent persists reusable code-quality patterns
83
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
83
84
 
84
85
  - Do not delegate every check by default; avoid duplicate source reading when one main-agent pass is cheaper.
85
86
  - Subagents may suggest memory content, but the main agent decides what durable knowledge to persist.
@@ -62,6 +62,7 @@ Do not use this workflow for findings-only SOLID, Clean Code, KISS, YAGNI, DRY,
62
62
  > - output: implementation summary, commands run, test counts, deviations
63
63
  > - firewall: raw diffs/logs summarized
64
64
  > - memory: suggest-only; main agent persists reusable code-quality patterns
65
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
65
66
 
66
67
  > **Dispatch: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
67
68
  > - trigger: independent verification of a high-risk code-quality fix
@@ -72,6 +73,7 @@ Do not use this workflow for findings-only SOLID, Clean Code, KISS, YAGNI, DRY,
72
73
  > - output: confirmed/disproven closure verdict with evidence
73
74
  > - firewall: raw test output/logs summarized
74
75
  > - memory: suggest-only; main agent persists reusable verification recipes
76
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
75
77
  - Main agent owns report parsing, prioritization, memory writes, final synthesis, and Evidence Gate.
76
78
  11. Verify each completed finding:
77
79
  - If verification found a reusable signal (`ac_gap`, `surviving_mutant`, `spec_precision_gap`, `spec_deviation`, `gate_fail`), record it via `references/lessons.md`:
@@ -69,6 +69,7 @@ Step 5: Flag as uncertain → "I'm not certain about X — here's my reasoning,
69
69
  > - output: entry points, core flow, dependencies, data ownership, relevant contracts, exact evidence pointers (path, symbol, line), confirmed facts vs inferences
70
70
  > - firewall: raw logs, snapshots, generated reports, and broad search output summarized, not returned raw
71
71
  > - memory: suggest-only; main agent persists durable discoveries
72
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
72
73
 
73
74
  - Follow the shared retrieval order: project map, summary search, targeted
74
75
  enriched search, symbol/file tools, optimized context, then focused shell
@@ -41,6 +41,7 @@ Do not use this parent workflow when the user wants only one audit lens; route d
41
41
  > - output: `Status`, `Scope checked`, `Evidence`, `Findings`, `Verification/Test Fidelity Checklist`, `Risks and skipped checks`, and `Exact next step`
42
42
  > - firewall: raw diffs/logs/search output summarized, not returned raw
43
43
  > - memory: suggest-only; children must not persist broad project memory unless assigned
44
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
44
45
 
45
46
  - Repeated-search children receive isolated Synapse sessions. Durable child tags retain the parent session and workflow-specific session.
46
47
  8. Use deterministic sensors when target-relevant commands are expected to finish in <=5 minutes and need no network, destructive action, production credential, or unapproved external service: tests, builds, lint, type checks, static checks, import checks, or focused runtime commands. Record skipped commands with one reason enum: `too-expensive`, `needs-network`, `needs-credentials`, `destructive-risk`, `outside-scope`, `tool-missing`, or `not-applicable`. Model judgment alone is not completion evidence.
@@ -56,6 +56,7 @@ Do not execute from chat summaries, inline review comments, remembered findings,
56
56
  > - output: implementation summary, commands run, test counts, deviations
57
57
  > - firewall: raw diffs/logs summarized
58
58
  > - memory: suggest-only; main agent persists reusable patterns
59
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
59
60
 
60
61
  > **Dispatch: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
61
62
  > - trigger: high-risk, security, public-contract, or multi-file fix
@@ -66,6 +67,7 @@ Do not execute from chat summaries, inline review comments, remembered findings,
66
67
  > - output: confirmed/disproven closure verdict with evidence
67
68
  > - firewall: raw test output/logs summarized
68
69
  > - memory: suggest-only; main agent persists reusable verification recipes
70
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
69
71
 
70
72
  Never run parallel writers against shared files or contracts.
71
73
  11. Verify each completed finding with the Mandatory Verification Fix Gate from `references/verification-ladder.md`: run the report's Verification Suggestion or an equivalent deterministic command/artifact check, then run focused tests, build, lint, type, static, or runtime checks relevant to the source lens. Reinspect tests, fixtures, snapshots, types, specs, public contracts, and touched identifiers so validation assets were not weakened and names follow `references/naming-standards.md`. A finding cannot be marked `fixed` when a target-relevant command or artifact check exists but was not attempted; if verification cannot run, mark it `blocked`, `deferred`, or `skipped` with an allowed skipped-check reason.
@@ -69,6 +69,7 @@ This workflow is findings-only. Do not edit code unless the user separately asks
69
69
  > - output: findings with requirement gap, location, evidence, severity, confidence, simplest fix direction, verification suggestion
70
70
  > - firewall: raw diffs/logs/search output summarized, not returned raw
71
71
  > - memory: suggest-only; main agent persists reusable requirements patterns
72
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
72
73
 
73
74
  - Build a requirement checklist from the source: must-have behavior, non-goals, acceptance criteria, compatibility constraints, inputs, outputs, and user-visible promises.
74
75
  - Compare implementation and tests against each checklist item.
@@ -57,6 +57,7 @@ Do not use this workflow for findings-only requirements review; route that to `w
57
57
  > - output: implementation summary, commands run, test counts, deviations
58
58
  > - firewall: raw diffs/logs summarized
59
59
  > - memory: suggest-only; main agent persists reusable requirements patterns
60
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
60
61
 
61
62
  > **Dispatch: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
62
63
  > - trigger: independent verification of a high-risk requirements fix
@@ -67,6 +68,7 @@ Do not use this workflow for findings-only requirements review; route that to `w
67
68
  > - output: confirmed/disproven closure verdict with evidence
68
69
  > - firewall: raw test output/logs summarized
69
70
  > - memory: suggest-only; main agent persists reusable verification recipes
71
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
70
72
  - Main agent owns report parsing, traceability matrix, memory writes, final synthesis, and Evidence Gate.
71
73
  11. Verify each completed finding:
72
74
  - If verification found a reusable signal (`ac_gap`, `surviving_mutant`, `spec_precision_gap`, `spec_deviation`, `gate_fail`), record it via `references/lessons.md`:
@@ -67,6 +67,7 @@ This workflow is findings-only. Do not edit code unless the user separately asks
67
67
  > - output: findings with security boundary, asset, trigger/exploit path, severity, confidence, evidence, simplest fix direction, verification suggestion
68
68
  > - firewall: raw diffs/logs/search output summarized, not returned raw
69
69
  > - memory: suggest-only; main agent persists reusable security patterns
70
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
70
71
 
71
72
  - Trace untrusted input -> validation -> authorization -> transformation -> persistence or side effect.
72
73
  - Check authn/authz, object ownership, tenant isolation, input validation, output encoding, secret handling, cryptography use, SSRF/path traversal/injection risks, logging privacy, dependency/config exposure, and security-sensitive tests.
@@ -61,6 +61,7 @@ Do not use this workflow for findings-only security review; route that to `workf
61
61
  > - output: implementation summary, commands run, test counts, deviations
62
62
  > - firewall: raw diffs/logs summarized
63
63
  > - memory: suggest-only; main agent persists reusable security patterns
64
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
64
65
 
65
66
  > **Dispatch: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
66
67
  > - trigger: independent verification of a high-risk security fix
@@ -71,6 +72,7 @@ Do not use this workflow for findings-only security review; route that to `workf
71
72
  > - output: confirmed/disproven closure verdict with evidence
72
73
  > - firewall: raw test output/logs summarized
73
74
  > - memory: suggest-only; main agent persists reusable verification recipes
75
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
74
76
  - Main agent owns report parsing, prioritization, memory writes, final synthesis, and Evidence Gate.
75
77
  11. Verify each completed finding:
76
78
  - If verification found a reusable signal (`ac_gap`, `surviving_mutant`, `spec_precision_gap`, `spec_deviation`, `gate_fail`), record it via `references/lessons.md`:
@@ -110,6 +110,7 @@ Quick artifacts live under `.specs/quick/NNN-slug/` with a `TASK.md` (one-line i
110
110
  > - output: `.specs/features/<slug>/validation.md` (PASS/FAIL, per-AC evidence, sensor result, diff range); compact verdict + ranked gap list; gaps become fix tasks
111
111
  > - firewall: raw diffs/logs/test output summarized; mutations run in scratch state only
112
112
  > - memory: suggest-only; main agent persists validation outcomes
113
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
113
114
 
114
115
  - The verification-agent re-derives coverage independently using evidence-or-zero and does not inherit the author's mental model.
115
116
  - The fix → re-verify loop is capped at 3 iterations before escalating to `Blocked`.
@@ -67,6 +67,7 @@ This workflow is findings-only. Do not edit code unless the user separately asks
67
67
  > - output: findings with missing/weak coverage type, location, evidence, regression risk, severity, simplest test direction, deterministic sensor, verification suggestion
68
68
  > - firewall: raw diffs/logs/search output summarized, not returned raw
69
69
  > - memory: suggest-only; main agent persists reusable testing patterns
70
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
70
71
 
71
72
  - Map changed or targeted behavior to existing tests, fixtures, mocks, and deterministic harnesses.
72
73
  - Check missing tests for new branches, error paths, auth/validation/persistence changes, async or race-prone logic, migrations, public contracts, and recalled bug patterns.
@@ -69,6 +69,7 @@ Do not use this workflow for findings-only test coverage, assertion quality, fix
69
69
  > - output: implementation summary, test counts, commands run, deviations
70
70
  > - firewall: raw test output/logs summarized
71
71
  > - memory: suggest-only; main agent persists reusable testing patterns
72
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
72
73
 
73
74
  > **Dispatch: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
74
75
  > - trigger: independent verification of a high-risk test fix
@@ -79,6 +80,7 @@ Do not use this workflow for findings-only test coverage, assertion quality, fix
79
80
  > - output: confirmed/disproven closure verdict with evidence
80
81
  > - firewall: raw test output/logs summarized
81
82
  > - memory: suggest-only; main agent persists reusable verification recipes
83
+ > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
82
84
  - Main agent owns report parsing, prioritization, memory writes, final synthesis, and Evidence Gate.
83
85
  12. At completion, persist only durable knowledge after scoring with the Importance Calibration System:
84
86
  - Testing conventions, deterministic harness recipes, flaky-test root causes, accepted exceptions, or reusable edge-case coverage patterns.
@@ -42,6 +42,24 @@ Apply precedence in this order:
42
42
 
43
43
  Persona text is additive. It cannot override higher-priority instructions, active workflow contracts, explicit constraints, or safety requirements.
44
44
 
45
+ ## Persona And Sub-Agents
46
+
47
+ Personas and sub-agents are different layers. A persona shapes how the main agent reasons and synthesizes. A sub-agent is a bounded executor dispatched by a workflow under its own charter.
48
+
49
+ - A persona grants no tool access, no write scope, and no permission. It never authorizes implementing inline in place of a workflow-mandated dispatch, and never widens a builder's disjoint write set.
50
+ - A workflow may pass the selected persona id into a dispatch capability packet as advisory framing. Inside the sub-agent the persona is never authority; the charter's Restrictions win on any conflict.
51
+ - The packet carries the persona **id only**, never the persona prompt. A sub-agent works from the id and its own charter, and never opens a `personas/` file to expand it.
52
+ - A persona route is not a specialist consultation. Applying a persona neither substitutes for nor satisfies an agent dispatch that the workflow requires.
53
+
54
+ 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.
55
+
56
+ | Persona | Overlapping agent |
57
+ |---|---|
58
+ | `senior-mobile-engineer` | `massa-ai-mobile-specialist` |
59
+ | `senior-mobile-qa-automation-engineer` | `massa-ai-test-engineer` |
60
+ | `context-skill-harness-engineer-architect` | `massa-ai-architecture-specialist` |
61
+ | `product-manager` | `massa-ai-requirements-analyst` |
62
+
45
63
  ## Automatic Routing Workflow
46
64
 
47
65
  ### 1. Resolve Explicit Choice And Policy
@@ -155,4 +173,4 @@ After resume or compaction, restore any route still present in conversation cont
155
173
 
156
174
  ## Stop Conditions
157
175
 
158
- Routing is complete when one primary persona is applied, the user selects no persona, or policy intentionally produces a no-persona route. Do not invoke a separate model router, launch subagents, create subprocess orchestration, or persist a route database.
176
+ Routing is complete when one primary persona is applied, the user selects no persona, or policy intentionally produces a no-persona route. Persona routing itself stays inline: do not invoke a separate model router, launch subagents for persona selection, create subprocess orchestration, or persist a route database. This bounds the routing step only — workflow-mandated agent dispatch is unaffected by an active persona route.