@bugzy-ai/bugzy 1.8.0 → 1.9.0

package/templates/init/.bugzy/runtime/subagent-memory-guide.md

@@ -1,87 +1,87 @@
-# Sub-Agent Memory: Maintenance Instructions
-
-## What This Memory Is
-
-A focused collection of knowledge relevant to your specific role. This is your working knowledge, not a log of interactions.
-
----
-
-## When to ADD
-
-Add when information:
-- Directly impacts your decisions or outputs
-- Represents a pattern or learning within your domain
-- Prevents repeated mistakes in your area
-
-**Check first**: Does this overlap with main agent knowledge or another sub-agent's domain?
-
----
-
-## When to UPDATE
-
-Update when:
-- Preferences or requirements change within your domain
-- Understanding deepens through repeated interactions
-- Patterns evolve or are refined
-- Multiple related facts can be consolidated
-
-**Replace** outdated information with current understanding.
-
----
-
-## When to REMOVE
-
-Remove when:
-- No longer relevant to current work
-- Better handled by main agent's knowledge
-- Proven incorrect or outdated
-- Never actually used in decision-making
-
-**Test**: "Has this influenced a decision recently? Will it influence one soon?"
-
----
-
-## Core Rules
-
-1. **Stay in your domain** - Don't duplicate main agent knowledge
-2. **Operational over historical** - Keep patterns, not logs
-3. **Patterns over instances** - Generalize from specific events
-4. **Actionable over observational** - Every entry must answer "How does this change what I do?"
-5. **Consolidate aggressively** - Aim for 10-30 high-signal entries
-6. **Update as understanding crystallizes** - Refine vague into specific
-
----
-
-## Quick Decision Tree
-
-```
-New information
-│
-├─ Relevant to my function? No → Ignore or suggest for main agent
-│                           Yes ↓
-│
-├─ Actionable (changes what I do)? No → Don't store
-│                                   Yes ↓
-│
-├─ Duplicates existing? Yes → UPDATE existing entry
-│                       No ↓
-│
-└─ Belongs in main agent? Yes → Move to main agent
-                          No → ADD to my memory
-```
-
----
-
-## Division with Main Agent
-
-**Main Agent** stores:
-- User's overall preferences and background
-- Project-wide decisions
-- Cross-cutting concerns
-
-**You (Sub-Agent)** store:
-- Domain-specific preferences and patterns
-- Tactical learnings within your scope
-- Working knowledge for your specific tasks
-
-**When in doubt**: If multiple sub-agents could use it → Main agent
+# Sub-Agent Memory: Maintenance Instructions
+
+## What This Memory Is
+
+A focused collection of knowledge relevant to your specific role. This is your working knowledge, not a log of interactions.
+
+---
+
+## When to ADD
+
+Add when information:
+- Directly impacts your decisions or outputs
+- Represents a pattern or learning within your domain
+- Prevents repeated mistakes in your area
+
+**Check first**: Does this overlap with main agent knowledge or another sub-agent's domain?
+
+---
+
+## When to UPDATE
+
+Update when:
+- Preferences or requirements change within your domain
+- Understanding deepens through repeated interactions
+- Patterns evolve or are refined
+- Multiple related facts can be consolidated
+
+**Replace** outdated information with current understanding.
+
+---
+
+## When to REMOVE
+
+Remove when:
+- No longer relevant to current work
+- Better handled by main agent's knowledge
+- Proven incorrect or outdated
+- Never actually used in decision-making
+
+**Test**: "Has this influenced a decision recently? Will it influence one soon?"
+
+---
+
+## Core Rules
+
+1. **Stay in your domain** - Don't duplicate main agent knowledge
+2. **Operational over historical** - Keep patterns, not logs
+3. **Patterns over instances** - Generalize from specific events
+4. **Actionable over observational** - Every entry must answer "How does this change what I do?"
+5. **Consolidate aggressively** - Aim for 10-30 high-signal entries
+6. **Update as understanding crystallizes** - Refine vague into specific
+
+---
+
+## Quick Decision Tree
+
+```
+New information
+│
+├─ Relevant to my function? No → Ignore or suggest for main agent
+│                           Yes ↓
+│
+├─ Actionable (changes what I do)? No → Don't store
+│                                   Yes ↓
+│
+├─ Duplicates existing? Yes → UPDATE existing entry
+│                       No ↓
+│
+└─ Belongs in main agent? Yes → Move to main agent
+                          No → ADD to my memory
+```
+
+---
+
+## Division with Main Agent
+
+**Main Agent** stores:
+- User's overall preferences and background
+- Project-wide decisions
+- Cross-cutting concerns
+
+**You (Sub-Agent)** store:
+- Domain-specific preferences and patterns
+- Tactical learnings within your scope
+- Working knowledge for your specific tasks
+
+**When in doubt**: If multiple sub-agents could use it → Main agent

package/templates/init/.bugzy/runtime/templates/test-plan-template.md

@@ -1,50 +1,50 @@
----
-version: 1.0.0
-created_at: [DATE]
-updated_at: [DATE]
-status: draft
----
-
-# Test Plan: [PROJECT_NAME]
-
-## Overview
-
-[2-3 sentences describing what the application does and the testing focus]
-
-## Features to Test
-
-### [Feature Area 1]
-- [ ] Feature 1.1 - Brief description
-- [ ] Feature 1.2 - Brief description
-
-### [Feature Area 2]
-- [ ] Feature 2.1 - Brief description
-- [ ] Feature 2.2 - Brief description
-
-### [Feature Area 3]
-- [ ] Feature 3.1 - Brief description
-
-## Out of Scope
-
-- Item 1 - Reason (e.g., requires native mobile app)
-- Item 2 - Reason (e.g., backend-only, no UI)
-
-## Test Environment
-
-- **URL**: TEST_BASE_URL
-- **User Credentials**: TEST_USER_EMAIL / TEST_USER_PASSWORD
-- **Admin Credentials**: TEST_ADMIN_EMAIL / TEST_ADMIN_PASSWORD (if applicable)
-
-## Automation Priority
-
-| Priority | Criteria |
-|----------|----------|
-| High | Critical user flows, smoke tests, frequent regression areas |
-| Medium | Important features, moderate user impact |
-| Low | Edge cases, rarely used features |
-
-## Notes
-
-- See `./exploration-reports/` for detailed UI element discovery
-- See `.bugzy/runtime/knowledge-base.md` for technical patterns
-- See `.bugzy/runtime/project-context.md` for SDLC and team info
+---
+version: 1.0.0
+created_at: [DATE]
+updated_at: [DATE]
+status: draft
+---
+
+# Test Plan: [PROJECT_NAME]
+
+## Overview
+
+[2-3 sentences describing what the application does and the testing focus]
+
+## Features to Test
+
+### [Feature Area 1]
+- [ ] Feature 1.1 - Brief description
+- [ ] Feature 1.2 - Brief description
+
+### [Feature Area 2]
+- [ ] Feature 2.1 - Brief description
+- [ ] Feature 2.2 - Brief description
+
+### [Feature Area 3]
+- [ ] Feature 3.1 - Brief description
+
+## Out of Scope
+
+- Item 1 - Reason (e.g., requires native mobile app)
+- Item 2 - Reason (e.g., backend-only, no UI)
+
+## Test Environment
+
+- **URL**: TEST_BASE_URL
+- **User Credentials**: TEST_USER_EMAIL / TEST_USER_PASSWORD
+- **Admin Credentials**: TEST_ADMIN_EMAIL / TEST_ADMIN_PASSWORD (if applicable)
+
+## Automation Priority
+
+| Priority | Criteria |
+|----------|----------|
+| High | Critical user flows, smoke tests, frequent regression areas |
+| Medium | Important features, moderate user impact |
+| Low | Edge cases, rarely used features |
+
+## Notes
+
+- See `./exploration-reports/` for detailed UI element discovery
+- See `.bugzy/runtime/knowledge-base.md` for technical patterns
+- See `.bugzy/runtime/project-context.md` for SDLC and team info