From 1126a0a345c982bb27b9e6e1d3a3b4f3acc11047 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A5rten=20Angner?= Date: Fri, 20 Mar 2026 11:51:44 +0100 Subject: [PATCH] fix: update all manifests to v0.4.1 + agent onboarding guide MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - All bmad-manifest.json files bumped to 0.4.1 - Design Space manifest: work-orders replaced with update-status - Added "For Agents Without Specific Instructions" section to Design Space SKILL.md — any agent entering the system gets a clear guide on how messaging works Co-Authored-By: Claude Opus 4.6 (1M context) --- src/skills/design-space/SKILL.md | 36 ++++++++++++++++++---- src/skills/design-space/bmad-manifest.json | 14 ++++----- src/skills/freya/bmad-manifest.json | 2 +- src/skills/saga/bmad-manifest.json | 2 +- 4 files changed, 39 insertions(+), 15 deletions(-) diff --git a/src/skills/design-space/SKILL.md b/src/skills/design-space/SKILL.md index 36779f32e..1008848ef 100644 --- a/src/skills/design-space/SKILL.md +++ b/src/skills/design-space/SKILL.md @@ -277,20 +277,44 @@ When invoked with no arguments (`/u` or `/design-space`): ## Quick Reference -| I want to... | Command | +| I want to... | How | |---|---| | Find what we know about X | `search ` | | Save a design decision | `capture ` | -| Check if agents left messages | `check` or just `/u` | +| Check messages | `check` or just `/u` | | Tell another agent something | `send ` | +| Give someone a task | `send ` with `message_type: "work-order"` | +| Claim or update a task | `update-status` on the message | | See who's online | `who` | -| Log an experiment result | `capture` with `failed_experiment` or `successful_pattern` | -| Post a task for another agent | `work post ` | -| See available tasks | `work list` | + +## For Agents Without Specific Instructions + +If you are an agent entering Design Space without persona-specific instructions (no Saga, Freya, Codex, or Ivonne activation), here is how to use the system: + +**Everything is a message.** There are no separate "tasks" or "work orders" — just messages with different types. When you check for messages, you see ALL unread messages from all agents. Signal strength tells you what's most relevant to you, but nothing is hidden. + +**Message types:** +- `notification` — FYI, no action needed +- `question` — someone is asking something, consider responding +- `work-order` — a task with status (ready → in-progress → done). Claim it by updating status. +- `handoff` — an agent is passing work to you or another agent +- `answer` — a response to a previous message +- `broadcast` — general announcement to everyone + +**Your identity:** Use your agent name (or "claude-code" as fallback) when sending and checking. Register on session start to get a session ID and see who else is online. + +**Core workflow:** +1. Register: `{"action": "register", "agent_id": "your-name"}` +2. Check messages: `{"action": "check", "agent_id": "your-name"}` +3. Read messages sorted by signal strength (strong = for you, available = ambient) +4. Respond, capture insights, or send new messages as needed +5. Mark messages read when done: `{"action": "mark-read", "message_ids": [...], "agent_id": "your-name"}` + +**Principle:** You can see everything. Signal strength helps you prioritize. Work orders are just messages you can claim. Capture your learnings so the next agent benefits. ## End-of-Turn Convention -When any WDS agent finishes a task, it should: +When any agent finishes a task, it should: 1. Check Design Space for unread messages 2. Capture any meaningful decisions or insights from the work just completed diff --git a/src/skills/design-space/bmad-manifest.json b/src/skills/design-space/bmad-manifest.json index 5019c1dea..de96c094f 100644 --- a/src/skills/design-space/bmad-manifest.json +++ b/src/skills/design-space/bmad-manifest.json @@ -1,7 +1,7 @@ { "name": "wds-design-space", - "version": "0.4.0", - "description": "Shared knowledge base and agent messaging system", + "version": "0.4.1", + "description": "Shared knowledge base and unified agent messaging", "capabilities": [ { "name": "search", @@ -16,17 +16,17 @@ { "name": "check", "menu-code": "M", - "description": "Check for unread agent messages" + "description": "Check all unread messages — notifications, questions, work orders, handoffs" }, { "name": "send", "menu-code": "T", - "description": "Send a message to another agent" + "description": "Send any message type: notification, question, work-order, handoff, broadcast" }, { - "name": "work-orders", - "menu-code": "W", - "description": "Post, claim, list, or update work orders" + "name": "update-status", + "menu-code": "U", + "description": "Update status on a work order or any message (ready → in-progress → done)" }, { "name": "who-online", diff --git a/src/skills/freya/bmad-manifest.json b/src/skills/freya/bmad-manifest.json index 045ede3aa..4f6576f5c 100644 --- a/src/skills/freya/bmad-manifest.json +++ b/src/skills/freya/bmad-manifest.json @@ -1,6 +1,6 @@ { "name": "wds-freya", - "version": "0.4.0", + "version": "0.4.1", "description": "UX designer, scenario facilitator, and visual design partner", "capabilities": [ { diff --git a/src/skills/saga/bmad-manifest.json b/src/skills/saga/bmad-manifest.json index 8eba7cb5d..0242dc703 100644 --- a/src/skills/saga/bmad-manifest.json +++ b/src/skills/saga/bmad-manifest.json @@ -1,6 +1,6 @@ { "name": "wds-saga", - "version": "0.4.0", + "version": "0.4.1", "description": "Strategic business analyst and product discovery partner", "capabilities": [ {