@jaggerxtrm/specialists 3.12.0 → 3.14.0

package/config/hooks/specialists-session-start.mjs

@@ -124,7 +124,7 @@ lines.push('');
 lines.push('- `--bead` on edit-capable specialists auto-provisions worktree');
 lines.push('- Reviewer enters with `--job <exec-job>`; `--worktree`/`--job` exclusive');
 lines.push('- `sp epic merge <epic>` for epic chains; `sp merge <chain>` for standalone');
-lines.push('- `sp ps`/`sp feed`/`sp result` (sp poll deprecated)');
+lines.push('- `sp ps`/`sp feed`/`sp result`');
 lines.push('- `--keep-alive` required so reviewer/overthinker can be `sp resume`d');
 lines.push('- `sp merge` fails after `sp stop` cleans status.json — see unitAI-ofjvj');
 

package/config/mandatory-rules/bead-id-verbatim.md

@@ -0,0 +1,14 @@
+# bead-id-verbatim
+
+## Rule
+Source bead-id arguments verbatim from injected context: `bead_id`, branch name, prior turn output, or `bd create` output. Do not retype bead ids from memory or regenerate them.
+
+## Command scope
+Applies only to bd commands that take a bead id, especially `bd close`, `bd update`, `bd dep add`, `bd dep list`, and `bd show`.
+
+## Legit cases
+- New bead creation: id may not exist yet; once `bd create` returns it, copy exact text forward.
+- Narrative prose: may mention bead ids freely. Only command arguments must be verbatim.
+
+## Failure example
+Today logs showed `unitAI-m8744.2` and `unitAI-m8744.3` retyped as `unitAI-m87442` and `unitAI-m87443`; `bd close` then failed with `issue id not found`.

package/config/mandatory-rules/per-turn-handoff-schema.md

@@ -0,0 +1,16 @@
+---
+name: per-turn-handoff-schema
+kind: mandatory-rule
+---
+End every `run_complete` turn, resume turns included, with JSON last. Use `docs/specialists/handoff-schema.md` for required common fields and role-specific fields. Keep block small and valid. Minimal block:
+
+```json
+{
+  "status": "success",
+  "summary": "Done.",
+  "files_changed": [],
+  "follow_ups": [],
+  "risks": [],
+  "verification": []
+}
+```

package/config/skills/specialists-creator/SKILL.md

@@ -13,6 +13,22 @@ synced_at: 236ca5e6
 
 > Source of truth: `src/specialist/schema.ts` | Runtime: `src/specialist/runner.ts`
 
+
+## Canonical References
+
+When a custom specialist needs a standard rule or skill, reference the canonical asset by name instead of copying its file into the repo. Runtime/package fallback resolves canonical mandatory rules and skills when no project-local override exists.
+
+Example:
+
+```json
+{
+  "mandatory_rules": { "template_sets": ["serena-cheatsheet"] },
+  "skills": { "paths": ["releasing"] }
+}
+```
+
+Only create project-local copies when intentionally changing canonical behavior. After setting references, run `sp config show <name> --resolved` to verify the resolved runtime surface.
+
 ---
 
 ## ACTION REQUIRED BEFORE ANYTHING ELSE