agentvibes 2.17.8 → 3.0.0

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.
@@ -0,0 +1,54 @@
1
+ # BMAD Agent Activation Instructions
2
+
3
+ When a BMAD agent activates, follow these steps EXACTLY:
4
+
5
+ ## STEP 3.5a: Create BMAD Context File (CRITICAL)
6
+
7
+ **IMMEDIATELY after agent identification, create the context file:**
8
+
9
+ ```bash
10
+ echo "$AGENT_ID" > .bmad-agent-context
11
+ ```
12
+
13
+ Where `$AGENT_ID` is one of:
14
+ - `pm` (Product Manager)
15
+ - `dev` (Developer)
16
+ - `qa` (QA)
17
+ - `architect` (Architect)
18
+ - `po` (Product Owner)
19
+ - `analyst` (Analyst)
20
+ - `sm` (Scrum Master)
21
+ - `ux-expert` (UX Expert)
22
+ - `bmad-master` (BMAD Master)
23
+ - `bmad-orchestrator` (Orchestrator)
24
+
25
+ **Example:**
26
+ ```bash
27
+ # For Product Manager agent
28
+ echo "pm" > .bmad-agent-context
29
+ ```
30
+
31
+ This file allows AgentVibes to:
32
+ 1. Detect which BMAD agent is active
33
+ 2. Look up the correct voice mapping
34
+ 3. Automatically speak questions using the agent's assigned voice
35
+
36
+ ## STEP 10: Clean Up on Exit
37
+
38
+ **Before exiting the agent, remove the context file:**
39
+
40
+ ```bash
41
+ rm -f .bmad-agent-context
42
+ ```
43
+
44
+ This ensures voice switching only happens when an agent is active.
45
+
46
+ ## Why This Matters
47
+
48
+ Without the `.bmad-agent-context` file:
49
+ - AgentVibes cannot detect which agent is active
50
+ - Questions won't be spoken automatically
51
+ - Voice switching won't work
52
+ - The BMAD voice plugin becomes non-functional
53
+
54
+ **This is MANDATORY for BMAD voice integration to work!**
Binary file