@bugzy-ai/bugzy 1.4.0 → 1.6.0

package/dist/templates/init/.bugzy/runtime/knowledge-base.md

@@ -0,0 +1,61 @@
+# Knowledge Base
+
+> A curated collection of factual knowledge about this project - what we currently know and believe to be true. This is NOT a historical log, but a living reference that evolves as understanding improves.
+
+**Maintenance Guide**: See `knowledge-maintenance-guide.md` for instructions on how to maintain this knowledge base.
+
+**Core Principle**: This document represents current understanding, not a history. When knowledge evolves, update existing entries rather than appending new ones.
+
+---
+
+## Project Knowledge
+
+_This knowledge base will be populated as you work. Add new discoveries, update existing understanding, and remove outdated information following the maintenance guide principles._
+
+### When to Update This File
+
+- **ADD**: New factual information discovered, new patterns emerge, new areas become relevant
+- **UPDATE**: Facts change, understanding deepens, multiple facts can be consolidated, language can be clarified
+- **REMOVE**: Information becomes irrelevant, facts proven incorrect, entries superseded by better content
+
+### Format Guidelines
+
+- Use clear, declarative statements in present tense
+- State facts confidently when known; flag uncertainty when it exists
+- Write for someone reading this 6 months from now
+- Keep entries relevant and actionable
+- Favor consolidation over accumulation
+
+---
+
+## Example Structure
+
+Below is an example structure. Feel free to organize knowledge in the way that makes most sense for this project:
+
+### Architecture & Infrastructure
+
+_System architecture, deployment patterns, infrastructure details_
+
+### Testing Patterns
+
+_Test strategies, common test scenarios, testing conventions_
+
+### UI/UX Patterns
+
+_User interface conventions, interaction patterns, design system details_
+
+### Data & APIs
+
+_Data models, API behaviors, integration patterns_
+
+### Known Issues & Workarounds
+
+_Current limitations, known bugs, and their workarounds_
+
+### Domain Knowledge
+
+_Business domain facts, terminology, rules, and context_
+
+---
+
+**Remember**: Every entry should answer "Will this help someone working on this project in 6 months?"

package/dist/templates/init/.bugzy/runtime/knowledge-maintenance-guide.md

@@ -0,0 +1,97 @@
+# Knowledge Maintenance Guide
+
+## Overview
+
+This document provides instructions for maintaining a **Context** or **Knowledge Base** - a living collection of factual knowledge that is actively curated and updated rather than simply accumulated over time.
+
+---
+
+## Core Principle: This is a Curated Snapshot, Not a Log
+
+This document represents **what we currently know and believe to be true**, not a history of what we've learned. Think of it as a living reference that evolves as understanding improves.
+
+---
+
+## When to ADD
+
+Add new entries when:
+
+- New factual information is discovered
+- New patterns or relationships emerge
+- New areas of knowledge become relevant
+
+**Check first**: Does this duplicate or overlap with existing entries?
+
+---
+
+## When to UPDATE
+
+Update existing entries when:
+
+- Facts change or we discover more accurate information
+- Understanding deepens (replace shallow with deeper insight)
+- Multiple related facts can be consolidated into one coherent statement
+- Language can be clarified or made more precise
+
+**Goal**: Replace outdated understanding with current understanding
+
+---
+
+## When to REMOVE
+
+Remove entries when:
+
+- Information becomes irrelevant to current needs
+- Facts are proven incorrect (unless there's value in noting the correction)
+- Information is superseded by better, more comprehensive entries
+- Entry is redundant with other content
+
+**Key question**: "If someone reads this in 6 months, will it help them?"
+
+---
+
+## Maintenance Principles
+
+### 1. Favor Consolidation Over Addition
+
+- Before adding, ask: "Can this merge with existing knowledge?"
+- Example: Instead of 10 facts about a person, maintain 2-3 well-organized paragraphs
+
+### 2. Update Rather Than Append
+
+- When information evolves, replace the old statement
+- Keep history only if the evolution itself is important
+- Example: ~~"User is learning Python"~~ → "User is proficient in Python and focusing on FastAPI"
+
+### 3. Regular Pruning
+
+- Periodically review for outdated or low-value entries
+- Ask: "Is this still accurate? Still relevant? Could it be stated better?"
+- Aim for signal-to-noise ratio improvement
+
+### 4. Quality Over Completeness
+
+- Better to have 50 highly relevant, accurate facts than 500 marginally useful ones
+- Prioritize insights over raw data
+- Focus on what's actionable or decision-relevant
+
+### 5. Resolve Contradictions Immediately
+
+- If new information contradicts old, investigate and keep only the truth
+- Don't accumulate conflicting statements
+
+### 6. Use Clear, Declarative Statements
+
+- Write in present tense: "User works at X" not "User mentioned they work at X"
+- State facts confidently when known; flag uncertainty when it exists
+- Avoid hedging unless genuinely uncertain
+
+---
+
+## Anti-Patterns to Avoid
+
+| ❌ Don't Do This | ✅ Do This Instead |
+|-----------------|-------------------|
+| "On Tuesday user said X, then on Friday user said Y" | "User's position on X is Y" (keep most current) |
+| Keeping every detail ever mentioned | Keeping relevant, current details |
+| "User might like coffee, user mentioned tea once, user drinks water" | "User prefers tea; also drinks coffee occasionally" |

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

@@ -0,0 +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

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

@@ -1,25 +1,50 @@
-# Test Plan Template
+---
+version: 1.0.0
+created_at: [DATE]
+updated_at: [DATE]
+status: draft
+---
 
-## Test Scenarios
+# Test Plan: [PROJECT_NAME]
 
-### Scenario 1: [Name]
-**Objective**: [What are we testing?]
+## Overview
 
-**Test Cases**:
-1. [Test case description]
-2. [Test case description]
+[2-3 sentences describing what the application does and the testing focus]
 
-**Expected Results**:
-- [Expected outcome]
+## Features to Test
 
-### Scenario 2: [Name]
-**Objective**: [What are we testing?]
+### [Feature Area 1]
+- [ ] Feature 1.1 - Brief description
+- [ ] Feature 1.2 - Brief description
 
-**Test Cases**:
-1. [Test case description]
+### [Feature Area 2]
+- [ ] Feature 2.1 - Brief description
+- [ ] Feature 2.2 - Brief description
 
-**Expected Results**:
-- [Expected outcome]
+### [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
-[Add any additional context or requirements]
+
+- 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