agentic-sdlc 1.5.1 → 1.8.1

package/.agent/workflows/cycle.md

@@ -1,24 +1,27 @@
 ---
-description: [Process] Complete Task Lifecycle - Plan → Work → Review → Compound
+description: Process - Complete Task Lifecycle - Plan, Work, Review, Compound
 ---
 
 # /cycle - Complete Task Lifecycle
 
+Complete Task Lifecycle workflow for small to medium tasks. This workflow guides you through planning, implementation, testing, and knowledge capture.
+
 ## ⚠️ STRICT EXECUTION PROTOCOL (MANDATORY)
 1. **NO SKIPPING:** Every step is MANDATORY.
 2. **TEAM COMMUNICATION FIRST:** Announce start and check history.
 3. **GIT FLOW:** Feature branch, atomic commits, PR.
 4. **SELF-LEARNING:** After completion, update Neo4j.
+5. **QUALITY CHECKS:** Run Observer and Judge before PR.
 
 ### 0.0 **Team Communication (MANDATORY):**
-   - **Check History:** `python tools/communication/cli.py history --channel general --limit 10`
-   - **Announce Start:** `python tools/communication/cli.py send --channel general --thread "SDLC-Flow" --role AGENT --content "Starting /cycle for [Task]."`
+   - **Check History:** `agentic-sdlc run tools/infrastructure/communication/cli.py history --channel general --limit 10`
+   - **Announce Start:** `agentic-sdlc run tools/infrastructure/communication/cli.py send --channel general --thread "SDLC-Flow" --role AGENT --content "Starting /cycle for [Task]."`
 
 ## Workflow Steps
 
 ### 1. Research Phase (MANDATORY)
 ```bash
-python tools/research/research_agent.py --feature "[task]" --type feature
+agentic-sdlc research --feature "[task]" --type feature
 ```
 - [ ] Search KB for similar implementations.
 - [ ] Check GitHub issues for context.
@@ -26,6 +29,10 @@ python tools/research/research_agent.py --feature "[task]" --type feature
 ### 2. Planning
 - Define acceptance criteria.
 - Add task to `Development-Log.md`.
+- **Observer Check:**
+  ```bash
+  python tools/core/brain/brain_cli.py observe --action "planning" --context '{"task": "[task]"}'
+  ```
 
 ### 3. Feature Branch
 ```bash
@@ -37,25 +44,39 @@ git push -u origin feat/TASK-ID-name
 - Code according to plan.
 - Atomic commits: `git commit -m "[TASK-ID] feat: description"`
 
-### 5. Verification
+### 5. Verification & Quality Assurance (MANDATORY)
 - Run local tests.
-- Create PR, tag @TESTER.
+- **Judge Score (Target > 8/10):**
+  ```bash
+  python tools/core/brain/brain_cli.py score "path/to/main_file.py"
+  ```
+- **Compliance Check:**
+  ```bash
+  python tools/core/brain/brain_cli.py observe
+  ```
 
 ### 6. Merge
+- Create PR, tag @TESTER.
 - Wait for `#testing-passed`.
 - Merge via @DEVOPS or @SA.
 
 ### 7. Self-Learning (MANDATORY)
 ```bash
-python tools/neo4j/sync_skills_to_neo4j.py
-python tools/neo4j/learning_engine.py --record-success "TASK-ID" --task-type "feature"
+agentic-sdlc kb compound sync
+python tools/core/brain/brain_cli.py learn "Completed [task] using [approach]"
 ```
 - Update `CHANGELOG.md`.
 
-#cycle #workflow #git-flow #self-learning---
-## ⚠️ ENFORCEMENT REMINDER
-Before executing this workflow, agent MUST:
-1. Have completed /preflight checks
-2. Searched knowledge base for similar tasks
-3. Checked current brain state
-Failure to complete pre-flight = workflow violation.
+#cycle #workflow #git-flow #self-learning
+
+## ⏭️ Next Steps
+- **If Compound Complete:** Workflow finished, ready for next task
+- **If Issues Found:** Repeat `/cycle` or escalate to `/explore`
+- **If Blocked:** Notify user via `notify_user`
+
+---
+## ⚠️ ENFORCEMENT REMINDER
+Before executing this workflow, agent MUST:
+1. Search knowledge base for similar tasks
+2. Check current brain state
+3. Run /onboarding if new to project

package/.agent/workflows/debug.md

@@ -0,0 +1,123 @@
+---
+description: Process - Systematic Debugging Workflow
+---
+
+# /debug - Debugging Workflow
+
+## ⚠️ PURPOSE
+Systematic approach to debugging issues in development. Different from `/emergency` which is for production incidents.
+
+// turbo-all
+
+## When to Use
+
+- Local development bugs
+- Test failures
+- Unexpected behavior
+- Performance issues (dev environment)
+
+## Quick Commands
+
+```bash
+# Search KB for similar bugs
+agentic-sdlc kb search "error type" --category bugs
+
+# Check learning engine for similar errors
+agentic-sdlc learn --similar-errors "ErrorType"
+```
+
+## Workflow Steps
+
+### 1. Reproduce the Issue
+- [ ] Identify exact steps to reproduce
+- [ ] Note environment (OS, versions, config)
+- [ ] Capture error message/stack trace
+
+```bash
+# Run failing test in isolation
+bun test --watch [test-file]
+```
+
+### 2. Search Knowledge Base
+```bash
+# Check if similar bug was fixed before
+agentic-sdlc kb search "[error message]"
+
+# Check neo4j for patterns
+agentic-sdlc learn --similar-errors "[ErrorType]"
+```
+
+### 3. Isolate the Problem
+- [ ] Binary search: Comment out code to find the culprit
+- [ ] Check recent changes: `git log --oneline -10`
+- [ ] Review git blame: `git blame [file]`
+
+### 4. Identify Root Cause
+- [ ] Add logging/breakpoints
+- [ ] Check input data
+- [ ] Verify assumptions
+- [ ] Review dependencies
+
+```bash
+# Debug with verbose output
+DEBUG=* bun run [script]
+```
+
+### 5. Implement Fix
+- [ ] Write failing test first (TDD)
+- [ ] Implement minimal fix
+- [ ] Verify fix works
+
+```bash
+git commit -m "fix: [description of fix]"
+```
+
+### 6. Verify No Regression
+```bash
+# Run full test suite
+bun test
+
+# Run type check
+bun run typecheck
+```
+
+### 7. Document & Learn (MANDATORY)
+
+```bash
+# Record error pattern for future reference
+agentic-sdlc learn --record-error "ErrorType" "[description]" \
+  --resolution "[how it was fixed]" \
+  --approach "[debugging approach used]"
+
+# Sync KB
+agentic-sdlc kb compound sync
+```
+
+## Common Debug Strategies
+
+| Strategy | When to Use | Command |
+|----------|-------------|---------|
+| **Binary Search** | Large codebase, unknown location | Comment out half |
+| **Git Bisect** | Regression, worked before | `git bisect start` |
+| **Logging** | Runtime issues | Add console.log/print |
+| **Breakpoints** | Complex state | Use debugger |
+| **Rubber Duck** | Stuck, need fresh perspective | Explain to "duck" |
+
+## Integration
+
+- **@DEV** - Primary debugger
+- **@TESTER** - Verify fix with tests
+- **/emergency** - Escalate if production issue
+- **/compound** - Document solution (embedded)
+
+#debug #troubleshooting #bugs #development
+
+## ⏭️ Next Steps
+- **If Fixed:** Trigger `/cycle` to resume normal work
+- **If Root Cause Unknown:** Trigger `/explore` for deeper analysis
+- **If Hotfix Needed:** Trigger `/emergency` or `/release`
+
+---
+
+## ENFORCEMENT REMINDER
+Always record error patterns after fixing bugs.

package/.agent/workflows/deep-search.md

@@ -0,0 +1,82 @@
+---
+description: Intelligence - Deep Search MCP for Technical Research
+---
+
+# /deep-search - Technical Research Workflow
+
+Deep web search using DuckDuckGo, GitHub, and StackOverflow APIs.
+**No third-party AI services** - fully manual implementation.
+
+// turbo-all
+
+## Quick Commands
+
+```bash
+# Aggregated search (all sources)
+python mcp/connectors/deep_search.py --search "query"
+
+# DuckDuckGo only
+python mcp/connectors/deep_search.py --ddg "query"
+
+# GitHub repos/code
+python mcp/connectors/deep_search.py --github "query"
+
+# StackOverflow Q&A
+python mcp/connectors/deep_search.py --stackoverflow "query"
+
+# Check status
+python mcp/connectors/deep_search.py --status
+```
+
+## Available Tools
+
+| Tool | Description | API Key |
+|------|-------------|---------|
+| `deep_search` | Aggregated multi-source search | None |
+| `ddg_search` | DuckDuckGo web search | None |
+| `github_search` | GitHub repos/code/issues | Optional |
+| `stackoverflow_search` | Stack Overflow Q&A | None |
+| `fetch_content` | Extract content from URL | None |
+
+## Python Usage
+
+```python
+from mcp.connectors.deep_search import DeepSearchConnector
+import json
+
+connector = DeepSearchConnector()
+
+# Aggregated search
+result = connector.call_tool("deep_search", {"query": "Python async await"})
+print(json.dumps(result, indent=2))
+
+# GitHub with filters
+result = connector.call_tool("github_search", {
+    "query": "MCP connector",
+    "search_type": "repositories",
+    "language": "python",
+    "sort": "stars"
+})
+
+# StackOverflow with tags
+result = connector.call_tool("stackoverflow_search", {
+    "query": "async programming",
+    "tags": ["python", "asyncio"],
+    "sort": "votes"
+})
+```
+
+## Integration
+
+- **@RESEARCH** - Primary user for investigations
+- **@SA** - Architecture decision research
+- **@DEV** - Solution lookup
+- **/explore** - Deep investigation workflow
+- **/planning** - Requirements research
+
+#deep-search #research #mcp #technical
+
+## ⏭️ Next Steps
+- **If Found Solution:** Apply to implementation
+- **If Need More Info:** Use `fetch_content` to extract URL details
+- **If GitHub Rate Limited:** Set `GITHUB_TOKEN` env var

package/.agent/workflows/docs.md

@@ -0,0 +1,144 @@
+---
+description: Support - Documentation Creation Workflow
+---
+
+# /docs - Documentation Workflow
+
+## ⚠️ PURPOSE
+Systematic approach to creating and maintaining project documentation.
+
+// turbo-all
+
+## When to Use
+
+- Creating new documentation
+- Updating existing docs
+- Writing KB entries
+- API documentation
+- User guides
+
+## Types of Documentation
+
+| Type | Template | Location |
+|------|----------|----------|
+| API Docs | Inline/OpenAPI | `docs/api/` |
+| User Guide | `User-Guide-Template.md` | `docs/guides/` |
+| Architecture | `Architecture-Spec-Template.md` | `docs/architecture/` |
+| Sprint Report | `Sprint-Review-Template.md` | `docs/sprints/sprint-[N]/` |
+
+## Workflow Steps
+
+### 1. Identify Doc Type
+- What are you documenting?
+- Who is the audience?
+- What template should you use?
+
+### 2. Check Existing Docs
+```bash
+# Search for related docs
+find docs -name "*.md" | xargs grep -l "[topic]"
+
+# Check KB for similar entries
+agentic-sdlc kb search "[topic]"
+```
+
+### 3. Choose Template
+```bash
+# List available templates
+ls .agent/templates/
+
+# Copy template
+cp .agent/templates/[Template].md docs/[appropriate-folder]/[new-doc].md
+```
+
+### 4. Write Content
+
+**Structure Guidelines:**
+- Start with clear heading
+- Add overview/purpose section
+- Use code blocks for commands
+- Include examples
+- Add cross-references
+
+**Style Guidelines:**
+- Use active voice
+- Keep sentences short
+- Use bullet points/tables
+- Include visuals when helpful
+
+### 5. Add Metadata (for KB entries)
+```yaml
+---
+category: feature|bug|architecture|security|performance
+tags: [relevant, tags]
+date: YYYY-MM-DD
+author: @ROLE
+---
+```
+
+### 6. Review & Validate
+- [ ] Spelling/grammar check
+- [ ] Links work
+- [ ] Code examples are correct
+- [ ] Follows project conventions
+
+```bash
+# Check for broken links
+find docs -name "*.md" -exec grep -l "\[.*\](.*)" {} \;
+```
+
+### 7. Update Indexes
+```bash
+# Update KB index
+agentic-sdlc kb update-index
+
+# Sync to Neo4j
+agentic-sdlc kb compound sync
+```
+
+## Documentation Standards
+
+### Naming Convention
+```
+[Type]-[Topic]-[Sprint]-v[Version].md
+Example: Architecture-Auth-Sprint-6-v1.md
+```
+
+### Required Sections
+
+**For KB Entries:**
+- Problem/Challenge
+- Solution
+- Implementation
+- Learnings
+
+**For User Guides:**
+- Overview
+- Prerequisites
+- Steps
+- Troubleshooting
+
+**For API Docs:**
+- Endpoint
+- Parameters
+- Response
+- Examples
+
+## Integration
+
+- **@PM** - Project documentation
+- **@SA** - Architecture docs
+- **@DEV** - Code documentation
+- **@REPORTER** - Reports and summaries
+- **/release** - Changelog updates
+
+#docs #documentation #writing 
+
+## ⏭️ Next Steps
+- **If Docs Created:** Trigger `/review` for feedback
+- **If Index Updated:** Trigger `/housekeeping` to verify health
+
+---
+
+## ENFORCEMENT REMINDER
+Update KB index after adding new entries.

package/.agent/workflows/emergency.md

@@ -1,5 +1,5 @@
 ---
-description: [Process] Emergency/Hotfix Response Workflow
+description: Process - Emergency/Hotfix Response Workflow
 ---
 
 # /emergency - Critical Incident Response
@@ -12,7 +12,7 @@ description: [Process] Emergency/Hotfix Response Workflow
 
 ### 0.0 **Declare Incident:**
 ```bash
-python tools/workflows/emergency.py --severity P0 --issue "[issue description]"
+python tools/infrastructure/workflows/emergency.py --severity P0 --issue "[issue description]"
 ```
 
 ## Severity Levels
@@ -34,7 +34,7 @@ python tools/workflows/emergency.py --severity P0 --issue "[issue description]"
 ### 2. Rapid Assessment (5 min max)
 ```bash
 # Search KB for similar incidents
-python tools/research/research_agent.py --task "[issue]" --type bug
+python tools/intelligence/research/research_agent.py --task "[issue]" --type bug
 ```
 **Quick Checks:**
 - [ ] Check monitoring/logs
@@ -77,11 +77,11 @@ git commit -m "hotfix: description (#INCIDENT-ID)"
 ### 7. Compound Learning (MANDATORY)
 ```bash
 # Create KB entry automatically
-python tools/workflows/emergency.py --severity P0 --issue "[issue]"
+python tools/infrastructure/workflows/emergency.py --severity P0 --issue "[issue]"
 
 # Or manually update Neo4j
-python tools/neo4j/sync_skills_to_neo4j.py
-python tools/neo4j/learning_engine.py --record-error "ErrorType" "description" --resolution "fix"
+python tools/intelligence/knowledge_graph/sync_skills_to_neo4j.py
+python tools/intelligence/knowledge_graph/learning_engine.py --record-error "ErrorType" "description" --resolution "fix"
 ```
 
 ### 8. Post-Incident
@@ -94,21 +94,23 @@ python tools/neo4j/learning_engine.py --record-error "ErrorType" "description" -
 
 ```bash
 # Interactive workflow
-python tools/workflows/emergency.py -s P0 -i "Payment gateway 500 errors"
+python tools/infrastructure/workflows/emergency.py -s P0 -i "Payment gateway 500 errors"
 
 # Non-interactive (for automation)
-python tools/workflows/emergency.py -s P1 -i "API timeout" --non-interactive
+python tools/infrastructure/workflows/emergency.py -s P1 -i "API timeout" --non-interactive
 ```
 
 ## Output Artifacts
 - `docs/sprints/sprint-[N]/logs/Incident-Report-[ID].json`
-- KB entry in `.agent/knowledge-base/bugs/`
 
 #emergency #hotfix #incident #production #p0
-
-
----
-
-## ENFORCEMENT REMINDER
-Before executing, complete /preflight checks.
 
+## ⏭️ Next Steps
+- **If Fixed:** Trigger `/compound` to document incident
+- **If Failed:** Escalate to User immediately
+- **If Recurring:** Trigger `/explore` for root cause analysis
+
+---
+
+## ENFORCEMENT REMINDER
+Act immediately for P0/P1 incidents.

package/.agent/workflows/explore.md

@@ -1,5 +1,5 @@
 ---
-description: [Process] Deep Investigation Workflow
+description: Process - Deep Investigation Workflow
 ---
 
 # /explore - Multi-Order Analysis
@@ -23,8 +23,11 @@ description: [Process] Deep Investigation Workflow
 **Question:** What does the user want?
 
 ```bash
-# Basic research
-python tools/research/research_agent.py --task "[feature]" --type general
+# Basic research with research agent
+python tools/intelligence/research/research_agent.py --task "[feature]" --type general
+
+# Deep Search MCP (aggregated: DuckDuckGo + GitHub + StackOverflow)
+python mcp/connectors/deep_search.py --search "[feature]"
 ```
 
 - [ ] Understand explicit requirements
@@ -138,10 +141,13 @@ Fourth-Order: Token revocation, multi-device sessions, privacy compliance
 ```
 
 #explore #analysis #research #architecture #risk-assessment
-
-
----
-
-## ENFORCEMENT REMINDER
-Before executing, complete /preflight checks.
 
+## ⏭️ Next Steps
+- **If Recommendation Approved:** Trigger `/cycle` or `/sprint` to implement
+- **If Rejected:** Refine analysis or explore alternatives
+- **If Unclear:** Request stakeholder feedback
+
+---
+
+## ENFORCEMENT REMINDER
+Search KB for related entries before deep investigation.

package/.agent/workflows/housekeeping.md

@@ -1,5 +1,5 @@
 ---
-description: [Support] Housekeeping - Cleanup and Maintenance
+description: Support - Housekeeping - Cleanup and Maintenance
 ---
 
 # /housekeeping - System Maintenance Workflow
@@ -12,7 +12,7 @@ description: [Support] Housekeeping - Cleanup and Maintenance
 ## Quick Command
 
 ```bash
-python tools/workflows/housekeeping.py
+python tools/infrastructure/workflows/housekeeping.py
 ```
 
 ## Workflow Steps
@@ -29,10 +29,9 @@ python tools/workflows/housekeeping.py
 
 ### Step 3: Update Indexes
 ```bash
-# Updates KB index
-python bin/kb_cli.py update-index
+# Updates indexes (KB, Documents, vectors)
+python tools/intelligence/knowledge_graph/brain_parallel.py --sync
 ```
-- Regenerates `.agent/knowledge-base/INDEX.md`
 - Ensures all entries are indexed
 - Updates statistics
 
@@ -43,6 +42,18 @@ Reports:
 - Current sprint status
 - System health status
 
+### Step 5: Brain Self-Analysis (NEW)
+```bash
+# Analyze patterns from A/B tests, Judge scores, Learner data
+python tools/intelligence/self_learning/self_improver.py --analyze
+
+# Create improvement plan based on patterns
+python tools/intelligence/self_learning/self_improver.py --plan
+
+# Sync all brain data
+python tools/intelligence/knowledge_graph/brain_parallel.py --full
+```
+
 ## Expected Output
 
 ```
@@ -96,10 +107,12 @@ Step 4: Verify System Health
 - **/sprint close** - Triggers housekeeping automatically
 
 #housekeeping #maintenance #cleanup #health-check
-
-
----
-
-## ENFORCEMENT REMINDER
-Before executing, complete /preflight checks.
 
+## ⏭️ Next Steps
+- **If Issues Found:** Trigger `/cycle` to fix
+- **If Clean:** End session or Trigger `/metrics` for analysis
+
+---
+
+## ENFORCEMENT REMINDER
+Run at least once per sprint.

package/.agent/workflows/metrics.md

@@ -1,5 +1,5 @@
 ---
-description: [Utility] Metrics - Project Statistics
+description: Utility - Metrics - Project Statistics
 ---
 
 # /metrics - Metrics Dashboard Generator
@@ -11,16 +11,16 @@ Analyzes KB entries, workflow usage, and project health to generate a metrics da
 
 ```bash
 # Generate dashboard
-python tools/kb/metrics-dashboard.py
+python tools/infrastructure/workflows/metrics.py
 
 # Weekly report focus
-python tools/kb/metrics-dashboard.py --weekly
+python tools/infrastructure/workflows/metrics.py --weekly
 
 # Sprint-specific metrics
-python tools/kb/metrics-dashboard.py --sprint 6
+python tools/infrastructure/workflows/metrics.py --sprint sprint-2
 
 # Custom output path
-python tools/kb/metrics-dashboard.py --output ./my-report.md
+python tools/infrastructure/workflows/metrics.py --output ./my-report.md
 ```
 
 ## What It Measures
@@ -169,11 +169,13 @@ Auto-generates recommendations based on:
 - **/housekeeping** - References health status
 - **/sprint close** - Include metrics in retrospective
 
-#metrics #dashboard #analytics #health #knowledge-base
-
-
----
-
-## ENFORCEMENT REMINDER
-Before executing, complete /preflight checks.
+#metrics #dashboard #analytics #health 
 
+## ⏭️ Next Steps
+- **If Trends Negative:** Trigger `/sprint` retrospective
+- **If Goals Met:** Celebrate and plan next sprint
+
+---
+
+## ENFORCEMENT REMINDER
+Run periodically to track project health.