agentic-sdlc 1.5.0 → 1.6.0

package/.agent/rules/artifacts.md

@@ -1,77 +1,79 @@
----
-description: Artifact and Naming Conventions
----
-# Artifact & Naming Conventions
-## ⚠️ DOCUMENTATION LOCATION RULE (PROJECT-SPECIFIC)
-Documentation MUST be located within each project's directory, NOT in the root docs/ folder (except for global guides).
-### Correct Structure
-`
-root/
-├── docs/ (Global System Docs ONLY)
-│   ├── ARCHITECTURE.md
-│   └── BRAIN-GUIDE.md
-│
-└── projects/
-    └── [project-name]/
-        └── docs/ (Project Specific Docs)
-            └── sprints/
-                └── sprint-[N]/
-                    ├── plans/
-                    ├── requirements/
-                    ├── designs/
-                    └── logs/
-`
-## Artifact Naming Convention
-Use versioned names attached to the current Sprint:
-| Artifact | Owner |
-|----------|-------|
-| Project-Plan-Sprint-[N]-v*.md | PM |
-| Product-Backlog-Sprint-[N]-v*.md | PO |
-| UIUX-Design-Spec-Sprint-[N]-v*.md | UIUX |
-| System-Design-Spec-Sprint-[N]-v*.md | SA |
-| Design-Verification-Report-Sprint-[N]-v*.md | QA |
-| Security-Review-Report-Sprint-[N]-v*.md | SecA |
-| Development-Log-Sprint-[N]-v*.md | DEV |
-| DevOps-Plan-and-Log-Sprint-[N]-v*.md | DevOps |
-| Test-Report-Sprint-[N]-v*.md | TESTER |
-| Phase-Report-Sprint-[N]-v*.md | REPORTER |
-| Master-Documentation.md | REPORTER |
-| Final-Project-Report.md | REPORTER |
-| Final-Approval-Report.md | STAKEHOLDER |
-## ⚠️ CRITICAL LOCATION RULE (SPRINT FOLDERS)
-ALL project artifacts MUST be created in the **PROJECT'S** workspace with organized structure based on **Sprint**:
-**Base Directory:** projects/[project-name]/docs/sprints/sprint-[N]/
-| Category | Folder Path | Content Example | Owner |
-|----------|-------------|-----------------|-------|
-| Plans | .../plans/ | Project-Plan-Sprint-[N]-v*.md, Product-Backlog-Sprint-[N]-v*.md | PM, PO |
-| Designs | .../designs/ | System-Design-Spec-Sprint-[N]-v*.md, UIUX-Design-Spec-Sprint-[N]-v*.md | SA, UIUX |
-| Reviews | .../reviews/ | Design-Verification-Report-Sprint-[N]-v*.md, Security-Review-Report-Sprint-[N]-v*.md | QA, SecA |
-| Logs | .../logs/ | Development-Log-Sprint-[N]-v*.md, DevOps-Plan-and-Log-Sprint-[N]-v*.md | DEV, DevOps |
-| Tests | .../tests/ | Test-Report-Sprint-[N]-v*.md | TESTER |
-| Reports | .../reports/ | Phase-Report-Sprint-[N]-v*.md | REPORTER |
-| Global | .../global/reports/ | Final-Project-Report.md, Final-Approval-Report.md | REPORTER, STAKEHOLDER |
-| Global | projects/[project-name]/docs/global/ | Master-Documentation.md | REPORTER |
-**FORBIDDEN LOCATIONS:**
-- .agent/ directory (reserved for instructions only)
-- Global docs/ folder for project-specific artifacts.
-## ⚠️ CHANGELOG RULE
-**CRITICAL:** Do NOT create or update CHANGELOG.md in the project root.
-- CHANGELOG.md exists ONLY as a template in .agent/templates/
-- All project changes are documented in sprint-specific reports
-- Use Phase-Report-Sprint-[N]-v*.md for sprint summaries
-- Use Final-Project-Report.md for overall project changelog
-## Mandatory Documentation Tags
-Every action must be tagged with appropriate hashtags:
-| Category | Tags |
-|----------|------|
-| **Planning** | #planning, #product-owner, #backlog |
-| **Design** | #designing, #uiux-design |
-| **Verification** | #verify-design, #security-review |
-| **Development** | #development, #devops |
-| **Testing** | #testing |
-| **Bug Fixes** | #fixbug-critical, #fixbug-high, #fixbug-medium, #fixbug-low |
-| **Status** | #blocked, #hotfix, #rollback |
-| **Deployment** | #deployed-staging, #deployed-production |
-| **Research** | #searching |
-| **Reporting** | #reporting, #stakeholder-review |
+---
+description: Artifact and Naming Conventions
+---
+# Artifact & Naming Conventions
+## ⚠️ DOCUMENTATION LOCATION RULE (PROJECT-SPECIFIC)
+Documentation MUST be located within each project's directory, NOT in the root docs/ folder (except for global guides).
+### Correct Structure
+`
+root/
+├── docs/ (Global System Docs ONLY)
+│   ├── ARCHITECTURE.md
+│   └── BRAIN-GUIDE.md
+│
+└── projects/
+    └── [project-name]/
+        └── docs/ (Project Specific Docs)
+            └── sprints/
+                └── sprint-[N]/
+                    ├── plans/
+                    ├── requirements/
+                    ├── designs/
+                    └── logs/
+`
+## Artifact Naming Convention
+Use versioned names attached to the current Sprint:
+| Artifact | Owner |
+|----------|-------|
+| Project-Plan-Sprint-[N]-v*.md | PM |
+| Product-Backlog-Sprint-[N]-v*.md | PO |
+| UIUX-Design-Spec-Sprint-[N]-v*.md | UIUX |
+| System-Design-Spec-Sprint-[N]-v*.md | SA |
+| Design-Verification-Report-Sprint-[N]-v*.md | QA |
+| Security-Review-Report-Sprint-[N]-v*.md | SecA |
+| Development-Log-Sprint-[N]-v*.md | DEV |
+| DevOps-Plan-and-Log-Sprint-[N]-v*.md | DevOps |
+| Test-Report-Sprint-[N]-v*.md | TESTER |
+| Phase-Report-Sprint-[N]-v*.md | REPORTER |
+| Master-Documentation.md | REPORTER |
+| Final-Project-Report.md | REPORTER |
+| Final-Approval-Report.md | STAKEHOLDER |
+## ⚠️ CRITICAL LOCATION RULE (SPRINT FOLDERS)
+ALL project artifacts MUST be created in the **PROJECT'S** workspace with organized structure based on **Sprint**:
+**Base Directory:** projects/[project-name]/docs/sprints/sprint-[N]/
+| Category | Folder Path | Content Example | Owner |
+|----------|-------------|-----------------|-------|
+| Plans | .../plans/ | Project-Plan-Sprint-[N]-v*.md, Product-Backlog-Sprint-[N]-v*.md | PM, PO |
+| Designs | .../designs/ | System-Design-Spec-Sprint-[N]-v*.md, UIUX-Design-Spec-Sprint-[N]-v*.md | SA, UIUX |
+| Reviews | .../reviews/ | Design-Verification-Report-Sprint-[N]-v*.md, Security-Review-Report-Sprint-[N]-v*.md | QA, SecA |
+| Logs | .../logs/ | Development-Log-Sprint-[N]-v*.md, DevOps-Plan-and-Log-Sprint-[N]-v*.md | DEV, DevOps |
+| Tests | .../tests/ | Test-Report-Sprint-[N]-v*.md | TESTER |
+| Reports | .../reports/ | Phase-Report-Sprint-[N]-v*.md | REPORTER |
+| Global | .../global/reports/ | Final-Project-Report.md, Final-Approval-Report.md | REPORTER, STAKEHOLDER |
+| Global | projects/[project-name]/docs/global/ | Master-Documentation.md | REPORTER |
+**FORBIDDEN LOCATIONS:**
+- .agent/ directory (reserved for instructions only)
+- Global docs/ folder for project-specific artifacts.
+## ⚠️ CHANGELOG RULE (UPDATED 2026-01-04)
+**Repository vs Project:**
+1. **Root CHANGELOG.md:** ALLOWED for **Repository versioning only**.
+   - MUST be managed AUTOMATICALLY by `release.py`.
+   - Manual edits are FORBIDDEN except for fixing formatting.
+2. **Project Reports:**
+   - Detailed project changes must still be documented in sprint reports.
+   - Use Phase-Report-Sprint-[N]-v*.md for detailed tracking.
+## Mandatory Documentation Tags
+Every action must be tagged with appropriate hashtags:
+| Category | Tags |
+|----------|------|
+| **Planning** | #planning, #product-owner, #backlog |
+| **Design** | #designing, #uiux-design |
+| **Verification** | #verify-design, #security-review |
+| **Development** | #development, #devops |
+| **Testing** | #testing |
+| **Bug Fixes** | #fixbug-critical, #fixbug-high, #fixbug-medium, #fixbug-low |
+| **Status** | #blocked, #hotfix, #rollback |
+| **Deployment** | #deployed-staging, #deployed-production |
+| **Research** | #searching |
+| **Reporting** | #reporting, #stakeholder-review |
 | **Knowledge** | #knowledge-base, #lessons-learned |

package/.agent/rules/git-workflow.md

@@ -1,25 +1,45 @@
----
-description: Unified Git and Task Workflow (Branching, Committing, Merging)
----
-# Git & Task Management Workflow
-**Requirement:** All tasks and artifacts must follow the **Branch-Based Workflow**.
-## A. Branching Strategy (MANDATORY)
-❌ **NEVER** commit directly to main or master.
-### Branch Naming Convention
-| Type | Prefix | Use Case |
-|------|--------|----------|
-| **Planning** | plan/ | Project plans, product backlogs |
-| **Design** | design/ | Architecture schematics, UI specs |
-| **Feature** | eat/ | New functionality |
-| **Fix** | ix/ | Bug fixes |
-| **Docs** | docs/ | General documentation |
-**Format:** prefix/TASK-ID-short-name (e.g., plan/SPRINT-2-setup)
-### Workflow
-1. **Start:** git checkout -b prefix/TASK-ID-name from main.
-2. **Work:** Create artifacts or code.
-3. **Push:** git push -u origin prefix/TASK-ID-name.
-4. **Docs-as-Code:** Treat documentation exactly like code.
-## B. Definition of Done (DoD)
-1. Branch created.
-2. Artifacts implemented.
+---
+description: Unified Git and Task Workflow (Branching, Committing, Merging)
+---
+# Git & Task Management Workflow
+**Requirement:** All tasks and artifacts must follow the **Branch-Based Workflow**.
+## A. Branching Strategy (MANDATORY)
+❌ **NEVER** commit directly to main or master.
+### Branch Naming Convention
+| Type | Prefix | Use Case |
+|------|--------|----------|
+| **Planning** | plan/ | Project plans, product backlogs |
+| **Design** | design/ | Architecture schematics, UI specs |
+| **Feature** | feat/ | New functionality |
+| **Fix** | fix/ | Bug fixes |
+| **Docs** | docs/ | General documentation |
+**Format:** prefix/TASK-ID-short-name (e.g., plan/SPRINT-2-setup)
+### Workflow
+1. **Start:** git checkout -b prefix/TASK-ID-name from main.
+2. **Work:** Create artifacts or code.
+3. **Push:** git push -u origin prefix/TASK-ID-name.
+4. **Docs-as-Code:** Treat documentation exactly like code.
+## B. Definition of Done (DoD)
+1. Branch created.
+2. Artifacts implemented.
 3. Pull Request created & merged.
+## C. Release Workflow (AUTOMATED)
+Releases are managed by the Release Agent (`release.py`).
+1. **Trigger:** Human or CI runs `/release`.
+2. **Commit:** Agent creates `chore(release): vX.Y.Z` commit.
+3. **Tag:** Agent creates `vX.Y.Z` tag.
+4. **Push:** Agent pushes commit and tags.
+## D. Commit Conventions (MANDATORY)
+We follow [Conventional Commits](https://www.conventionalcommits.org/) to enable automated semantic versioning.
+**Format:** `type(scope): description`
+**Types:**
+- `feat`: New feature (MINOR bump)
+- `fix`: Bug fix (PATCH bump)
+- `docs`: Documentation only
+- `style`: Formatting, missing semi-colons, etc.
+- `refactor`: Code change that neither fixes a bug nor adds a feature
+- `perf`: Code change that improves performance
+- `test`: Adding missing tests or correcting existing tests
+- `chore`: Build process, auxiliary tools, libraries updates
+**Breaking Changes:**
+Append `!` after type/scope (e.g., `feat!: drop support for Node 12`) for MAJOR bump.

package/.agent/rules/global.md

@@ -1,7 +1,7 @@
 # TeamLifecycle Global Rules & Conventions
-(Version 1.4 – Strict IT SDLC Simulation for Google Antigravity)
+(Version 1.5 – Strict IT SDLC Simulation for Google Antigravity)
 
-**Last Updated:** 2026-01-01  
+**Last Updated:** 2026-01-04
 **Maintainer:** Project Team
 
 ---
@@ -134,6 +134,11 @@ Use this at the end of **every artifact**:
 #[appropriate-tags]
 ```
 
+### 8. Tooling Standards (New)
+- **Polyglot Support:** Tools should run in environment-agnostic ways (e.g. CLI bridges).
+- **Testing:** All tools MUST be covered by integration tests in `tests/`.
+- **CLI Interface:** All tools MUST support `--help` for discoverability.
+
 ---
 
 ## Final Note
@@ -150,10 +155,9 @@ Use this at the end of **every artifact**:
 
 | Version | Date | Changes |
 |---------|------|---------|
+| 1.5 | 2026-01-04 | Added Tooling Standards, Polyglot Support. |
 | 1.4 | 2026-01-01 | Split large rules into artifacts.md, git-workflow.md, knowledge-base.md |
 | 1.3 | 2026-01-01 | Added Task Management & Atomic Git Commit Rules |
 | 1.2 | 2026-01-01 | Migrated to Native Agent structure (.agent/). Updated paths. |
 | 1.1 | 2025-12-23 | Added PO role, new tags (#product-owner, #backlog, #blocked, #hotfix, #rollback, #deployed-*), Definition of Done, Cross-Role Dependencies diagram, Incident/Hotfix workflow, Changelog |
 | 1.0 | Initial | Initial release with 10 roles and core SDLC flow |
-
-

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

@@ -62,6 +62,11 @@ kb compound search "architecture-pattern"
 - Communicate blockers immediately
 - Share learnings with team via KB
 
+### 7. Tooling Standards
+- **Polyglot:** Support Python/Node environments (use `agentic-sdlc` bridge).
+- **Testing:** ALL new tools must include integration tests in `tests/`.
+- **CLI:** Ensure tools have `-h/--help` support.
+
 ## Artifact Requirements
 
 **Focus on code, not logs.**
@@ -90,16 +95,16 @@ kb compound search "architecture-pattern"
 ### How to Document
 ```bash
 # Interactive KB entry creation
-kb add
+agentic-sdlc kb add
 
 # Or compound add (auto-syncs to Neo4j)
-kb compound add
+agentic-sdlc kb compound add
 
 # Update index
-kb index
+agentic-sdlc kb index
 
 # Full sync to Neo4j Brain
-kb compound sync
+agentic-sdlc kb compound sync
 ```
 
 ### KB Entry Template

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.
 

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.

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/workflows/brain.md

@@ -16,72 +16,71 @@ Brain is NOT an executor—it monitors, detects issues, routes to handlers, scor
 
 ### Observer (Halt on Errors)
 ```bash
-python tools/brain/observer.py --watch       # Monitor workflows
-python tools/brain/observer.py --halt "Err"  # Halt system
-python tools/brain/observer.py --resume      # Resume after halt
+agentic-sdlc run tools/brain/observer.py --watch       # Monitor workflows
+agentic-sdlc run tools/brain/observer.py --halt "Err"  # Halt system
+agentic-sdlc run tools/brain/observer.py --resume      # Resume after halt
 ```
 
 ### Judge (Score Quality)
 ```bash
-python tools/brain/judge.py --score "path/to/report.md"
-python tools/brain/judge.py --review --sprint 1
-python tools/brain/judge.py --threshold 7    # Set pass threshold
+agentic-sdlc run tools/brain/judge.py --score "path/to/report.md"
+agentic-sdlc run tools/brain/judge.py --review --sprint 1
+agentic-sdlc run tools/brain/judge.py --threshold 7    # Set pass threshold
 ```
 
 ### Learner (Auto-Learning)
 ```bash
-python tools/brain/learner.py --learn "Task completed"
-python tools/brain/learner.py --watch
-python tools/brain/learner.py --stats
+agentic-sdlc learn --learn "Task completed"
+agentic-sdlc learn --watch
+agentic-sdlc learn --stats
 ```
 
 ### A/B Tester (Compare Options)
 ```bash
-python tools/brain/ab_tester.py --create "Test description"
-python tools/brain/ab_tester.py --compare --test-id TEST-001
-python tools/brain/ab_tester.py --select A --test-id TEST-001
+agentic-sdlc run tools/brain/ab_tester.py --create "Test description"
+agentic-sdlc run tools/brain/ab_tester.py --compare --test-id TEST-001
+agentic-sdlc run tools/brain/ab_tester.py --select A --test-id TEST-001
 ```
 
 ### Model Optimizer (Token Efficiency)
 ```bash
-python tools/brain/model_optimizer.py --recommend "Task description"
-python tools/brain/model_optimizer.py --record --model "gemini-2.5" --tokens 1500
+agentic-sdlc run tools/brain/model_optimizer.py --recommend "Task description"
+agentic-sdlc run tools/brain/model_optimizer.py --record --model "gemini-2.5" --tokens 1500
 ```
 
 ### Self-Improver (Create Improvement Plans)
 ```bash
-python tools/brain/self_improver.py --analyze  # Analyze all data
-python tools/brain/self_improver.py --plan     # Create improvement plan
-python tools/brain/self_improver.py --apply-plan PLAN-ID
+agentic-sdlc run tools/brain/self_improver.py --analyze  # Analyze all data
+agentic-sdlc run tools/brain/self_improver.py --plan     # Create improvement plan
+agentic-sdlc run tools/brain/self_improver.py --apply-plan PLAN-ID
 ```
 
 ## State Management
 ```bash
-python tools/brain/brain_cli.py init 1          # Initialize sprint
-python tools/brain/brain_cli.py status          # Check status
-python tools/brain/brain_cli.py transition STATE --reason "Reason"
-python tools/brain/brain_cli.py validate        # Validate state
-python tools/brain/brain_cli.py rollback        # Rollback
+agentic-sdlc brain init 1          # Initialize sprint
+agentic-sdlc brain status          # Check status
+agentic-sdlc brain transition STATE --reason "Reason"
+agentic-sdlc brain validate        # Validate state
+agentic-sdlc brain rollback        # Rollback
 ```
 
 ## Supervisor Commands
 ```bash
-python tools/brain/brain_cli.py watch   # Monitor workflows
-python tools/brain/brain_cli.py route "request"  # Route to workflow
-python tools/brain/brain_cli.py health  # Health check
+agentic-sdlc brain watch   # Monitor workflows
+agentic-sdlc run tools/brain/brain_cli.py route "request"  # Route to workflow
+agentic-sdlc health  # Health check
 ```
 
 ## Sync Commands
 ```bash
-python tools/neo4j/brain_parallel.py --sync  # Quick sync
-python tools/neo4j/brain_parallel.py --full  # Full sync
+agentic-sdlc kb compound sync
+agentic-sdlc kb compound sync --full
 ```
 
 #brain #root-layer #meta-controller
-
-
----
-
-## ENFORCEMENT REMINDER
-Before executing, complete /preflight checks.
 
+
+---
+
+## ENFORCEMENT REMINDER
+Before executing, complete /preflight checks.

package/.agent/workflows/cycle.md

@@ -11,14 +11,14 @@ description: [Process] Complete Task Lifecycle - Plan → Work → Review → Co
 4. **SELF-LEARNING:** After completion, update Neo4j.
 
 ### 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/communication/cli.py history --channel general --limit 10`
+   - **Announce Start:** `agentic-sdlc run tools/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.
@@ -47,15 +47,15 @@ git push -u origin feat/TASK-ID-name
 
 ### 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
+agentic-sdlc learn --record-success "TASK-ID" --task-type "feature"
 ```
 - 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
+#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.

package/.agent/workflows/orchestrator.md

@@ -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,14 @@ 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
+---
+## ⚠️ 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.

package/CHANGELOG.md

@@ -4,6 +4,34 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+---
+
+## [1.6.0] - 2026-01-04 (Sprint 6)
+
+### Added
+- add release management tool for automated changelog generation and version bumping based on conventional commits
+
+### Documentation
+- [Workflows] standardize on agentic-sdlc cli and unified roles
+- [Templates] update templates for unified roles and automation
+- [Skills] consolidate roles and update for release/automation
+- [Rules] update release workflow and tooling standards
+
+### Testing
+- add release manager tests and fix breaking change detection
+
+
+---
+
+## [1.5.1] - 2026-01-04 (Sprint 6)
+
+### Documentation
+- update CLI documentation and landing page
+
+### Maintenance
+- add chat.db and research artifacts
+
+
 ---
 
 ## [1.5.0] - 2026-01-04 (Sprint 6)

package/README.md

@@ -183,10 +183,15 @@ agentic-sdlc ide all            # Setup all supported IDEs
 # Knowledge Base
 agentic-sdlc init-kb            # Initialize KB
 agentic-sdlc list               # List roles & workflows
+agentic-sdlc kb search "query"  # Search KB
 
-# Brain System (see GEMINI.md)
+# Release Management
+agentic-sdlc release preview    # Preview changes
+agentic-sdlc release release    # Full release cycle
+
+# Brain System
+agentic-sdlc agent              # Run default agent
 python tools/neo4j/brain_parallel.py --sync      # Sync brain
-python tools/neo4j/brain_parallel.py --recommend  # Get recommendations
 ```
 
 ## 🌟 Why Agentic SDLC?

package/bin/cli.js

@@ -13,7 +13,9 @@ const commands = {
     'agent': 'tools/run.py',
     'validate': 'tools/validation/validate.py',
     'health': 'tools/validation/health-check.py',
-    'setup': 'tools/setup/init.py'
+    'setup': 'tools/setup/init.py',
+    'brain': 'tools/brain/brain_cli.py',
+    'research': 'tools/research/research_agent.py'
 };
 
 const args = process.argv.slice(2);
@@ -29,6 +31,8 @@ function printUsage() {
     console.log("  validate  Validate system");
     console.log("  health    Check health");
     console.log("  setup     Initialize project");
+    console.log("  brain     Brain system management");
+    console.log("  research  Research agent");
 }
 
 if (!command || command === '--help' || command === '-h') {

package/docs/research-reports/research-20260104-094131.json

@@ -0,0 +1,94 @@
+{
+  "task": "cli documentation",
+  "task_type": "feature",
+  "timestamp": "2026-01-04T09:41:31.918753",
+  "sources": {
+    "knowledge_base": {
+      "found": true,
+      "entries": [
+        {
+          "file": ".agent\\knowledge-base\\features\\figma-landing-page-workflow.md",
+          "category": "features",
+          "title": "Untitled",
+          "relevance": 1.0
+        },
+        {
+          "file": ".agent\\knowledge-base\\features\\figma-mcp-sa-guide.md",
+          "category": "features",
+          "title": "Figma MCP Integration for @SA",
+          "relevance": 1.0
+        },
+        {
+          "file": ".agent\\knowledge-base\\features\\figma-mcp-uiux-guide.md",
+          "category": "features",
+          "title": "Figma MCP Integration for @UIUX",
+          "relevance": 1.0
+        },
+        {
+          "file": ".agent\\knowledge-base\\features\\KB-2026-01-01-004-uiux-design-skills-2026.md",
+          "category": "features",
+          "title": "Essential UI/UX Design Skills for 2026",
+          "relevance": 1.0
+        },
+        {
+          "file": ".agent\\knowledge-base\\features\\KB-2026-01-01-005-modern-ai-landing-page-ui.md",
+          "category": "features",
+          "title": "Build successful",
+          "relevance": 1.0
+        },
+        {
+          "file": ".agent\\knowledge-base\\architecture\\KB-2026-01-01-003-neo4j-graph-database-skills.md",
+          "category": "architecture",
+          "title": "Neo4j Graph Database Skills & Best Practices",
+          "relevance": 1.0
+        },
+        {
+          "file": ".agent\\knowledge-base\\features\\KB-2026-01-01-001-landing-page-design-trends-2026.md",
+          "category": "features",
+          "title": "Modern Landing Page Design Trends for 2026",
+          "relevance": 0.5
+        },
+        {
+          "file": ".agent\\knowledge-base\\features\\KB-2026-01-01-006-award-winning-landing-page-patterns.md",
+          "category": "features",
+          "title": "Build successful",
+          "relevance": 0.5
+        },
+        {
+          "file": ".agent\\knowledge-base\\features\\KB-2026-01-02-001-cleanup-workflow.md",
+          "category": "features",
+          "title": "Standard cleanup",
+          "relevance": 0.5
+        },
+        {
+          "file": ".agent\\knowledge-base\\features\\KB-2026-01-02-002-landing-page-monorepo-architecture.md",
+          "category": "features",
+          "title": "✓ Built successfully in 3.20s",
+          "relevance": 0.5
+        },
+        {
+          "file": ".agent\\knowledge-base\\performance\\KB-2026-01-02-lazy-loading-optimization.md",
+          "category": "performance",
+          "title": "Untitled",
+          "relevance": 0.5
+        }
+      ],
+      "categories": [
+        "features",
+        "architecture",
+        "performance"
+      ]
+    }
+  },
+  "summary": {
+    "total_sources": 1,
+    "findings": [
+      "Found 11 related entries in Knowledge Base"
+    ],
+    "recommendations": [
+      "✓ Strong knowledge base available - Review existing solutions before starting"
+    ],
+    "related_entries": 11,
+    "confidence": "high"
+  }
+}

package/docs/research-reports/research-20260104-094131.md

@@ -0,0 +1,78 @@
+# Research Report
+
+**Task:** cli documentation
+**Type:** feature
+**Date:** 2026-01-04T09:41:31.918753
+
+## Summary
+
+- **Confidence:** high
+- **Related Entries:** 11
+
+### Findings
+
+- Found 11 related entries in Knowledge Base
+
+### Recommendations
+
+- ✓ Strong knowledge base available - Review existing solutions before starting
+
+## Detailed Results
+
+### Knowledge Base (11 entries)
+
+#### Untitled
+- File: `.agent\knowledge-base\features\figma-landing-page-workflow.md`
+- Category: features
+- Relevance: 100%
+
+#### Figma MCP Integration for @SA
+- File: `.agent\knowledge-base\features\figma-mcp-sa-guide.md`
+- Category: features
+- Relevance: 100%
+
+#### Figma MCP Integration for @UIUX
+- File: `.agent\knowledge-base\features\figma-mcp-uiux-guide.md`
+- Category: features
+- Relevance: 100%
+
+#### Essential UI/UX Design Skills for 2026
+- File: `.agent\knowledge-base\features\KB-2026-01-01-004-uiux-design-skills-2026.md`
+- Category: features
+- Relevance: 100%
+
+#### Build successful
+- File: `.agent\knowledge-base\features\KB-2026-01-01-005-modern-ai-landing-page-ui.md`
+- Category: features
+- Relevance: 100%
+
+#### Neo4j Graph Database Skills & Best Practices
+- File: `.agent\knowledge-base\architecture\KB-2026-01-01-003-neo4j-graph-database-skills.md`
+- Category: architecture
+- Relevance: 100%
+
+#### Modern Landing Page Design Trends for 2026
+- File: `.agent\knowledge-base\features\KB-2026-01-01-001-landing-page-design-trends-2026.md`
+- Category: features
+- Relevance: 50%
+
+#### Build successful
+- File: `.agent\knowledge-base\features\KB-2026-01-01-006-award-winning-landing-page-patterns.md`
+- Category: features
+- Relevance: 50%
+
+#### Standard cleanup
+- File: `.agent\knowledge-base\features\KB-2026-01-02-001-cleanup-workflow.md`
+- Category: features
+- Relevance: 50%
+
+#### ✓ Built successfully in 3.20s
+- File: `.agent\knowledge-base\features\KB-2026-01-02-002-landing-page-monorepo-architecture.md`
+- Category: features
+- Relevance: 50%
+
+#### Untitled
+- File: `.agent\knowledge-base\performance\KB-2026-01-02-lazy-loading-optimization.md`
+- Category: performance
+- Relevance: 50%
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentic-sdlc",
-  "version": "1.5.0",
+  "version": "1.6.0",
   "description": "Simulating a complete Software Development Lifecycle (SDLC) with specialized AI Agents.",
   "type": "module",
   "private": false,

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