The five agent suites in detail

💻 Development Suite

Implements approved stories in priority order, commits code, opens PRs and stamps every story with full traceability.

Inputs

• Approved roadmap (story order)
• Repository handle (GitHub / GitLab / Bitbucket)
• Coding standards: pyproject.toml, ESLint config, .editorconfig

Plan-and-Code loop (ReAct)

• Story picker — pulls next Ready story, marks In Progress
• Context builder — RAG over repo with tree-sitter AST-aware chunking
• Planner LLM — step-by-step plan
• Coder LLM — Claude / GPT-4 / Qwen-Coder / DeepSeek emit diffs
• Self-review LLM — re-reads diff against acceptance criteria
• Local verify — ruff, eslint, mypy, tsc, existing unit tests

Commit + PR workflow

• One feature branch per story (feat/PROJ-123-…)
• Conventional Commits — reuses repo's existing workflow
• PR description auto-generated, linked back to the story
• Sandboxed execution in ephemeral Docker containers

Story closure payload

• What was done — LLM summary of the diff
• DoD checklist — ticked
• Code pointers — files + line ranges + permalinks
• Test pointers — tests added or modified

🧪 Testing Suite

Independently verifies that merged code fulfils the design. Maintains a monotonically-growing regression registry and gates the Production Ready state.

Design ↔ Code conformance

• LLM-as-judge scores every acceptance criterion
• Mismatches file bugs immediately — no test gen for failed ACs

Test generation

• Positive (happy path) tests
• Negative (invalid input, auth, boundary) tests
• Edge cases (empty, max, unicode, concurrency)
• Integration tests across services
• UI tests via Playwright / Cypress
• Stable ids: TC-<storyKey>-<n>

Execution engine

• Runs full regression on every story completion
• Parallelised via pytest-xdist, vitest, playwright workers
• Captures screenshots, video, console + network HAR for UI tests
• Security gates: bandit, semgrep, trivy, OWASP ZAP

Bug lifecycle & Prod-Ready gate

• Any failure → auto-Jira bug with stack, screenshot, suspected file
• Originating story reopened, re-queued to Dev
• Story is Production Ready only when: ACs pass, all its tests pass, no open bugs, regression green

🚀 Production Suite

Promotes Production-Ready artifacts to live environments safely and verifies in-place.

Release composition

• Bundles all Production Ready stories into a release candidate
• Generates release notes from story summaries
• Awaits PO / Release-Manager approval ✅

Deploy strategies

• Blue/green, canary, rolling — selectable per environment
• IaC: Terraform / Helm / Pulumi
• Targets: Kubernetes, ECS, Lambda, Azure App Service
• Reuses existing executors (Terraform, Kubernetes, Docker)

Post-deploy verification

• Re-runs the Testing Suite against the production URL
• Critical-path smoke now, full regression off-hours
• Synthetic monitoring: uptime, Lighthouse, k6 baseline

Promotion / Rollback

• Green → promote canary to 100%
• Red → automatic rollback + bug + story re-queued
• GitOps via ArgoCD / FluxCD

🛰️ DevOps Suite

The suite that already exists in this repository — the other four are being built around it. Watches the live system, root-causes incidents, self-heals or files a bug story back to Dev.

Capabilities live today

• Pluggable agents: Jenkins, K8s, GitHub Actions, Ansible, Terraform, Docker, Git, generic API
• Failure-context extraction
• Decision engine with per-agent thresholds
• Memory + audit store
• Remediation orchestrator
• Jira / PagerDuty / ServiceNow integrations
• Grafana dashboard
• Daily test runner + scheduler

Loop closure

When the DevOps agent cannot self-heal:

• Builds a FailureContext (logs, metrics, traces, suspect commit)
• Drafts a bug-story (title, repro, ACs for the fix)
• Pushes to Jira and tags the originating release
• Hands off to the Development Suite — lifecycle restarts

What's coming next

• Phase 2 — multi-tenant SaaS mode
• Phase 3 — real-time RCA streaming dashboard
• Phase 4 — predictive failure detection
• Phase 5 — auto-PR generation for known patterns