agentic-sdlc 1.5.1 → 1.8.1

package/.agent/workflows/monitor.md

@@ -0,0 +1,98 @@
+---
+description: Intelligence - Monitor - System Health Check
+---
+
+# /monitor - System Health Monitoring
+
+## ⚠️ PURPOSE
+Check overall system health, identify missing documentation, detect obsolete code, and get improvement suggestions.
+
+// turbo-all
+
+## Quick Commands
+
+```bash
+# Full health check
+python tools/intelligence/monitor/health_monitor.py --check
+
+# Get improvement suggestions
+python tools/intelligence/monitor/health_monitor.py --suggest
+
+# Check via Brain CLI
+python tools/core/brain/brain_cli.py health
+```
+
+## When to Use
+
+- Start of each work session
+- Before major releases
+- During housekeeping
+- After major changes
+
+## Workflow Steps
+
+### 1. Run Health Check
+```bash
+python tools/intelligence/monitor/health_monitor.py --check
+```
+
+### 2. Review Health Status
+
+**Health Indicators:**
+| Status | Score | Description |
+|--------|-------|-------------|
+| 🟢 Healthy | 80-100 | System in good shape |
+| 🟡 Warning | 50-79 | Some issues to address |
+| 🔴 Critical | 0-49 | Immediate attention needed |
+
+### 3. Review Metrics
+
+The monitor checks:
+- **Documentation Coverage** - Are all features documented?
+- **Test Coverage Gaps** - Missing tests
+- **Obsolete Code** - Unused files, deprecated functions
+- **Compliance Trends** - Observer violation rate over time
+- **Performance Issues** - Slow functions, memory leaks
+
+### 4. Get Suggestions
+```bash
+python tools/intelligence/monitor/health_monitor.py --suggest
+```
+
+### 5. Address Issues
+Based on suggestions:
+- Add missing documentation
+- Create tests for uncovered code
+- Remove obsolete files
+- Fix compliance issues
+
+### 6. Verify Fix
+Re-run health check to confirm improvements.
+
+## Health Check Areas
+
+| Area | What's Checked |
+|------|----------------|
+| Documentation | `docs/` directory, walkthroughs, plans |
+| Brain State | `.agent/` directory integrity |
+| Tools | `tools/` directory structure |
+| KB Health | Entry count, category distribution |
+
+## Integration
+
+- **@BRAIN** - System oversight
+- **/housekeeping** - Maintenance routine
+- **/validate** - Tool reference validation
+- **/metrics** - Detailed statistics
+
+#monitor #health #system #metrics
+
+## ⏭️ Next Steps
+- **If Healthy:** Continue normal work
+- **If Warning:** Schedule `/housekeeping`
+- **If Critical:** Address issues immediately
+
+---
+
+## ENFORCEMENT REMINDER
+Run health check at the start of each session.

package/.agent/workflows/observe.md

@@ -0,0 +1,84 @@
+---
+description: Intelligence - Observer - Rule Compliance Check
+---
+
+# /observe - Rule Compliance Monitor
+
+## ⚠️ PURPOSE
+Trigger the Observer agent to check rule compliance for actions, code, or the entire system.
+
+// turbo-all
+
+## Quick Commands
+
+```bash
+# Check overall compliance status
+python tools/intelligence/observer/observer.py --report
+
+# Check a specific action
+python tools/intelligence/observer/observer.py --check-action "create file foo.py"
+
+# Start continuous observation
+python tools/intelligence/observer/observer.py --start
+```
+
+## When to Use
+
+- Before committing code
+- After making changes to workflows or rules
+- During code review
+- When debugging compliance issues
+
+## Workflow Steps
+
+### 1. Check Current Compliance
+```bash
+python tools/intelligence/observer/observer.py --report
+```
+Review the compliance score and any violations.
+
+### 2. Check Specific Action
+```bash
+python tools/intelligence/observer/observer.py --check-action "[action description]"
+```
+Validates a specific action against the rules.
+
+
+### 3. Review Violations
+If violations are found:
+- Review the violation report in `docs/reports/observer/`
+- Fix the issues
+- Re-run the check
+
+### 4. Self-Learning
+```bash
+# Record the violation pattern for future reference
+python tools/core/brain/brain_cli.py learn "Fixed compliance issue: [description]"
+```
+
+## Integration
+
+- **@BRAIN** - Uses Observer for monitoring
+- **/cycle** - Compliance check before PR
+- **/commit** - Pre-commit validation
+- **/housekeeping** - Part of maintenance
+
+## Observer Checks
+
+| Check | Description |
+|-------|-------------|
+| Code Quality | Naming conventions, style |
+| Template Compliance | Correct template usage |
+| Workflow Steps | Mandatory steps followed |
+| Documentation | Required docs present |
+
+#observe #compliance #monitoring #rules
+
+## ⏭️ Next Steps
+- **If Compliant:** Continue with current workflow
+- **If Violations Found:** Fix issues and re-run `/observe`
+
+---
+
+## ENFORCEMENT REMINDER
+Run Observer before major commits.

package/.agent/workflows/onboarding.md

@@ -0,0 +1,135 @@
+---
+description: Support - New Agent Onboarding Workflow
+---
+
+# /onboarding - Agent Onboarding
+
+## ⚠️ PURPOSE
+Quick ramp-up workflow for new AI agent sessions joining the project. Accelerates context building.
+
+// turbo-all
+
+## When to Use
+
+- Starting a new AI agent session
+- Switching context to this project
+- After long absence from project
+
+## Quick Commands
+
+```bash
+# Check project status
+agentic-sdlc brain status
+
+# View recent activity
+git log --oneline -20
+```
+
+## Workflow Steps
+
+### 1. Read Core Documents
+**MANDATORY reading in order:**
+
+1. **GEMINI.md** - Agent instructions and rules
+   ```bash
+   cat GEMINI.md
+   ```
+
+2. **README.md** - Project overview
+   ```bash
+   cat README.md
+   ```
+
+3. **CHANGELOG.md** - Recent changes
+   ```bash
+   head -100 CHANGELOG.md
+   ```
+
+### 2. Understand Project Structure
+```bash
+# View top-level structure
+ls -la
+
+# View .agent structure
+ls -la .agent/
+
+# View tools
+ls -la tools/
+```
+
+### 3. Check Current State
+```bash
+# Brain status
+agentic-sdlc brain status
+
+# Current sprint
+ls docs/sprints/
+
+# Active issues
+gh issue list --limit 10
+```
+
+### 4. Search Knowledge Base
+```bash
+# Get overview of KB
+agentic-sdlc kb list
+
+# Search for recent entries
+agentic-sdlc kb search "recent"
+```
+
+### 5. Review Active Work
+```bash
+# Check branches
+git branch -a
+
+# Check open PRs
+gh pr list
+
+# Check open issues
+gh issue list
+```
+
+### 6. Context Checklist
+By end of onboarding, you should know:
+
+- [ ] Project purpose and goals
+- [ ] Current sprint and priorities
+- [ ] Active issues/PRs
+- [ ] Key technologies used
+- [ ] Available tools and workflows
+- [ ] Team communication patterns
+
+## Quick Reference Card
+
+| What | Where |
+|------|-------|
+| Agent rules | `GEMINI.md` |
+| Project overview | `README.md` |
+| Workflows | `.agent/workflows/` |
+| Roles | `.agent/skills/` |
+| Templates | `.agent/templates/` |
+| Tools | `tools/` |
+| Sprint docs | `docs/sprints/sprint-[N]/` |
+
+## Shortcuts for Common Tasks
+
+| Task | Command/Workflow |
+|------|------------------|
+| New feature | `/orchestrator` |
+| Quick fix | `/cycle` |
+| Investigation | `/explore` |
+| Production issue | `/emergency` |
+| Code review | `/review` |
+| Debugging | `/debug` |
+
+#onboarding #context #ramp-up #new-session
+
+## ⏭️ Next Steps
+- **If Setup Complete:** Trigger `/sprint` to check tasks
+- **If Task Assigned:** Trigger `/cycle` to start work
+
+---
+
+## ENFORCEMENT REMINDER
+Always read GEMINI.md before starting work.

package/.agent/workflows/orchestrator.md

@@ -1,5 +1,5 @@
 ---
-description: [Process] Orchestrator - Full Automation Workflow
+description: Process - Orchestrator - Full Automation Workflow
 ---
 
 # Orchestrator Workflow
@@ -13,16 +13,16 @@ All phases must be executed in order. No skipping.
 
 ## State Machine Integration
 This workflow follows the state machine defined in `@BRAIN`. Before each phase transition:
-1. Run `python tools/brain/brain_cli.py validate` to check prerequisites
-2. Run `python tools/brain/brain_cli.py transition <NEW_STATE>` to update state
+1. Run `agentic-sdlc brain validate` to check prerequisites
+2. Run `agentic-sdlc brain transition <NEW_STATE>` to update state
 3. Artifacts required per state are validated automatically
 
 ### 0.0 **Team Communication (MANDATORY):**
-   - **Announce:** `python tools/communication/cli.py send --channel general --thread "SDLC-Flow" --role ORCHESTRATOR --content "Starting Full SDLC Automation."`
+   - **Announce:** `agentic-sdlc run tools/communication/cli.py send --channel general --thread "SDLC-Flow" --role ORCHESTRATOR --content "Starting Full SDLC Automation."`
 
 ### 0.1 **Initialize State (If New Sprint):**
 ```bash
-python tools/brain/brain_cli.py init <SPRINT_NUMBER>
+agentic-sdlc brain init <SPRINT_NUMBER>
 ```
 
 ## SDLC Flow (State Transitions)
@@ -55,14 +55,21 @@ python tools/brain/brain_cli.py init <SPRINT_NUMBER>
 - Update CHANGELOG, Final Review.
 
 ### Phase 11: Self-Learning
-- Run: `python tools/neo4j/sync_skills_to_neo4j.py`
-- Run: `python tools/neo4j/learning_engine.py --record-success`
+- Run: `agentic-sdlc kb compound sync`
+- Run: `agentic-sdlc learn --record-success`
 
 #orchestrator #automation #sdlc
----
-## ⚠️ 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.
+
+## ⏭️ Next Steps
+- **If Setup Complete:** Trigger @PM for Phase 1 (Planning)
+- **If Planning Complete:** Trigger @SA + @UIUX for Phase 3 (Design)
+- **If Design Complete:** Trigger @TESTER + @SECA for Phase 4 (Verification)
+- **If Dev Complete:** Trigger @TESTER for Phase 6 (Testing)
+- **If Deployment Complete:** Trigger @REPORTER for Phase 9 (Reporting)
+
+---
+## ⚠️ 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/planning.md

@@ -0,0 +1,126 @@
+---
+description: Process - Planning Phase Workflow
+---
+
+# /planning - Task Planning Workflow
+
+## ⚠️ PURPOSE
+Standardize the planning phase for tasks and sprints. Ensures proper requirements gathering, design, and user approval before implementation.
+
+// turbo-all
+
+## Quick Commands
+
+```bash
+# Generate project plan from template
+python tools/intelligence/artifact_gen/generator.py --template project-plan --context "[project name]"
+
+# Check brain state
+python tools/core/brain/brain_cli.py status
+
+# Transition to planning state
+python tools/core/brain/brain_cli.py transition PLANNING --reason "Starting new task"
+```
+
+## When to Use
+
+- Starting a new feature or project
+- Beginning a new sprint
+- Before any significant implementation
+- After receiving new requirements
+
+## Workflow Steps
+
+### 1. Initialize Planning State
+```bash
+python tools/core/brain/brain_cli.py transition PLANNING --reason "New task: [description]"
+```
+
+### 2. Gather Requirements
+- Review user request
+- Search KB for similar implementations
+- Identify stakeholders
+
+```bash
+# Research with agent
+python tools/intelligence/research/research_agent.py --task "[feature]" --type general
+
+# Deep Search (DuckDuckGo + GitHub + StackOverflow)
+python mcp/connectors/deep_search.py --search "[feature]"
+```
+
+### 3. Create Specification (New Requirement)
+For new features or complex changes, create a specification first:
+
+```bash
+# Generate specification from template
+python tools/intelligence/artifact_gen/generator.py --template specification --context "[feature description]"
+```
+
+**Spec Review:**
+- Verify user stories cover the problem
+- Confirm functional requirements are complete
+- Clarify open questions with user
+
+### 4. Create Implementation Plan
+
+Create `implementation_plan.md` based on the approved spec:
+- **Goal Description** - Link to functionality in spec
+- **Proposed Changes** - File-by-file breakdown
+- **Verification Plan** - How to test against requirements
+
+```bash
+python tools/intelligence/artifact_gen/generator.py --template project-plan --context "[description]"
+```
+
+### 5. Request User Approval
+Present the Spec and Plan to the user for review.
+
+**Approval Checklist:**
+- [ ] Requirements understood
+- [ ] Scope is clear
+- [ ] Risks identified
+- [ ] User approved
+
+### 5. Transition to Execution
+Once approved:
+```bash
+python tools/core/brain/brain_cli.py transition EXECUTION --reason "Plan approved"
+```
+
+## Planning Checklist
+
+| Item | Required |
+|------|----------|
+| Requirements documented | ✅ |
+| KB searched | ✅ |
+| Specification created | ✅ |
+| Implementation plan created | ✅ |
+| User approval obtained | ✅ |
+| Risks identified | ✅ |
+
+## Artifacts
+
+- `implementation_plan.md` - Detailed plan
+- `task.md` - Task checklist
+- Sprint folder structure (if new sprint)
+
+## Integration
+
+- **@PM** - Primary owner
+- **@BA** - Requirements
+- **@SA** - Technical design
+- **/orchestrator** - Full SDLC flow
+- **/cycle** - Task lifecycle
+
+#planning #requirements #design #approval
+
+## ⏭️ Next Steps
+- **If Approved:** Trigger `/cycle` for implementation
+- **If Rejected:** Revise plan based on feedback
+- **If Complex:** Trigger `/explore` for deeper analysis
+
+---
+
+## ENFORCEMENT REMINDER
+Never start coding without an approved plan.

package/.agent/workflows/refactor.md

@@ -0,0 +1,132 @@
+---
+description: Process - Safe Refactoring Workflow
+---
+
+# /refactor - Safe Refactoring Workflow
+
+## ⚠️ PURPOSE
+Systematic approach to refactoring code safely without breaking existing functionality.
+
+// turbo-all
+
+## When to Use
+
+- Improving code structure
+- Reducing technical debt
+- Extracting reusable components
+- Renaming/reorganizing files
+
+## Golden Rule
+> **Tests MUST pass before AND after refactoring.**
+
+## Quick Commands
+
+```bash
+# Run tests before starting
+bun test
+
+# Check current coverage
+bun test --coverage
+```
+
+## Workflow Steps
+
+### 1. Define Scope
+- [ ] What exactly will be refactored?
+- [ ] What will NOT be touched?
+- [ ] Expected outcome (cleaner code, better performance, etc.)
+
+### 2. Verify Test Coverage
+```bash
+# Ensure code is covered by tests
+bun test --coverage
+
+# If coverage is low, add tests FIRST
+```
+
+**Critical:** If no tests exist for the code being refactored, write tests first!
+
+### 3. Create Feature Branch
+```bash
+git checkout -b refactor/[description]
+```
+
+### 4. Run Tests (Baseline)
+```bash
+# All tests must pass before refactoring
+bun test
+```
+
+### 5. Refactor in Small Steps
+- [ ] Make ONE small change
+- [ ] Run tests
+- [ ] Commit if green
+- [ ] Repeat
+
+```bash
+# Atomic commits
+git commit -m "refactor: extract [function] from [module]"
+```
+
+### 6. Run Full Test Suite
+```bash
+# Verify no regressions
+bun test
+
+# Check types
+bun run typecheck
+
+# Lint check
+bun run lint
+```
+
+### 7. Code Review
+```bash
+# Create PR for review
+gh pr create --title "refactor: [description]"
+```
+
+Invoke `/review` workflow for PR.
+
+### 8. Self-Learning
+```bash
+# Document refactoring pattern
+agentic-sdlc kb compound sync
+```
+
+## Refactoring Patterns
+
+| Pattern | Description | Risk |
+|---------|-------------|------|
+| **Extract Function** | Move code to reusable function | Low |
+| **Rename** | Improve naming | Low |
+| **Move File** | Reorganize structure | Medium |
+| **Extract Module** | Split large file | Medium |
+| **Change Signature** | Update function parameters | High |
+| **Replace Algorithm** | New implementation | High |
+
+## Anti-Patterns (Don't Do)
+
+- ❌ Refactor AND add features at same time
+- ❌ Refactor without tests
+- ❌ Large refactoring without incremental commits
+- ❌ Skip code review for "safe" refactoring
+
+## Integration
+
+- **@DEV** - Primary refactorer
+- **@TESTER** - Verify test coverage
+- **/review** - Code review after refactoring
+- **/cycle** - Standard task lifecycle
+
+#refactor #code-quality #technical-debt #cleanup
+
+## ⏭️ Next Steps
+- **If Tests Pass:** Trigger `/review` for code review
+- **If Tests Fail:** Fix regressions (do not merge)
+- **If Verified:** Trigger `/release` (if applicable)
+
+---
+
+## ENFORCEMENT REMINDER
+Tests MUST pass before AND after refactoring.