agentic-sdlc 1.0.0

package/.agent/ide-integration/vscode-commands.json

@@ -0,0 +1,190 @@
+{
+  "commands": [
+    {
+      "command": "/pm",
+      "description": "Project Manager - Planning, scope management, team coordination",
+      "prompt": "@PM - ",
+      "category": "TeamLifecycle",
+      "icon": "project",
+      "examples": [
+        "/pm Build a todo app with authentication",
+        "/pm Review current project status",
+        "/pm Update project plan based on feedback"
+      ]
+    },
+    {
+      "command": "/orchestrator",
+      "description": "Orchestrator - Auto-execute entire workflow",
+      "prompt": "@ORCHESTRATOR - ",
+      "category": "TeamLifecycle",
+      "icon": "robot",
+      "examples": [
+        "/orchestrator Enable full-auto mode",
+        "/orchestrator Status",
+        "/orchestrator Pause"
+      ]
+    },
+    {
+      "command": "/po",
+      "description": "Product Owner - Backlog management, feature prioritization",
+      "prompt": "@PO - ",
+      "category": "TeamLifecycle",
+      "icon": "list-ordered",
+      "examples": [
+        "/po Prioritize backlog items",
+        "/po Add user story for authentication",
+        "/po Review acceptance criteria"
+      ]
+    },
+    {
+      "command": "/sa",
+      "description": "System Analyst - Architecture, data models, API design",
+      "prompt": "@SA - ",
+      "category": "TeamLifecycle",
+      "icon": "server",
+      "examples": [
+        "/sa Design backend architecture",
+        "/sa Review database schema",
+        "/sa Define API endpoints"
+      ]
+    },
+    {
+      "command": "/uiux",
+      "description": "UI/UX Designer - Interface design, user experience",
+      "prompt": "@UIUX - ",
+      "category": "TeamLifecycle",
+      "icon": "paintbrush",
+      "examples": [
+        "/uiux Design login page",
+        "/uiux Create mobile-first dashboard",
+        "/uiux Review accessibility compliance"
+      ]
+    },
+    {
+      "command": "/qa",
+      "description": "QA Analyst - Design review, quality assurance",
+      "prompt": "@QA - ",
+      "category": "TeamLifecycle",
+      "icon": "checklist",
+      "examples": [
+        "/qa Review design specifications",
+        "/qa Verify testability",
+        "/qa Check requirements coverage"
+      ]
+    },
+    {
+      "command": "/seca",
+      "description": "Security Analyst - Security assessment, vulnerability analysis",
+      "prompt": "@SECA - ",
+      "category": "TeamLifecycle",
+      "icon": "shield",
+      "examples": [
+        "/seca Review authentication flow",
+        "/seca Check for XSS vulnerabilities",
+        "/seca Audit API security"
+      ]
+    },
+    {
+      "command": "/dev",
+      "description": "Developer - Code implementation",
+      "prompt": "@DEV - ",
+      "category": "TeamLifecycle",
+      "icon": "code",
+      "examples": [
+        "/dev Implement login feature",
+        "/dev Fix bug BUG-001",
+        "/dev Refactor authentication module"
+      ]
+    },
+    {
+      "command": "/devops",
+      "description": "DevOps Engineer - CI/CD, deployment, infrastructure",
+      "prompt": "@DEVOPS - ",
+      "category": "TeamLifecycle",
+      "icon": "rocket",
+      "examples": [
+        "/devops Setup CI/CD pipeline",
+        "/devops Deploy to staging",
+        "/devops Configure monitoring"
+      ]
+    },
+    {
+      "command": "/tester",
+      "description": "Tester - Functional testing, bug detection",
+      "prompt": "@TESTER - ",
+      "category": "TeamLifecycle",
+      "icon": "beaker",
+      "examples": [
+        "/tester Test login functionality",
+        "/tester Run E2E tests",
+        "/tester Verify bug fixes"
+      ]
+    },
+    {
+      "command": "/reporter",
+      "description": "Reporter - Progress reports, documentation",
+      "prompt": "@REPORTER - ",
+      "category": "TeamLifecycle",
+      "icon": "file-text",
+      "examples": [
+        "/reporter Generate progress report",
+        "/reporter Update master documentation",
+        "/reporter Create phase report"
+      ]
+    },
+    {
+      "command": "/stakeholder",
+      "description": "Stakeholder - Final approval, business acceptance",
+      "prompt": "@STAKEHOLDER - ",
+      "category": "TeamLifecycle",
+      "icon": "person",
+      "examples": [
+        "/stakeholder Review final deliverables",
+        "/stakeholder Approve project completion",
+        "/stakeholder Provide feedback"
+      ]
+    },
+    {
+      "command": "/auto",
+      "description": "Start project with full automation",
+      "prompt": "@PM - {input} --mode=full-auto",
+      "category": "TeamLifecycle",
+      "icon": "zap",
+      "examples": [
+        "/auto Build a todo app with authentication"
+      ]
+    },
+    {
+      "command": "/semi-auto",
+      "description": "Start project with semi-automation",
+      "prompt": "@PM - {input} --mode=semi-auto",
+      "category": "TeamLifecycle",
+      "icon": "play-circle",
+      "examples": [
+        "/semi-auto Build a mobile fitness app"
+      ]
+    },
+    {
+      "command": "/kb-search",
+      "description": "Search knowledge base for solutions",
+      "prompt": "Search the knowledge base at .agent/knowledge-base/ for: {input}",
+      "category": "Knowledge Base",
+      "icon": "search",
+      "examples": [
+        "/kb-search authentication bug",
+        "/kb-search React hydration error",
+        "/kb-search performance optimization"
+      ]
+    },
+    {
+      "command": "/kb-add",
+      "description": "Add entry to knowledge base",
+      "prompt": "Create a knowledge base entry using the template at .agent/templates/Knowledge-Entry-Template.md for: {input}",
+      "category": "Knowledge Base",
+      "icon": "plus-circle",
+      "examples": [
+        "/kb-add OAuth token refresh issue"
+      ]
+    }
+  ]
+}

package/.agent/ide-integration/windsurf-cascade.md

@@ -0,0 +1,125 @@
+# Windsurf Cascade - TeamLifecycle Integration
+
+## Custom Instructions for Windsurf Cascade
+
+Add this to your project's `.windsurfrules` or Cascade settings:
+
+```markdown
+# TeamLifecycle SDLC Roles for Cascade
+
+## Slash Commands
+
+Cascade should recognize these slash commands as role invocations:
+
+### Team Roles
+- `/pm` - Project Manager (@PM)
+- `/orchestrator` - Workflow Automation (@ORCHESTRATOR)
+- `/po` - Product Owner (@PO)
+- `/sa` - System Analyst (@SA)
+- `/uiux` - UI/UX Designer (@UIUX)
+- `/qa` - Quality Assurance (@QA)
+- `/seca` - Security Analyst (@SECA)
+- `/dev` - Developer (@DEV)
+- `/devops` - DevOps Engineer (@DEVOPS)
+- `/tester` - Tester (@TESTER)
+- `/reporter` - Reporter (@REPORTER)
+- `/stakeholder` - Stakeholder (@STAKEHOLDER)
+
+### Automation
+- `/auto` - Full automation mode
+- `/semi-auto` - Semi-automation mode
+
+### Knowledge Base
+- `/kb-search` - Search knowledge base
+- `/kb-add` - Add knowledge entry
+
+## Command Behavior
+
+When a slash command is used:
+
+1. Load role definition from `.agent/workflows/[role].md`
+2. Execute according to role responsibilities
+3. Create artifacts in `docs/sprints/sprint-[N]/`
+4. Follow global rules from `.agent/rules/global.md`
+5. Use templates from `.agent/templates/`
+
+## Multi-Agent Flow
+
+Cascade's multi-agent capability maps perfectly to TeamLifecycle:
+
+```
+User → /pm → Planning Agent
+     → /auto → Orchestrator Agent
+            → Design Agents (SA, UIUX, PO in parallel)
+            → Review Agents (QA, SecA in parallel)
+            → Development Agents (DEV, DevOps in parallel)
+            → Testing Agent (TESTER)
+            → Reporting Agent (REPORTER)
+            → Approval Agent (STAKEHOLDER)
+```
+
+## Cascade-Specific Features
+
+### Parallel Execution
+Use Cascade's multi-agent feature for parallel roles:
+```
+/orchestrator Enable full-auto mode
+→ Cascade spawns: SA Agent + UIUX Agent + PO Agent (parallel)
+→ Then spawns: QA Agent + SecA Agent (parallel)
+```
+
+### Context Sharing
+All agents share context through:
+- Artifacts in `docs/sprints/sprint-[N]/`
+- Knowledge base in `.agent/knowledge-base/`
+- Global rules in `.agent/rules/global.md`
+
+### Agent Handoff
+Each agent tags the next agent using @tags:
+```
+SA Agent completes → Tags @QA @SECA
+→ Cascade spawns QA Agent + SecA Agent
+```
+
+## Examples
+
+```
+/pm Build a SaaS platform for project management
+/auto Create an e-commerce mobile app
+/dev Implement Stripe payment integration
+/kb-search database connection pooling
+```
+
+## Configuration
+
+Add to Cascade settings or `.windsurfrules`:
+
+```json
+{
+  "customCommands": {
+    "pm": {
+      "description": "Project Manager",
+      "action": "loadRole",
+      "rolePath": ".agent/workflows/pm.md"
+    },
+    "orchestrator": {
+      "description": "Workflow Automation",
+      "action": "loadRole",
+      "rolePath": ".agent/workflows/orchestrator.md"
+    },
+    "auto": {
+      "description": "Full Auto Mode",
+      "action": "executeWorkflow",
+      "mode": "full-auto"
+    }
+  }
+}
+```
+```
+
+## Installation
+
+1. Create `.windsurfrules` in project root
+2. Copy configuration above
+3. Restart Windsurf
+4. Use `/` commands in Cascade chat

package/.agent/knowledge-base/README.md

@@ -0,0 +1,202 @@
+# Knowledge Base - Project Memory
+
+## Purpose
+This knowledge base stores lessons learned, bug patterns, difficult features, and solutions that required multiple attempts. Use this as a reference when encountering similar issues in the future.
+
+---
+
+## 📁 Structure
+
+```
+knowledge-base/
+├── README.md                    # This file
+├── index.md                     # Searchable index of all entries
+├── bugs/                        # Bug patterns and fixes
+│   ├── critical/
+│   ├── high/
+│   ├── medium/
+│   └── low/
+├── features/                    # Complex feature implementations
+│   ├── authentication/
+│   ├── performance/
+│   ├── integration/
+│   └── ui-ux/
+├── architecture/                # Architecture decisions and patterns
+├── security/                    # Security issues and solutions
+├── performance/                 # Performance optimizations
+└── platform-specific/           # Platform-specific issues
+    ├── web/
+    ├── mobile/
+    ├── desktop/
+    ├── cli/
+    └── embedded/
+```
+
+---
+
+## 🔍 How to Use
+
+### When to Create an Entry
+Create a knowledge entry when:
+- ✅ Bug required multiple attempts to fix (3+ attempts)
+- ✅ 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
+- ✅ Performance issue required deep investigation
+- ✅ Security vulnerability was discovered and fixed
+
+### When to Search
+Search the knowledge base when:
+- 🔍 Encountering a new bug or error
+- 🔍 Starting a complex feature implementation
+- 🔍 Facing performance issues
+- 🔍 Dealing with platform-specific problems
+- 🔍 Making architecture decisions
+- 🔍 Reviewing security concerns
+
+### How to Search
+1. **By Category:** Browse folders by type (bugs, features, etc.)
+2. **By Severity:** Check critical/high priority entries first
+3. **By Keywords:** Search for error messages, technology names, component names
+4. **By Index:** Check `index.md` for quick reference
+
+---
+
+## 📝 Creating an Entry
+
+### Step 1: Use the Template
+Copy `.gemini/instructions/templates/Knowledge-Entry-Template.md`
+
+### Step 2: Fill in Details
+- Provide clear problem description
+- Include code snippets
+- Document root cause
+- Explain solution step-by-step
+- Add prevention measures
+
+### Step 3: Choose Location
+Place entry in appropriate folder:
+- **Bugs:** `knowledge-base/bugs/[severity]/KB-[date]-[id].md`
+- **Features:** `knowledge-base/features/[category]/KB-[date]-[id].md`
+- **Architecture:** `knowledge-base/architecture/KB-[date]-[id].md`
+- **Security:** `knowledge-base/security/KB-[date]-[id].md`
+- **Performance:** `knowledge-base/performance/KB-[date]-[id].md`
+- **Platform:** `knowledge-base/platform-specific/[platform]/KB-[date]-[id].md`
+
+### Step 4: Update Index
+Add entry to `index.md` with:
+- ID, Title, Category, Tags, Date
+
+---
+
+## 🏷️ Tagging System
+
+### Category Tags
+- `#bug-pattern` - Recurring bug patterns
+- `#feature-solution` - Complex feature implementations
+- `#performance` - Performance optimizations
+- `#security` - Security issues
+- `#architecture` - Architecture decisions
+- `#integration` - Third-party integrations
+- `#platform-specific` - Platform-specific issues
+
+### Technology Tags
+- `#react`, `#nodejs`, `#python`, `#flutter`, etc.
+- `#postgresql`, `#mongodb`, `#redis`, etc.
+- `#aws`, `#docker`, `#kubernetes`, etc.
+
+### Severity Tags
+- `#critical` - System breaking, data loss
+- `#high` - Major functionality affected
+- `#medium` - Moderate impact
+- `#low` - Minor issues
+
+---
+
+## 📊 Entry Naming Convention
+
+**Format:** `KB-[YYYY-MM-DD]-[###]-[short-title].md`
+
+**Examples:**
+- `KB-2025-12-29-001-react-hydration-error.md`
+- `KB-2025-12-29-002-oauth-token-refresh.md`
+- `KB-2025-12-29-003-mobile-memory-leak.md`
+
+---
+
+## 🔄 Maintenance
+
+### Regular Reviews
+- **Monthly:** Review and update entries
+- **Quarterly:** Archive outdated entries
+- **Yearly:** Consolidate similar entries
+
+### Quality Standards
+- ✅ Clear problem description
+- ✅ Reproducible steps
+- ✅ Working solution
+- ✅ Prevention measures
+- ✅ Proper tagging
+
+### Archiving
+Move outdated entries to `knowledge-base/archive/[year]/`
+
+---
+
+## 📈 Metrics to Track
+
+Track these metrics in `index.md`:
+- Total entries by category
+- Most referenced entries
+- Average resolution time
+- Recurrence rate
+
+---
+
+## 🎯 Best Practices
+
+### Writing Entries
+1. **Be Specific:** Include exact error messages, versions, configurations
+2. **Be Complete:** Document all attempts, not just the final solution
+3. **Be Searchable:** Use clear keywords and tags
+4. **Be Visual:** Include screenshots, diagrams, code snippets
+5. **Be Preventive:** Focus on how to avoid the issue
+
+### Using Entries
+1. **Search First:** Always check knowledge base before starting
+2. **Adapt Solutions:** Don't copy-paste blindly, understand the context
+3. **Update Entries:** Add notes if you find better solutions
+4. **Cross-Reference:** Link related entries together
+
+---
+
+## 🤝 Contributing
+
+### Who Can Add Entries
+- @DEV - Bug fixes, feature implementations
+- @DEVOPS - Infrastructure, deployment issues
+- @TESTER - Test patterns, edge cases
+- @SECA - Security vulnerabilities
+- @SA - Architecture decisions
+- @UIUX - UI/UX patterns
+
+### Review Process
+1. Create entry using template
+2. Tag @REPORTER for review
+3. @REPORTER verifies completeness
+4. Entry added to index
+5. Team notified
+
+---
+
+## 📞 Questions?
+
+If unsure about:
+- **What to document:** Ask @PM or @REPORTER
+- **Where to place entry:** Check this README or ask @REPORTER
+- **How to search:** Use index.md or ask @REPORTER
+
+---
+
+#knowledge-base #documentation #lessons-learned

package/.agent/knowledge-base/architecture/.gitkeep

@@ -0,0 +1 @@
+# This folder stores architecture decisions and patterns

package/.agent/knowledge-base/bugs/.gitkeep

@@ -0,0 +1 @@
+# This folder stores bug patterns and solutions

package/.agent/knowledge-base/features/.gitkeep

@@ -0,0 +1 @@
+# This folder stores complex feature implementations