agentic-orchestration

Feature development pipeline for GitHub repositories using Claude LLMs. Requirements engineer takes input from specs.md or user, creates a GitHub issue as feature request, then architect plans, tdd-developer implements, qa tests, and reviewer peer-reviews the pull request. Triggers on: github pipeline, github feature, claude pipeline, specs pipeline.

Full feature development pipeline for GitLab repositories using Copilot CLI agents and Jira integration. Takes a Jira item through requirements engineering, test planning, architecture, TDD development, testing, and MR review. Triggers on: gitlab pipeline, gitlab feature, copilot pipeline.

Incident response pipeline for GitLab repositories using Copilot CLI, Jira, and troubleshooter. Takes a Jira incident, investigates root cause, optionally fixes via TDD, and reviews the merge request. User decides whether to fix or just document findings on the Jira ticket. Triggers on: gitlab incident, incident pipeline, troubleshoot gitlab.

Entry point for all new work. Orchestrates the full agent pipeline: architect (Opus) designs spec+todo, tdd-developer (Sonnet) implements via TDD, qa (Opus) hunts spec/impl gaps, reviewer (Sonnet) reviews code. Triggers on: plan, new feature, start work, build feature.

Create an Architecture Decision Record in docs/decisions/ and optionally sync to Confluence for business projects. Use when making significant technical decisions. Triggers on: architecture decision, ADR, technical decision.

Ultra-compressed communication mode — cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Slash-only: /caveman to enable, "stop caveman" / "normal mode" to disable.

Drive the GitHub CLI (gh) to review a pull request — fetch the diff and context, post inline review comments anchored to specific diff lines, open conceptual conversation threads, and submit a verdict (APPROVE / REQUEST_CHANGES / COMMENT). Use when reviewing or commenting on a GitHub PR. Triggers on: gh, github cli, pull request, pr review, post pr comment, gh api, review github pr.

Drive the GitLab CLI (glab) to review a merge request — fetch the diff and context, post inline discussion comments anchored to specific diff lines (via a position object), open conceptual resolvable threads, and express a verdict with approve / revoke + a summary thread. Use when reviewing or commenting on a GitLab MR. Triggers on: glab, gitlab cli, merge request, mr review, post mr comment, glab api, review gitlab mr.

Iterative spec elicitation for vague ideas. Asks one question at a time to develop a thorough, step-by-step spec. Use BEFORE /plan when the idea is too fuzzy to hand to the architect. Pairs with explorer if the brainstorm leads to wanting to prototype. Triggers on: brainstorm, fuzzy idea, help me think, vague idea.

Generate an Obsidian session report at the end of a coding session. Summarizes commits, tests, decisions, blockers, and next steps. Triggers on: end session, session report, wrap up, done for today.

Pull a Jira issue and scaffold a feature spec with test stubs. Use when starting work on a new Jira ticket or GitHub issue. Reads acceptance criteria, description, and comments. Requires Jira MCP server for Jira tickets. Triggers on: ticket, issue, PROJ-*, start work on, pick up.

Bypass the confidence gate for the next PR/MR creation. Logs the reason for accountability. Auto-clears after the next gate fire. Triggers on: override confidence, bypass confidence, force PR.

Exploratory mode — spike, prototype, brainstorm. Throwaway code under spikes/. Use when the goal is to learn or generate options, NOT to ship. Pairs with the explorer agent. Triggers on: explore, spike, prototype, experiment, sketch, try out.

Multi-cluster reference data for troubleshooting across EMEA, APAC, NAM. Contains kubectl contexts, ArgoCD cluster names, and Log Analytics workspace details per region. Auto-loaded by the troubleshooter agent.

Create a pull request (GitHub) or merge request (GitLab) with conventional description, test summary, and checklist. Auto-detects platform. Triggers on: create pr, create mr, pull request, merge request, push and pr.

Temporarily bypass the TDD commit gate. Use for documentation changes, CI/CD config, dependency updates, or hotfixes. Logs the reason for accountability. Bypass auto-clears after the next commit. Triggers on: skip tdd, bypass tests, no-tdd.

Strict test-driven development workflow. Use when implementing any feature, bug fix, or code change. Follows RED → GREEN → REFACTOR cycle with stack-aware test runner detection. Triggers on: implement, build, create, add feature, fix bug, write code for.