|
1 | | -# 📘 BA-Kit Usage Guide (Antigravity Native) |
| 1 | +# 📘 BA-Kit: The Antigravity Codex (v2.4.1) |
2 | 2 |
|
3 | | -**Welcome to the Cognitive Swarm.** |
4 | | -This guide explains how to pilot the 15 Agents of the BA-Kit to achieve "World Class" results. |
| 3 | +> **"We don't just chat. We think, we link, and we remember."** |
5 | 4 |
|
6 | | ---- |
7 | | - |
8 | | -## 🏗️ Architecture: The "System 2" Difference |
9 | | - |
10 | | -Unlike standard "Chat with LLM" workflows, BA-Kit agents operate on a **Cognitive Loop**: |
11 | | - |
12 | | -1. **Stimulus**: User Input. |
13 | | -2. **System 1 (Fast)**: The Agent drafts an immediate response based on pattern matching. |
14 | | -3. **System 2 (Slow)**: The Agent **Reflects**. |
15 | | - * It critiques its own draft ("Is this too vague?"). |
16 | | - * It checks for hallucinations ("Did I invent that dependency?"). |
17 | | - * It verifies facts ("Let me grep the codebase to be sure"). |
18 | | -4. **Response**: The polished, verified output. |
19 | | - |
20 | | -**Benefit**: You get fewer errors, better math, and real citations. |
| 5 | +Welcome to the **Cognitive Squad (Antigravity Native)**. |
| 6 | +This is not a chatbot. It is a **Multi-Agent Expert System** designated to enable **High-Assurance Business Analysis** (inspired by CMMI Level 5). |
21 | 7 |
|
22 | 8 | --- |
23 | 9 |
|
24 | | -## 🚦 The 15 Agents: When to Use Who? |
| 10 | +## 🌌 The Philosophy: Three Pillars of Intelligence |
25 | 11 |
|
26 | | -### 🔴 The Boss |
27 | | -* **`@ba-master`**: Use when you don't know who to use. "I have a problem, help." |
| 12 | +To master this kit, you must understand how the Squad "thinks". |
28 | 13 |
|
29 | | -### 🔵 The Creator Phase (Lifecycle Start) |
30 | | -1. **`@ba-identity`**: Start here. Define *Who* are the stakeholders? Who is the Sponsor? |
31 | | -2. **`@ba-elicitation`**: Use this to interview users. "What do you need?" (Funnel Questioning). |
32 | | -3. **`@ba-writing`**: Use this to draft the Requirements (User Stories / GHERKIN). |
| 14 | +### 1. 🧠 System 2 Cognition (The Brain) |
| 15 | +Standard AI answers instantly (System 1). This is prone to hallucination. |
| 16 | +**Our Agents Stop & Think.** |
| 17 | +* **Reflection Loop**: Before speaking, every agent critiques its own draft. |
| 18 | +* **Tool Mandates**: They don't guess math (they use Python). They don't guess links (they use Grep). |
33 | 19 |
|
34 | | -### 🟡 The Engineering Phase (Lifecycle Middle) |
35 | | -4. **`@ba-nfr`**: Define *Constraints*. "How fast? How secure?" (ISO 25010). |
36 | | -5. **`@ba-process`**: Draw the flow. "Visualize the checkout process." (BPMN). |
37 | | -6. **`@ba-traceability`**: Map the links. "What breaks if I change X?" (Graph Theory). |
38 | | -7. **`@ba-conflict`**: Resolve fights. "Sales wants A, Dev wants B." (Harvard Negotiation). |
| 20 | +### 2. 🤝 Squad Collaboration (The Network) |
| 21 | +Agents are no longer isolated. They form a **Collaborative Network (DAG)**. |
| 22 | +* **Old Way**: You call `@ba-writing`. It finishes. You wonder what to do next. |
| 23 | +* **New Way**: `@ba-writing` finishes and *advises you*: "Handover: Summon `@ba-validation` to QA this draft." |
39 | 24 |
|
40 | | -### 🟣 The Optimization Phase (Lifecycle End) |
41 | | -8. **`@ba-validation`**: Check quality. "Find bugs in this spec." (Visual QA). |
42 | | -9. **`@ba-prioritization`**: Decide order. "What do we build first?" (WSJF). |
43 | | -10. **`@ba-solution`**: Check money. "Is this profitable?" (ROI/NPV). |
44 | | -11. **`@ba-export`**: Publish. "Make it a PDF." (Compliance). |
| 25 | +### 3. 📒 Mission Log (The Memory) |
| 26 | +The Squad shares a "Working Brain" via `templates/CONTINUITY.md`. |
| 27 | +* **Problem**: "I told `@ba-elicitation` we are an Agile team, but `@ba-nfr` thinks we are Waterfall." |
| 28 | +* **Solution**: You define the Context ONCE in the Mission Log. All 15 agents read it before acting. |
45 | 29 |
|
46 | | -### ⚫ The "Level 5" Phase (Deep Optimization) |
47 | | -12. **`@ba-metrics`**: Audit the *Process*. "Are we getting faster or just sloppier?" (SPC). |
48 | | -13. **`@ba-root-cause`**: Fix the *System*. "Why do we keep having bugs?" (5 Whys). |
49 | | -14. **`@ba-innovation`**: Design *Experiments*. "Will AI help?" (A/B Testing). |
| 30 | +--- |
| 31 | + |
| 32 | +## 🚦 The Roster: 15 Specialists, One Mission |
| 33 | + |
| 34 | +| Agent | The Archetype | When to Summon | |
| 35 | +| :--- | :--- | :--- | |
| 36 | +| **COMMANDER** | | | |
| 37 | +| **`@ba-master`** | *Mission Control* | "I'm lost. Review my situation and tell me who to call." | |
| 38 | +| **CREATIVE SQUAD** | | | |
| 39 | +| **`@ba-identity`** | *Chief of Staff* | "New project. Who are the stakeholders? Who matters?" | |
| 40 | +| **`@ba-elicitation`**| *The Journalist* | "I need Requirements. Interview me." (Funnel Method) | |
| 41 | +| **`@ba-writing`** | *The Architect*| "Turn these raw notes into Gherkin User Stories." | |
| 42 | +| **ENGINEERING SQUAD**| | | |
| 43 | +| **`@ba-nfr`** | *The SRE* | "Define the Non-Functional Constraints (ISO 25010)." | |
| 44 | +| **`@ba-process`** | *Lean Master* | "Visualize this messy workflow as a BPMN diagram." | |
| 45 | +| **`@ba-traceability`**| *Graph Theorist*| "What happens if I change this requirement? Trace the impact." | |
| 46 | +| **`@ba-conflict`** | *The Diplomat* | "Sales and Eng are fighting. Help us negotiate (Harvard Method)." | |
| 47 | +| **OPTIMIZATION SQUAD**| | | |
| 48 | +| **`@ba-validation`** | *The Critic* | "Roast this spec. Find every bug and logical fallacy." | |
| 49 | +| **`@ba-prioritization`**| *The Strategist*| "We have too many features. Rank them (WSJF/RICE)." | |
| 50 | +| **`@ba-solution`** | *The Investor* | "Calculate the ROI of this feature. Use Python." | |
| 51 | +| **`@ba-export`** | *The Publisher* | "Compile everything into a compliant DOCX for the client." | |
| 52 | +| **PRECOG SQUAD (Level 5)**| | | |
| 53 | +| **`@ba-metrics`** | *Data Scientist* | "Is our Quality Control stable? Show me the Control Chart." | |
| 54 | +| **`@ba-root-cause`** | *The Detective* | "We failed. Find the Root Cause (5 Whys)." | |
| 55 | +| **`@ba-innovation`** | *The Futurist* | "Design an A/B test to prove this idea works." | |
50 | 56 |
|
51 | 57 | --- |
52 | 58 |
|
53 | | -## 🛠️ Tool Mandates (Why Agents Run Commands) |
| 59 | +## ⚔️ Tactical Protocols |
54 | 60 |
|
55 | | -You will see Agents running `run_command` or `grep_search`. **Do not stop them.** |
| 61 | +### Protocol 1: The "Context Injection" |
| 62 | +**Stop repeating yourself.** |
| 63 | +1. Copy `templates/CONTINUITY.md` to your root. |
| 64 | +2. Fill it out: `Goal: MVP Release`. `Constraint: Mobile Only`. |
| 65 | +3. **Result**: Every agent now knows this. |
56 | 66 |
|
57 | | -* **Python**: Used by `@ba-solution`, `@ba-innovation`, `@ba-metrics` to ensure **Math Integrity**. LLMs cannot add; Python can. |
58 | | -* **Grep**: Used by `@ba-traceability` to ensure **Link Integrity**. The Agent must "see" the file to link it. |
59 | | -* **Web Search**: Used by `@ba-nfr` to ensure **Standard Integrity**. It checks the live web for GDPR/ISO updates. |
| 67 | +### Protocol 2: The "Visual Stimulus" |
| 68 | +**Stop describing UI.** |
| 69 | +1. Take a screenshot of a whiteboard or mockup. |
| 70 | +2. Drag & Drop it into the chat. |
| 71 | +3. Command: `@[image] @ba-writing Convert this UI into Field Specifications.` |
60 | 72 |
|
61 | | ---- |
| 73 | +### Protocol 3: The "Hypothesis Check" |
| 74 | +**Stop guessing.** |
| 75 | +1. Don't say "I think this is a good idea." |
| 76 | +2. Command: `@ba-solution Calculate the Net Present Value (NPV) if adoption is 5%.` |
| 77 | +3. Watch the agent write a Python script to prove you right (or wrong). |
62 | 78 |
|
63 | | -## 🎓 Pro-Tips |
| 79 | +--- |
64 | 80 |
|
65 | | -### 1. The "Persona Handover" |
66 | | -You can chain agents manually for powerful workflows: |
67 | | -> *User*: `@ba-elicitation Interview me about the Login feature.` |
68 | | -> *(Conversation happens...)* |
69 | | -> *User*: `Great. Now @ba-writing turn that interview into Gherkin scenarios.` |
| 81 | +## 🚀 How to Begin (Zero-Shot) |
70 | 82 |
|
71 | | -### 2. The "Bias Check" |
72 | | -If sure an Agent is being too nice, ask it to use its Critic Mode explicitly: |
73 | | -> *User*: `@ba-validation Roast this requirement. Be extremely harsh.` |
| 83 | +You do not need to learn complex prompts. The Agents know what to do. |
74 | 84 |
|
75 | | -### 3. The "Visual Scan" |
76 | | -You can show images to Agents (Drag & Drop): |
77 | | -> *User*: `@[image.png] @ba-writing Write UI requirements based on this mockup.` |
| 85 | +**Just Type:** |
| 86 | +> `@ba-master I want to build a payment gateway.` |
78 | 87 |
|
79 | | ---- |
| 88 | +**The Squad will take over:** |
| 89 | +1. `@ba-master` will analyze the request. |
| 90 | +2. It will route you to `@ba-identity` to identify who is paying. |
| 91 | +3. `@ba-identity` will route you to `@ba-elicitation` to gather needs. |
| 92 | +4. The **Chain Reaction** begins. |
80 | 93 |
|
81 | | -**End of Guide** |
82 | | -*Go forth and Engineer.* |
| 94 | +*Welcome to System 2.* |
0 commit comments