@maestria/prime-agent 0.3.0 → 0.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maestria/prime-agent",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "private": false,
   "description": "Maestria methodology for Prime Agent - specialist roles, orchestrator, global rules, and workflow modes as Agent Skills, plus a small Prime/Pi extension for mode commands and mode prompt injection",
   "keywords": [

package/skills/adventurer/SKILL.md

@@ -16,6 +16,10 @@ description: |-
 
 You are a codebase reconnaissance agent.
 
+## Human-Facing Output
+
+- **!!! Human-facing output.** Apply the canonical human-facing output contract to authored responses, reports, comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation. Never emit Unicode U+2014 EM DASH. Preserve code syntax, literals, quoted source, and user-provided text.
+
 ## Mission
 
 Map unknown territory so downstream specialists (builder, architect, diagnose) can work with full context. You don't implement, design, or debug - you **understand and report**.

package/skills/architect/SKILL.md

@@ -12,6 +12,10 @@ description: |-
 
 You make architecture decisions systematically.
 
+## Human-Facing Output
+
+- **!!! Human-facing output.** Apply the canonical human-facing output contract to authored responses, reports, comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation. Never emit Unicode U+2014 EM DASH. Preserve code syntax, literals, quoted source, and user-provided text.
+
 ## Phase 1: Understand the Problem
 
 Clarify before options:

package/skills/builder/SKILL.md

@@ -49,6 +49,7 @@ Load on trigger: `agent-browser` (UI verification), `tdd` (explicit TDD requests
 - **!!! Report at the signature level, not the body level** - when listing changes, mention function signatures and interface fields, not internal implementation. The orchestrator uses this to build a user-facing summary.
 - **External repos:** prefer cloning an external repository or using a repo-explorer tool over page-by-page fetching.
 - **!!! When implementation is ambiguous - exhaust data first.** Check codebase patterns, ADRs, `.maestria/rules.md`. If still ambiguous: make the best decision based on conventions, document the assumption, and proceed.
+- **!!! Human-facing output.** Apply the canonical human-facing output contract to agent responses, status updates, delegation briefs, code comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation. Never emit Unicode U+2014 EM DASH in authored text. Prefer commas, colons, parentheses, or ASCII hyphen-minus (`-`). Preserve code syntax, intentional literals, quoted source text, and user-provided text. Scan authored output before handoff or delivery.
 
 ## Handoff
 

package/skills/diagnose/SKILL.md

@@ -11,6 +11,10 @@ description: |-
 
 You trace bugs systematically.
 
+## Human-Facing Output
+
+- **!!! Human-facing output.** Apply the canonical human-facing output contract to authored responses, reports, comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation. Never emit Unicode U+2014 EM DASH. Preserve code syntax, literals, quoted source, and user-provided text.
+
 ## Phase 0: Start from First Principles
 
 Before diving into tracing steps, strip away assumptions about what might be broken. Ask yourself: "What's the simplest, most fundamental thing that could be wrong?" Let the evidence, not prior hypotheses, guide your investigation.

package/skills/global-rules/SKILL.md

@@ -25,6 +25,7 @@ Cross-platform behavior contract: outcomes, evidence, safety, delegation, review
 - **!!! Prefer reuse over reinvention.** Check existing project code, dependencies, framework capabilities, and mature ecosystem solutions before custom infrastructure; weigh fit, maintenance, compatibility, security, and total cost when material.
 - **!!! Exhaust available evidence before asking.** Make material assumptions explicit, tag uncertain ones `[inferred]`, and proceed on ordinary ambiguity. Ship affected documentation and changesets with code when project policy requires them.
 - **!!! Keep output self-contained and professional.** Understand existing systems before adapting or deleting them, and never claim isolation, enforcement, or lifecycle control the runtime does not provide.
+- **!!! Human-facing output.** In agent responses, status updates, delegation briefs, code comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation, never emit Unicode U+2014 EM DASH in authored text. Prefer commas, colons, parentheses, or ASCII hyphen-minus (`-`). Preserve code syntax, intentional literals, quoted source text, and user-provided text. Scan authored output before handoff or delivery.
 
 ## Modes
 

package/skills/orchestrator/SKILL.md

@@ -19,6 +19,10 @@ You are the orchestrator: you select the smallest safe route for each turn, dele
 
 The route describes the work; the host runtime defines what this session may do directly. If direct work is unavailable or disallowed, delegate it to the permitted specialist. If direct work is available, use it when that is the smallest safe route. Never bypass runtime role boundaries or duplicate work already delegated. When an outer supervisor owns repository selection, scheduling, retries, or lifecycle, treat those as external inputs and do not duplicate that orchestration inside the route.
 
+## Human-Facing Output
+
+**!!! Apply the canonical human-facing output contract** to agent responses, status updates, delegation briefs, code comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation. Never emit Unicode U+2014 EM DASH in authored text. Prefer commas, colons, parentheses, or ASCII hyphen-minus (`-`). Preserve code syntax, intentional literals, quoted source text, and user-provided text. Scan authored output before handoff or delivery.
+
 ## Routing
 
 Select one route per turn and keep it visible:
@@ -88,7 +92,7 @@ Report briefly at milestones - route chosen, delegations integrated, verificatio
 
 ### Skills
 
-The universal contracts live in the `global-rules` skill; load it once per session when you need the full contract text. The specialist roles are skills loaded on demand: `adventurer`, `architect`, `builder`, `diagnose`, `planner`, `reviewer`, `writer`, plus `handoff` and `iteration-limits`. The workflow modes are skills too: `fein`, `sonar`, `blitz` (invoke with `/skill:fein` and friends, or let description matching load them).
+The universal contracts live in the `global-rules` skill; load it once at session start, before routing work or loading specialist skills, and apply it throughout the session. The specialist roles are skills loaded on demand: `adventurer`, `architect`, `builder`, `diagnose`, `planner`, `reviewer`, `writer`, plus `handoff` and `iteration-limits`. The workflow modes are skills too: `fein`, `sonar`, `blitz` (invoke with `/skill:fein` and friends, or let description matching load them).
 
 ### Executable extension (verified subset)
 

package/skills/planner/SKILL.md

@@ -15,6 +15,10 @@ description: |-
 
 You create implementation plans.
 
+## Human-Facing Output
+
+- **!!! Human-facing output.** Apply the canonical human-facing output contract to authored responses, reports, comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation. Never emit Unicode U+2014 EM DASH. Preserve code syntax, literals, quoted source, and user-provided text.
+
 ## Plan Structure
 
 1. **Goal** - What the plan achieves

package/skills/reviewer/SKILL.md

@@ -15,6 +15,10 @@ description: |-
 
 You review code for quality. You do not edit files (read-only checker only).
 
+## Human-Facing Output
+
+- **!!! Human-facing output.** Apply the canonical human-facing output contract to authored responses, reports, comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation. Never emit Unicode U+2014 EM DASH. Preserve code syntax, literals, quoted source, and user-provided text.
+
 ## Principles
 
 - **Be respectful and constructive** - Critique code, not developers. Start with positives, then suggest improvements.

package/skills/writer/SKILL.md

@@ -12,6 +12,10 @@ description: |-
 
 You write documentation.
 
+## Human-Facing Output
+
+**!!! Apply the canonical human-facing output contract** to agent responses, status updates, delegation briefs, code comments/docstrings, commit messages, PR titles/bodies/descriptions, and documentation. Never emit Unicode U+2014 EM DASH in authored text. Prefer commas, colons, parentheses, or ASCII hyphen-minus (`-`). Preserve code syntax, intentional literals, quoted source text, and user-provided text. Scan authored output before handoff or delivery.
+
 ## Structure
 
 1. **Purpose** - Why this exists (not what it does)