agentic-sdlc 1.5.1 → 1.8.1

package/.agent/rules/AUTO-LEARNING.md

@@ -1,418 +0,0 @@
-# 🧠 Automatic Knowledge Base Learning System
-
-## Purpose
-This system automatically captures and stores knowledge from every task, issue, and bug fix to build project intelligence over time.
-
----
-
-## 🔄 Auto-Learning Triggers
-
-### Mandatory Knowledge Capture
-The following events **MUST** trigger automatic knowledge base entry creation:
-
-| Event | Trigger Condition | Auto-Create Entry |
-|-------|------------------|-------------------|
-| **Bug Fixed** | Any bug with priority medium+ | ✅ Yes |
-| **Multiple Attempts** | Task required 3+ attempts | ✅ Yes |
-| **Error Pattern** | Same error occurred 2+ times | ✅ Yes |
-| **Complex Feature** | Implementation took 4+ hours | ✅ Yes |
-| **Security Issue** | Any security vulnerability found | ✅ Yes |
-| **Performance Fix** | Performance optimization applied | ✅ Yes |
-| **Integration Issue** | Third-party integration problem | ✅ Yes |
-| **Platform Issue** | Platform-specific problem solved | ✅ Yes |
-| **Architecture Decision** | Major design decision made | ✅ Yes |
-| **Rollback Event** | Deployment rolled back | ✅ Yes |
-
----
-
-## 📝 Auto-Learning Workflow
-
-### Step 1: Detection (Automatic)
-When any agent completes a task, they MUST check if it meets learning criteria:
-
-```markdown
-### Knowledge Base Check
-- [ ] Bug priority: [critical/high/medium/low]
-- [ ] Attempts required: [number]
-- [ ] Similar issues before: [yes/no]
-- [ ] Implementation complexity: [simple/moderate/complex]
-- [ ] Security impact: [yes/no]
-- [ ] Performance impact: [yes/no]
-
-**Auto-Learn Required:** [YES/NO]
-```
-
-### Step 2: Capture (Automatic)
-If auto-learn is required, immediately create knowledge entry:
-
-```markdown
-## Auto-Generated Knowledge Entry
-
-**Entry ID:** KB-[YYYY-MM-DD]-[###]-[auto-title]
-**Category:** [bugs/features/architecture/security/performance/platform]
-**Severity:** [critical/high/medium/low]
-**Auto-Generated:** Yes
-**Source:** [Task ID / Issue ID / Bug ID]
-
-### Problem
-[Auto-extracted from task description]
-
-### Context
-- Sprint: [N]
-- Component: [name]
-- Technology: [stack]
-- Platform: [web/mobile/desktop/cli]
-
-### Solution Applied
-[Auto-extracted from implementation]
-
-### Root Cause
-[To be filled by agent]
-
-### Prevention
-[To be filled by agent]
-
-### Tags
-#auto-learned #[category] #[technology] #[severity]
-```
-
-### Step 3: Index Update (Automatic)
-Automatically update `knowledge-base/index.md`:
-
-```markdown
-| KB-[date]-[###] | [Title] | [Category] | [Severity] | [Tags] | [Date] | Auto |
-```
-
-### Step 4: Cross-Reference (Automatic)
-Link to related entries:
-- Search for similar keywords
-- Link to related bugs/features
-- Update related entries with new insights
-
----
-
-## 🎯 Role-Specific Auto-Learning
-
-### @DEV - Development Learning
-**Auto-capture when:**
-- Bug fixed (any priority)
-- Code refactoring completed
-- Performance optimization applied
-- Integration implemented
-
-**Knowledge Type:** Code patterns, bug fixes, optimizations
-
-### @DEVOPS - Infrastructure Learning
-**Auto-capture when:**
-- Deployment issue resolved
-- Configuration changed
-- Infrastructure scaled
-- Monitoring alert triggered
-
-**Knowledge Type:** Deployment patterns, infrastructure issues
-
-### @TESTER - Testing Learning
-**Auto-capture when:**
-- Test failure pattern identified
-- Edge case discovered
-- Test automation challenge solved
-- Regression bug found
-
-**Knowledge Type:** Test patterns, edge cases, regression patterns
-
-### @SECA - Security Learning
-**Auto-capture when:**
-- Security vulnerability found
-- Security scan issue resolved
-- Authentication/authorization issue fixed
-- Data protection measure implemented
-
-**Knowledge Type:** Security vulnerabilities, attack patterns, fixes
-
-### @SA - Architecture Learning
-**Auto-capture when:**
-- Architecture decision made
-- Design pattern applied
-- Scalability issue addressed
-- Technology choice made
-
-**Knowledge Type:** Architecture patterns, design decisions
-
-### @UIUX - Design Learning
-**Auto-capture when:**
-- UX issue identified and fixed
-- Accessibility improvement made
-- Design pattern applied
-- User feedback incorporated
-
-**Knowledge Type:** UX patterns, accessibility solutions
-
----
-
-## 🤖 Automated Knowledge Entry Template
-
-Every agent MUST use this template for auto-learning:
-
-```markdown
----
-id: KB-[YYYY-MM-DD]-[###]
-title: [Auto-Generated Title]
-category: [bugs/features/architecture/security/performance/platform]
-severity: [critical/high/medium/low]
-auto-generated: true
-source-task: [Task/Issue/Bug ID]
-sprint: [N]
-date: [YYYY-MM-DD]
-author: [@ROLE]
-tags: [#tag1, #tag2, #tag3]
----
-
-# [Title]
-
-## 📋 Metadata
-- **Entry ID:** KB-[YYYY-MM-DD]-[###]
-- **Category:** [Category]
-- **Severity:** [Severity]
-- **Sprint:** [N]
-- **Date:** [YYYY-MM-DD]
-- **Author:** [@ROLE]
-- **Source:** [Task/Issue/Bug ID]
-- **Auto-Generated:** Yes
-
-## 🔍 Problem Description
-[Clear description of the problem encountered]
-
-## 🌍 Context
-- **Component:** [Component name]
-- **Technology:** [Tech stack]
-- **Platform:** [web/mobile/desktop/cli]
-- **Environment:** [dev/staging/production]
-- **Related Files:** [List of files]
-
-## 🚨 Symptoms
-- [Symptom 1]
-- [Symptom 2]
-- [Symptom 3]
-
-## 🔬 Root Cause Analysis
-[Detailed explanation of why the issue occurred]
-
-## ✅ Solution Applied
-[Step-by-step solution that worked]
-
-```code
-[Code snippets if applicable]
-```
-
-## 🛡️ Prevention Measures
-- [ ] [Prevention measure 1]
-- [ ] [Prevention measure 2]
-- [ ] [Prevention measure 3]
-
-## 📊 Impact Assessment
-- **Severity:** [critical/high/medium/low]
-- **Affected Users:** [number/percentage]
-- **Downtime:** [duration]
-- **Data Loss:** [yes/no]
-
-## 🔗 Related Entries
-- [KB-YYYY-MM-DD-###] - [Related entry title]
-- [KB-YYYY-MM-DD-###] - [Related entry title]
-
-## 📚 References
-- [Documentation link]
-- [Stack Overflow link]
-- [GitHub issue link]
-
-## 🏷️ Tags
-#auto-learned #[category] #[technology] #[severity] #sprint-[N]
-
----
-*Auto-generated by @[ROLE] on [YYYY-MM-DD]*
-```
-
----
-
-## 🔍 Auto-Search Before Starting
-
-Before starting ANY task, agents MUST:
-
-1. **Search Knowledge Base**
-   ```markdown
-   ### Knowledge Base Search
-   - Keywords: [list keywords]
-   - Category: [category]
-   - Technology: [tech]
-   - Results: [number] entries found
-   ```
-
-2. **Review Relevant Entries**
-   - Read top 3 most relevant entries
-   - Check for similar patterns
-   - Adapt solutions to current context
-
-3. **Document Search Results**
-   ```markdown
-   ### KB Search Results
-   - **KB-[date]-[###]:** [Title] - [Relevance: high/medium/low]
-   - **KB-[date]-[###]:** [Title] - [Relevance: high/medium/low]
-   - **Applicable Solutions:** [yes/no]
-   ```
-
----
-
-## 📈 Learning Metrics
-
-Track these metrics in `knowledge-base/index.md`:
-
-| Metric | Description | Target |
-|--------|-------------|--------|
-| **Total Entries** | Number of KB entries | Growing |
-| **Auto-Generated** | Percentage auto-created | >80% |
-| **Reuse Rate** | Entries referenced in tasks | >50% |
-| **Resolution Time** | Average time to fix similar issues | Decreasing |
-| **Recurrence Rate** | Same issue occurring again | <10% |
-
----
-
-## 🎯 Quality Standards for Auto-Learning
-
-Every auto-generated entry MUST include:
-
-- ✅ Clear problem description
-- ✅ Reproducible steps (if applicable)
-- ✅ Root cause analysis
-- ✅ Working solution with code
-- ✅ Prevention measures
-- ✅ Proper categorization
-- ✅ Relevant tags
-- ✅ Cross-references
-
----
-
-## 🔄 Continuous Improvement
-
-### Weekly Review
-Every Friday, @REPORTER MUST:
-1. Review all auto-generated entries from the week
-2. Verify completeness and quality
-3. Add missing details
-4. Update cross-references
-5. Archive duplicates
-
-### Monthly Analysis
-Every month-end, @REPORTER MUST:
-1. Analyze learning metrics
-2. Identify knowledge gaps
-3. Consolidate similar entries
-4. Update index and categories
-5. Generate learning report
-
-### Quarterly Optimization
-Every quarter, @PM + @REPORTER MUST:
-1. Review entire knowledge base
-2. Archive outdated entries
-3. Refactor categories if needed
-4. Update templates
-5. Train team on new patterns
-
----
-
-## 🚀 Integration with Workflow
-
-### In Development Log
-```markdown
-## Knowledge Base Integration
-- **KB Entries Created:** [number]
-- **KB Entries Referenced:** [number]
-- **New Patterns Learned:** [list]
-- **Prevention Measures Applied:** [list]
-```
-
-### In Test Report
-```markdown
-## Knowledge Base Integration
-- **Test Patterns Learned:** [list]
-- **Edge Cases Documented:** [number]
-- **Regression Patterns:** [list]
-```
-
-### In Phase Report
-```markdown
-## Knowledge Base Summary
-- **Total KB Entries:** [number]
-- **Categories:** [breakdown]
-- **Most Referenced:** [top 3]
-- **Learning Impact:** [description]
-```
-
----
-
-## 🎓 Learning Categories
-
-### 1. Bug Patterns
-- Error messages and solutions
-- Common mistakes
-- Edge cases
-- Regression patterns
-
-### 2. Feature Patterns
-- Implementation approaches
-- Design patterns
-- Best practices
-- Anti-patterns to avoid
-
-### 3. Architecture Patterns
-- Design decisions
-- Scalability solutions
-- Technology choices
-- Integration patterns
-
-### 4. Security Patterns
-- Vulnerabilities and fixes
-- Security best practices
-- Attack patterns
-- Protection measures
-
-### 5. Performance Patterns
-- Optimization techniques
-- Bottleneck solutions
-- Caching strategies
-- Resource management
-
-### 6. Platform Patterns
-- Platform-specific issues
-- Cross-platform solutions
-- Device-specific problems
-- Browser compatibility
-
----
-
-## 🔐 Access Control
-
-| Role | Create | Read | Update | Delete |
-|------|--------|------|--------|--------|
-| @DEV | ✅ | ✅ | ✅ | ❌ |
-| @DEVOPS | ✅ | ✅ | ✅ | ❌ |
-| @TESTER | ✅ | ✅ | ✅ | ❌ |
-| @SECA | ✅ | ✅ | ✅ | ❌ |
-| @SA | ✅ | ✅ | ✅ | ❌ |
-| @UIUX | ✅ | ✅ | ✅ | ❌ |
-| @REPORTER | ✅ | ✅ | ✅ | ✅ |
-| @PM | ❌ | ✅ | ❌ | ❌ |
-| @PO | ❌ | ✅ | ❌ | ❌ |
-
----
-
-## 📞 Support
-
-If you need help with auto-learning:
-- **What to capture:** Tag @REPORTER
-- **How to document:** Use template above
-- **Where to store:** Check category structure
-- **Quality issues:** Tag @REPORTER for review
-
----
-
-#auto-learning #knowledge-base #continuous-improvement #project-intelligence
-

package/.agent/rules/KNOWLEDGE-BASE.md

@@ -1,45 +0,0 @@
----
-description: Knowledge Base System Rules
----
-
-# Knowledge Base System Rules
-
-## Purpose
-The Knowledge Base stores lessons learned, bug patterns, difficult features, and solutions that required multiple attempts. This serves as project memory for future reference.
-
-## When to Create Entry
-Create a knowledge entry when:
-- Bug required 3+ attempts to fix
-- Feature implementation was particularly challenging
-- Solution was non-obvious or counter-intuitive
-- Issue is likely to recur in similar projects
-- Root cause analysis revealed important insights
-
-## Entry Naming
-**Format:** `KB-[YYYY-MM-DD]-[###]-[short-title].md`
-
-**Location:** `.agent/knowledge-base/[category]/[severity]/`
-
-## Categories
-| Category | Folder | Description |
-|----------|--------|-------------|
-| Bugs | `knowledge-base/bugs/[severity]/` | Bug patterns and fixes |
-| Features | `knowledge-base/features/[type]/` | Complex feature implementations |
-| Architecture | `knowledge-base/architecture/` | Architecture decisions |
-| Security | `knowledge-base/security/` | Security issues and solutions |
-| Performance | `knowledge-base/performance/` | Performance optimizations |
-| Platform | `knowledge-base/platform-specific/[platform]/` | Platform-specific issues |
-
-## Workflow
-1. **Create Entry:** Use `Knowledge-Entry-Template.md`
-2. **Document:** Include problem, root cause, solution, prevention
-3. **Tag:** Add appropriate tags for searchability
-4. **Update Index:** Add to `knowledge-base/index.md`
-5. **Notify:** Tag @REPORTER for review
-
-## Search Before Starting
-Before implementing complex features or fixing bugs:
-1. Check `knowledge-base/index.md`
-2. Search by keywords, technology, or error messages
-3. Review similar entries
-4. Adapt solutions to current context

package/.agent/skills/role-qa.md

@@ -1,81 +0,0 @@
----
-inclusion: manual
----
-
-# Quality Assurance (QA) Role
-
-When acting as @QA, you are the Quality Assurance engineer responsible for design review and testing strategy.
-
-## Role Activation
-Activate when user mentions: `@QA`, "quality assurance", "design review", "testing strategy"
-
-## Primary Responsibilities
-
-1. **Review Design Artifacts**
-   - Read `Project-Plan-v*.md`
-   - Review `UIUX-Design-Spec-Sprint-[N]-v*.md`
-   - Review `Backend-Design-Spec-Sprint-[N]-v*.md`
-
-2. **Perform Design Review**
-   - Verify requirement coverage (all features addressed)
-   - Check consistency between UI and backend designs
-   - Assess testability of proposed solutions
-   - Identify edge cases and error scenarios
-   - Validate acceptance criteria are clear
-
-3. **Define Testing Strategy**
-   - Specify types of testing needed (unit, integration, E2E)
-   - Define test classes and scenarios
-   - Document acceptance criteria for each feature
-   - Identify testing tools and frameworks
-
-4. **Risk Assessment**
-   - Identify potential quality risks
-   - Flag incomplete or ambiguous requirements
-   - Highlight areas needing clarification
-
-5. **Make Decision**
-   - APPROVED: Design is complete and testable
-   - REJECTED: Critical issues must be addressed
-
-## Artifact Requirements
-
-**Output Location:** `docs/sprints/sprint-[N]/reviews/`
-**Filename Format:** `Design-Verification-Report-Sprint-[N]-v[version].md`
-
-**Required Sections:**
-- Review Summary
-- Requirement Coverage Analysis
-- Design Consistency Check
-- Testability Assessment
-- Edge Cases & Error Scenarios
-- Testing Strategy
-- Issues Found (Critical/High/Medium/Low)
-- Decision: APPROVED or REJECTED
-
-## Strict Rules
-
-- ❌ NEVER approve if critical/high issues exist
-- ❌ NEVER place artifacts in `.agent/` directory
-- ✅ ALWAYS document with `#verify-design` tag
-- ✅ ALWAYS provide clear decision with reasoning
-
-## Communication Template
-
-End your report with:
-
-```markdown
-### Design Review Decision: [APPROVED / REJECTED]
-
-### Next Step:
-- If APPROVED: @DEV @DEVOPS - Please proceed with implementation
-- If REJECTED: @SA @UIUX - Please address the issues listed above and submit revised designs
-
-#verify-design #qa
-```
-
-## MCP Tools to Leverage
-
-- **File Tools** - Read all design artifacts
-- **Web Search** - Research testing best practices
-- **Diagnostic Tools** - Check for existing test coverage

package/.agent/workflows/compound.md

@@ -1,51 +0,0 @@
----
-description: [Support] Compound Knowledge Capture - After Tasks
----
-
-# Compound Learning Workflow
-
-## ⚠️ STRICT EXECUTION PROTOCOL (MANDATORY)
-This workflow MUST be executed after completing any significant task.
-
-## When to Use
-- After fixing a bug (medium+ priority)
-- After completing a feature
-- After resolving a complex problem (3+ hours)
-
-## Steps
-
-### 1. Create KB Entry
-```bash
-cp .agent/templates/Knowledge-Entry-Template.md \
-   .agent/knowledge-base/[category]/KB-$(date +%Y-%m-%d)-###-[name].md
-```
-
-### 2. Fill Entry
-- Problem/Challenge
-- Solution
-- Implementation details
-- Learnings
-
-### 3. Sync to Neo4j
-```bash
-python tools/neo4j/sync_skills_to_neo4j.py
-```
-
-### 4. Update KB Index
-```bash
-python bin/kb_cli.py update-index
-```
-
-### 5. Record Success (Learning Engine)
-```bash
-python tools/neo4j/learning_engine.py --record-success "TASK-ID" --task-type "feature"
-```
-
-#compound #learning #knowledge-base
-
-
----
-
-## ENFORCEMENT REMINDER
-Before executing, complete /preflight checks.
-

package/.agent/workflows/preflight.md

@@ -1,35 +0,0 @@
----
-description: [Support] Pre-flight workflow checker - Run BEFORE any task
----
-# Pre-Flight Workflow
-> **MANDATORY:** This workflow MUST be executed conceptually before ANY task.
-## Step 1: Identify Task Type
-Analyze user request and determine:
-- Is this a new feature? -> Use /orchestrator
-- Is this a bug fix? -> Use /cycle
-- Is this investigation? -> Use /explore
-- Is this emergency? -> Use /emergency
-## Step 2: Read Workflow File
-`bash
-# For /orchestrator tasks
-cat .agent/workflows/orchestrator.md
-# For /cycle tasks  
-cat .agent/workflows/cycle.md
-`
-## Step 3: Search Knowledge Base
-`bash
-grep -r "relevant_keyword" .agent/knowledge-base/
-`
-## Step 4: Check Brain State
-`bash
-python tools/brain/brain_cli.py status
-`
-## Step 5: Identify Required Roles
-Based on task type, activate roles:
-- @PM for planning
-- @SA for architecture  
-- @DEV for implementation
-- @TESTER for testing
-## Step 6: Proceed with Workflow
-Now follow the identified workflow file step-by-step.
-#preflight #mandatory #enforcement