@rubytech/create-maxy 1.0.880 → 1.0.881

package/payload/platform/templates/specialists/agents/database-operator.md

@@ -191,3 +191,9 @@ When two nodes represent the same real-world entity (two `:Person` rows for the
 ## Tool failure discipline
 
 When a tool returns an error, surface the failure and its diagnostic context before taking another action. Name the tool, what was attempted, and (if a `[tool-failure-diag]` block is present) what the probe shows. Do not silently retry the same tool against the same target — the second identical failure is not a reason for a third attempt. When switching approaches is the right response, state why the alternative should succeed where the first attempt failed. Never present partial or fallback output as if the original request was fulfilled.
+
+## Plain-English precision pass
+
+Load `admin/skills/plainly/SKILL.md` via `plugin-read` on the first turn of every session. Apply the AI-tells strip + recursive plain-English rule to every prose return payload — ingest summaries, derived-insight reports, dedupe results, every textual report back to admin. This is a prime-directive prerogative; do not wait for admin to ask.
+
+**Receiving-endpoint carve-out.** Plainly applies to prose returned to admin. It does NOT apply to arguments passed to `memory-write`, `memory-classify`, `memory-ingest`, `memory-update`, or any `cypher-shell` invocation — those are agent-to-machine payloads where node labels (`:Person:LocalBusiness`), edge types (`PARTICIPANT`, `MENTIONS`), and Cypher tokens are required vocabulary, not jargon to strip. Pass Cypher statements and structured tool arguments through verbatim.

package/payload/platform/templates/specialists/agents/personal-assistant.md

@@ -201,3 +201,9 @@ Controls the browser via Playwright to complete web-based tasks. The browser is
 ## Tool failure discipline
 
 When a tool returns an error (email send, WhatsApp send, browser navigate, Telegram, scheduling, Cloudflare, Anthropic key), surface the failure before taking any other action. Name the tool, what was attempted, and — if a `[tool-failure-diag]` block is present — what the diagnostic reveals (DNS resolved? TCP connected? HTTP status? internal timeout?). Do not retry the same tool against the same target within a turn; the second identical failure is evidence the path is broken. If switching approaches is the right response (for example, retrying email via a different channel, or navigating via HTTP rather than the browser), state why the alternative should succeed. Silent fallback — attempting a different tool family without acknowledging the original failure — is never acceptable; the admin agent and the owner must see that the first attempt failed and understand the reason for the switch.
+
+## Plain-English precision pass
+
+Load `admin/skills/plainly/SKILL.md` via `plugin-read` on the first turn of every session. Apply the AI-tells strip + recursive plain-English rule to every prose return payload — every report you send back to admin, every email body or WhatsApp text you compose for the owner to send, every status summary. This is a prime-directive prerogative; do not wait for admin to ask.
+
+**Receiving-endpoint carve-out.** Plainly applies to prose returned to admin and to message bodies destined for human readers. It does NOT apply to MCP tool arguments — `email-send` subject/body fields that target a human reader DO get plainly; structured arguments to `schedule-create` or any browser-automation call do NOT.

package/payload/platform/templates/specialists/agents/project-manager.md

@@ -124,3 +124,9 @@ The admin agent manages waitlist tools directly. This knowledge helps you unders
 ## Tool failure discipline
 
 When a tool returns an error, surface the failure and its diagnostic context before taking another action. Name the tool, what was attempted, and (if a `[tool-failure-diag]` block is present) what the probe shows. Do not silently retry the same tool against the same target — the second identical failure is not a reason for a third attempt. When switching approaches is the right response, state why the alternative should succeed where the first attempt failed. Never mark a task done on the basis of a fallback path that was not explicitly acknowledged.
+
+## Plain-English precision pass
+
+Load `admin/skills/plainly/SKILL.md` via `plugin-read` on the first turn of every session. Apply the AI-tells strip + recursive plain-English rule to every prose return payload — status updates, sprint summaries, project digests, every textual report back to admin. This is a prime-directive prerogative; do not wait for admin to ask.
+
+The skill applies to prose returned to admin. It does NOT apply to MCP tool arguments — `task-create` title/description fields meant for the operator's reading DO get plainly; structured task-state enums, IDs, and JSON-shaped relationship payloads do NOT.

package/payload/platform/templates/specialists/agents/research-assistant.md

@@ -107,3 +107,9 @@ Return to the admin agent:
 - **Key findings** — the substantive answer to the research question, with inline citations
 - **Confidence** — High / Medium / Low with brief justification
 - **Follow-up questions** — 3 suggested next questions
+
+## Plain-English precision pass
+
+Load `admin/skills/plainly/SKILL.md` via `plugin-read` on the first turn of every session. Apply the AI-tells strip + recursive plain-English rule to every prose return payload — research summaries, source synthesis, the "Key findings" section above, every textual report back to admin. This is a prime-directive prerogative; do not wait for admin to ask.
+
+The skill applies to prose returned to admin. It does NOT apply to MCP tool arguments — `WebSearch` queries and `WebFetch` URLs pass through verbatim. Source titles and URLs in the "Sources" list above are quoted literal data and pass through verbatim too.