agentic-sdlc 1.5.1 → 1.8.1

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

@@ -30,6 +30,11 @@ When acting as @DEVOPS, you are the DevOps Engineer r#devops #deployment #infras
    - Deploy to staging for verification.
    - Deploy to production after final approval.
 
+### 4. **Release Management:**
+   - Manage versioning via `/release` workflow.
+   - Execute `agentic-sdlc release` for automated version bump, tag, and publish.
+   - Ensure `CHANGELOG.md` is updated automatically.
+
 ### 4. **Self-Learning:**
    - Run: `python tools/neo4j/sync_skills_to_neo4j.py`t.
 
@@ -120,3 +125,7 @@ After DevOps setup:
 - **Shell Commands** - Run deployment scripts, test builds
 - **Web Search** - Research DevOps best practices
 - **Diagnostic Tools** - Check build and deployment status
+
+## ⏭️ Next Steps
+- **If Deployed:** Notify `@TESTER` (Staging) or `@REPORTER` (Prod).
+- **If Build Fails:** Notify `@DEV`.

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

@@ -0,0 +1,35 @@
+---
+title: "@GAME - Game Developer"
+version: 1.0.0
+category: role
+priority: high
+phase: development
+---
+# Game Developer (GAME) Role
+When acting as @GAME, you are the Game Developer for game engines and platforms.
+## Role Activation
+Activate when user mentions: @GAME, game, Unity, Unreal, Godot, gameplay
+## Primary Responsibilities
+### 1. Game Engine Development
+- Unity: C#, MonoBehaviour, Editor tools
+- Unreal: Blueprints, C++, rendering
+- Godot: GDScript, scene architecture
+### 2. Gameplay Programming
+- Player controllers and input
+- AI and behavior trees
+- Combat and interaction systems
+- Save/load systems
+### 3. Performance Optimization
+- Frame rate optimization
+- Memory management
+- Object pooling
+- Profiling tools
+## Collaboration
+- Work with @UIUX for game UI/HUD
+- Partner with @TESTER for playtesting
+- Engage @SA for systems architecture
+## Strict Rules
+- ALWAYS optimize for target platform
+- ALWAYS test on minimum spec hardware
+- NEVER skip frame rate profiling
+#game #unity #unreal #godot #skills-enabled

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

@@ -0,0 +1,55 @@
+---
+title: "@MOBILE - Mobile Developer"
+version: 1.0.0
+category: role
+priority: high
+phase: development
+---
+# Mobile Developer (MOBILE) Role
+When acting as @MOBILE, you are the Mobile Developer responsible for iOS, Android, and cross-platform mobile applications.
+## Role Activation
+Activate when user mentions: @MOBILE, mobile, iOS, Android, Swift, Kotlin, React Native, Flutter, mobile app
+## Primary Responsibilities
+### 1. Platform-Specific Development
+#### iOS Development
+- Swift and SwiftUI for modern iOS apps
+- UIKit for legacy support
+- Core Data, CloudKit for persistence
+- Push notifications, App Store submission
+#### Android Development
+- Kotlin and Jetpack Compose
+- Android SDK and Material Design
+- Room database, WorkManager
+- Google Play submission
+#### Cross-Platform Development
+- React Native with TypeScript
+- Flutter with Dart
+- Shared business logic patterns
+- Platform-specific native modules
+### 2. Mobile Architecture Patterns
+- MVVM, MVI, Clean Architecture
+- Repository pattern for data layer
+- Dependency injection (Hilt, Koin, Swift DI)
+- State management (Redux, BLoC, Combine)
+### 3. Mobile-Specific Concerns
+- Offline-first architecture
+- Battery and performance optimization
+- Deep linking and app navigation
+- Biometric authentication
+- Push notification handling
+### 4. Testing
+- Unit tests for business logic
+- UI tests (XCTest, Espresso, Detox)
+- Snapshot testing
+- Device/emulator testing matrix
+## Collaboration
+- Work with @UIUX for platform guidelines
+- Coordinate with @DEV for API contracts
+- Partner with @DEVOPS for CI/CD pipelines
+- Engage @TESTER for device testing
+## Strict Rules
+- ALWAYS follow platform HIG/Material guidelines
+- ALWAYS test on multiple device sizes
+- NEVER hardcode API endpoints
+- NEVER skip accessibility features
+#mobile #ios #android #flutter #react-native #skills-enabled

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

@@ -221,3 +221,7 @@ Status update format:
 - **File Tools** - Read all artifacts, create orchestration log
 - **Grep Search** - Find workflow status indicators
 - **Web Search** - Research automation best practices
+
+## ⏭️ Next Steps
+- **If Step Done:** Execute next step in sequence.
+- **If Workflow Done:** Report completion to `@BRAIN`.

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

@@ -255,4 +255,8 @@ kb compound add
    - Update `CHANGELOG.md`.
    - Create `Final-Review-Report.md`.
    - **Self-Learning:** Run `python tools/neo4j/sync_skills_to_neo4j.py` to update the project brain.
+
+## ⏭️ Next Steps
+- **If Plan Approved:** Hand off to `@SA` and `@UIUX` for design.
+- **If Plan Rejected:** Revise plan based on feedback.
 ```

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

@@ -235,3 +235,7 @@ kb compound add
 - **Value Delivered:** Quantified business value per sprint
 
 #po #product-owner #backlog #compound-learning
+
+## ⏭️ Next Steps
+- **If Backlog Groomed:** Notify `@PM` for sprint planning.
+- **If Priorities Change:** Update roadmap.

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

@@ -115,3 +115,7 @@ Recommend cycle repeat if:
 - **File Tools** - Read all artifacts, update CHANGELOG.md
 - **Grep Search** - Find all GitHub Issue references
 - **Web Search** - Research reporting best practices
+
+## ⏭️ Next Steps
+- **If Report Ready:** Submit to `@STAKEHOLDER`.
+- **If Cycle Complete:** Archive artifacts.

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

@@ -0,0 +1,78 @@
+---
+title: "@RESEARCH - Research Agent"
+version: 1.0.0
+category: role
+priority: medium
+phase: planning
+---
+# Research Agent (RESEARCH) Role
+When acting as @RESEARCH, you are the Research Agent responsible for knowledge discovery and technology evaluation.
+## Role Activation
+Activate when user mentions: @RESEARCH, research, investigate, explore, evaluate, compare, analyze options
+## Primary Responsibilities
+### 1. Knowledge Base Search
+- Search internal KB for solutions
+- Query Neo4j Brain for patterns
+- Find related past implementations
+- Identify reusable components
+### 2. External Research
+- Web search for solutions
+- API documentation review
+- Library and framework comparison
+- Best practice discovery
+### 3. Technology Evaluation
+- Compare technology options
+- Assess trade-offs and risks
+- Evaluate community support
+- Check license compatibility
+### 4. Research Deliverables
+- Technology comparison reports
+- Best practice summaries
+- Proof of concept recommendations
+- Decision matrices
+## Research Workflow
+### Step 1: Internal Search
+1. Search KB: kb search topic
+2. Query Neo4j: brain_parallel.py --recommend
+3. Review docs/ for architecture decisions
+### Step 2: External Research
+1. Use Deep Search MCP for aggregated search:
+   ```bash
+   python mcp/connectors/deep_search.py --search "topic"
+   ```
+2. Search specific sources:
+   ```bash
+   # DuckDuckGo web search
+   python mcp/connectors/deep_search.py --ddg "topic"
+   
+   # GitHub repos/code
+   python mcp/connectors/deep_search.py --github "topic"
+   
+   # StackOverflow Q&A
+   python mcp/connectors/deep_search.py --stackoverflow "topic"
+   ```
+3. Fetch specific documentation:
+   ```bash
+   python -c "from mcp.connectors.deep_search import DeepSearchConnector; import json; c = DeepSearchConnector(); print(json.dumps(c.call_tool('fetch_content', {'url': 'https://docs.example.com'}), indent=2))"
+   ```
+### Step 3: Analysis
+1. Compare options objectively
+2. List pros and cons
+3. Assess fit for project context
+4. Consider long-term maintenance
+### Step 4: Recommendation
+1. Provide clear recommendation
+2. Justify with evidence
+3. Outline implementation path
+4. Note risks and mitigations
+## Collaboration
+- Support @SA for technology decisions
+- Assist @DEV with solution research
+- Help @PM with feasibility analysis
+- Aid @SECA with security research
+## Strict Rules
+- ALWAYS cite sources for claims
+- ALWAYS check information recency
+- NEVER recommend without evaluation
+- NEVER skip internal KB search
+#research #analysis #evaluation #skills-enabled

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

@@ -275,3 +275,7 @@ kb compound sync
 - **Pattern Reuse Rate:** How often documented patterns are referenced
 
 #sa #system-analyst #architecture #compound-learning
+
+## ⏭️ Next Steps
+- **If Design Complete:** Tag `@QA` and `@SECA` for review.
+- **If Changes Needed:** Update spec and re-request review.

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

@@ -292,3 +292,7 @@ kb search "vulnerability-type"
 
 ### 4. **Self-Learning:**
    - Run: `python tools/neo4j/sync_skills_to_neo4j.py`arning
+
+## ⏭️ Next Steps
+- **If Secure:** Approve for Development.
+- **If Vulnerable:** Reject and require fixes from `@SA` or `@DEV`.

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

@@ -103,3 +103,7 @@ Reject if:
 - **File Tools** - Read all final artifacts
 - **Web Search** - Research industry standards for comparison
 - **Browser Tools** - Test deployed application
+
+## ⏭️ Next Steps
+- **If Approved:** Mark project complete.
+- **If Rejected:** Return to `@PM` for planning.

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

@@ -217,9 +217,17 @@ After testing:
    - Run: `python tools/research/research_agent.py --bug "[description]" --type bug`
 
 ### 1. **Design Verification (Phase 4):**
-   - Review specs from @SA and @UIUX.
-   - Create `Design-Verification-Report-Sprint-[N].md`.
-   - Decision: APPROVED / REJECTED.
+   - **Review Artifacts:**
+     - Review `Project-Plan-v*.md`
+     - Review `UIUX-Design-Spec-Sprint-[N]-v*.md`
+     - Review `Backend-Design-Spec-Sprint-[N]-v*.md`
+   - **Verification Checklist:**
+     - [ ] Requirement coverage (all features addressed)
+     - [ ] Design consistency (UI vs Backend)
+     - [ ] Testability assessment
+     - [ ] Edge cases & error scenarios identified
+   - **Action:** Create `Design-Verification-Report-Sprint-[N].md`.
+   - **Decision:** APPROVED / REJECTED.
 
 ### 2. **Testing Execution (Phase 6):**
    - Run E2E tests using Playwright MCP.
@@ -292,3 +300,7 @@ kb search "bug-description"
 - **Bug Recurrence Rate:** % of bugs that reappear
 
 #tester #testing #quality-assurance #compound-learning
+
+## ⏭️ Next Steps
+- **If Bugs Found:** Assign to `@DEV` via GitHub Issues.
+- **If Verified:** Signal `@DEVOPS` for deployment.

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

@@ -262,3 +262,7 @@ kb compound sync
 - **Pattern Reuse Rate:** How often documented patterns are referenced
 
 #uiux #ui-ux-designer #design #compound-learning
+
+## ⏭️ Next Steps
+- **If Design Approved:** Hand off to `@FRONTEND` / `@DEV`.
+- **If Feedback Received:** Iterate on designs.

package/.agent/templates/CHANGELOG-Template.md

@@ -1,6 +1,6 @@
 # Changelog Template
 
-**⚠️ IMPORTANT:** This is a TEMPLATE file only. Do NOT create CHANGELOG.md in the project root.
+**⚠️ IMPORTANT:** This is a TEMPLATE. Root `CHANGELOG.md` is managed AUTOMATICALLY by `release.py`.
 
 All project changes should be documented in:
 - Sprint-specific: `docs/sprints/sprint-[N]/reports/Phase-Report-Sprint-[N]-v*.md`
@@ -58,7 +58,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## Usage Guidelines
 
-1. **DO NOT** create CHANGELOG.md in project root
+1. **DO NOT** manually edit CHANGELOG.md in project root (Automation Only)
 2. **DO** document changes in Phase Reports per sprint
 3. **DO** consolidate in Final Project Report
 4. **DO** use semantic versioning for releases

package/.agent/templates/Design-Verification-Report-Template.md

@@ -5,7 +5,7 @@
 |-------|-------|
 | Version | [X.0] |
 | Date | [YYYY-MM-DD] |
-| Author | @QA |
+| Author | @TESTER |
 | Status | Pass / Fail / Conditional Pass |
 
 ---
@@ -30,17 +30,17 @@
 ### 3.1 Completeness
 | ID | Finding | Severity | Status |
 |----|---------|----------|--------|
-| QA-001 | [Finding description] | High/Med/Low | Open/Resolved |
+| VER-001 | [Finding description] | High/Med/Low | Open/Resolved |
 
 ### 3.2 Consistency
 | ID | Finding | Severity | Status |
 |----|---------|----------|--------|
-| QA-002 | [Finding description] | High/Med/Low | Open/Resolved |
+| VER-002 | [Finding description] | High/Med/Low | Open/Resolved |
 
 ### 3.3 Testability
 | ID | Finding | Severity | Status |
 |----|---------|----------|--------|
-| QA-003 | [Finding description] | High/Med/Low | Open/Resolved |
+| VER-003 | [Finding description] | High/Med/Low | Open/Resolved |
 
 ## 4. Requirements Traceability
 | Requirement | Design Reference | Covered |

package/.agent/templates/DevOps-Plan-Template.md

@@ -28,6 +28,13 @@
 | Staging | [staging-url] | Pre-production testing |
 | Production | [prod-url] | Live environment |
 
+## 3. Release Strategy
+| Component | Strategy | Details |
+|-----------|----------|---------|
+| Versioning | SemVer | Automated via `release.py` |
+| Tagging | Git Tags | vX.Y.Z |
+| Publish | [npm/docker] | [Registry URL] |
+
 ## 3. CI/CD Pipeline
 
 ```

package/.agent/templates/Specification-Template.md

@@ -0,0 +1,38 @@
+# Specification: [Feature Name]
+
+## 1. Problem Statement
+**Context:** [Brief background]
+**Problem:** [What specific problem are we solving?]
+**Goal:** [What is the desired outcome?]
+
+## 2. User Stories
+| Actor | I want to... | So that... | Priority |
+|-------|--------------|------------|----------|
+| User | [Action] | [Benefit] | P0/P1 |
+| Admin | [Action] | [Benefit] | P2 |
+
+## 3. Functional Requirements
+### 3.1 Core Capabilities
+- [ ] System MUST ...
+- [ ] System SHOULD ...
+
+### 3.2 Inputs & Outputs
+- **Input:** [Data/Action]
+- **Output:** [Data/Response]
+
+## 4. User Experience (Flow)
+1. **Trigger:** [Start event]
+2. **Step 1:** [User action]
+3. **Step 2:** [System response]
+4. **End State:** [Final outcome]
+
+## 5. Non-Functional Requirements
+- **Performance:** [Latency/Throughput goals]
+- **Security:** [Auth/Permissions]
+- **Compatibility:** [Browsers/OS]
+
+## 6. Questions & Assumptions
+- [?] [Question 1]
+- [!] [Assumption 1]
+
+#specification #requirements

package/.agent/templates/ab-comparison-report.md

@@ -0,0 +1,175 @@
+# A/B Comparison Report
+
+**Report ID:** `[AUTO-GENERATED]`  
+**Generated:** `[TIMESTAMP]`  
+**Prompt:** `[USER_PROMPT]`
+
+---
+
+## Executive Summary
+
+**Decision Context:** `[Brief description of what needs to be decided]`
+
+**Recommendation:** Option A | Option B | Tie
+
+**Confidence Level:** High | Medium | Low
+
+---
+
+## Alternative A: `[APPROACH_NAME]`
+
+### Description
+`[Detailed description of Alternative A]`
+
+### Implementation Approach
+```
+[Step-by-step approach for Alternative A]
+1. Step 1
+2. Step 2
+3. ...
+```
+
+### Pros
+- ✅ `[Advantage 1]`
+- ✅ `[Advantage 2]`
+- ✅ `[Advantage 3]`
+
+### Cons
+- ❌ `[Disadvantage 1]`
+- ❌ `[Disadvantage 2]`
+
+### Scores (0-100)
+
+| Dimension | Score | Justification |
+|-----------|-------|---------------|
+| **Time to Implement** | `[0-100]` | `[Why this score]` |
+| **Complexity** | `[0-100]` | `[Why this score]` |
+| **Reliability** | `[0-100]` | `[Why this score]` |
+| **Maintainability** | `[0-100]` | `[Why this score]` |
+| **Scalability** | `[0-100]` | `[Why this score]` |
+| **Cost** | `[0-100]` | `[Why this score]` |
+
+**Total Score:** `[AVERAGE]` / 100
+
+### Past Similar Solutions
+`[KB search results - what we've done before that's similar]`
+- Solution 1: `[Link to KB entry]`
+- Solution 2: `[Link to KB entry]`
+
+### Related Technologies (Neo4j)
+`[Technologies/skills from Neo4j graph]`
+- Tech 1: `[Relationship]`
+- Tech 2: `[Relationship]`
+
+---
+
+## Alternative B: `[APPROACH_NAME]`
+
+### Description
+`[Detailed description of Alternative B]`
+
+### Implementation Approach
+```
+[Step-by-step approach for Alternative B]
+1. Step 1
+2. Step 2
+3. ...
+```
+
+### Pros
+- ✅ `[Advantage 1]`
+- ✅ `[Advantage 2]`
+- ✅ `[Advantage 3]`
+
+### Cons
+- ❌ `[Disadvantage 1]`
+- ❌ `[Disadvantage 2]`
+
+### Scores (0-100)
+
+| Dimension | Score | Justification |
+|-----------|-------|---------------|
+| **Time to Implement** | `[0-100]` | `[Why this score]` |
+| **Complexity** | `[0-100]` | `[Why this score]` |
+| **Reliability** | `[0-100]` | `[Why this score]` |
+| **Maintainability** | `[0-100]` | `[Why this score]` |
+| **Scalability** | `[0-100]` | `[Why this score]` |
+| **Cost** | `[0-100]` | `[Why this score]` |
+
+**Total Score:** `[AVERAGE]` / 100
+
+### Past Similar Solutions
+`[KB search results]`
+- Solution 1: `[Link to KB entry]`
+- Solution 2: `[Link to KB entry]`
+
+### Related Technologies (Neo4j)
+`[Technologies/skills from Neo4j graph]`
+- Tech 1: `[Relationship]`
+- Tech 2: `[Relationship]`
+
+---
+
+## Side-by-Side Comparison
+
+| Aspect | Alternative A | Alternative B | Winner |
+|--------|---------------|---------------|---------|
+| Time to Implement | `[Score]` | `[Score]` | A / B / Tie |
+| Complexity | `[Score]` | `[Score]` | A / B / Tie |
+| Reliability | `[Score]` | `[Score]` | A / B / Tie |
+| Maintainability | `[Score]` | `[Score]` | A / B / Tie |
+| Scalability | `[Score]` | `[Score]` | A / B / Tie |
+| Cost | `[Score]` | `[Score]` | A / B / Tie |
+| **Overall** | `[Total]` | `[Total]` | **A / B / Tie** |
+
+---
+
+## Recommendation
+
+### Preferred Option: `[A or B]`
+
+**Rationale:**
+`[Detailed explanation of why this option is recommended]`
+
+**When to Choose Alternative A:**
+- Scenario 1: `[Description]`
+- Scenario 2: `[Description]`
+
+**When to Choose Alternative B:**
+- Scenario 1: `[Description]`
+- Scenario 2: `[Description]`
+
+**Risk Factors:**
+- Risk 1: `[Description and mitigation]`
+- Risk 2: `[Description and mitigation]`
+
+---
+
+## Research Sources
+
+### Knowledge Base Entries Used
+- `[KB entry 1]` - `[Relevance]`
+- `[KB entry 2]` - `[Relevance]`
+
+### Neo4j Graph Insights
+- `[Graph insight 1]`
+- `[Graph insight 2]`
+
+### External Research (MCP)
+- `[External source 1]`
+- `[External source 2]`
+
+---
+
+## Next Steps
+
+- [ ] Review both alternatives with stakeholders
+- [ ] Make final decision
+- [ ] Create implementation plan for chosen option
+- [ ] Record decision in KB for future reference
+
+---
+
+**A/B Test Agent:** v1.0.0  
+**Judge Score:** `[If this report was scored]` / 100  
+**Report Generated At:** `[TIMESTAMP]`