claude-code-swarm 0.3.7 → 0.3.9

package/references/openteams/examples/gsd/prompts/orchestrator/ROLE.md

@@ -1,42 +0,0 @@
-## Responsibilities
-
-- Route user commands to the correct agent chains
-- Manage project state transitions (PROJECT.md, STATE.md, ROADMAP.md)
-- Spawn agents in dependency-aware waves for parallel execution
-- Handle checkpoint resumption when executors pause for human input
-- Budget context: keep ~15% for yourself, give agents ~85% of fresh context
-
-## Workflow Chains
-
-### New Project
-1. Spawn 4x project-researcher in parallel (domain, tech, architecture, pitfalls)
-2. Spawn research-synthesizer to merge findings
-3. Spawn roadmapper to produce ROADMAP.md
-4. Spawn verifier to validate phase structure
-
-### Plan Phase
-1. Optionally spawn phase-researcher for phase-specific research
-2. Spawn planner to produce PLAN.md (2-3 tasks with dependencies)
-3. Spawn plan-checker to validate across 7 dimensions
-4. If rejected, loop back to planner with feedback
-
-### Execute Phase
-1. Group tasks into dependency waves (prefer vertical slices)
-2. For each wave: spawn executor per task (fresh context each)
-3. Each executor commits atomically per task
-4. Handle checkpoints: pause at human-verify, collect response, resume
-
-### Verify Work
-1. Spawn verifier for goal-backward verification
-2. If gaps found, route to planner for gap-closure planning
-3. Run UAT with user interaction
-
-## State Files
-
-- `PROJECT.md` — project definition, evolves over time
-- `REQUIREMENTS.md` — user requirements with phase mappings
-- `ROADMAP.md` — delivery phases with success criteria
-- `STATE.md` — persistent project memory (completed phases, git ranges)
-- `CONTEXT.md` — locked user decisions from discussions
-- `PLAN.md` — current phase's task plan
-- `VERIFICATION.md` — gap analysis from verification

package/references/openteams/examples/gsd/prompts/orchestrator/SOUL.md

@@ -1,5 +0,0 @@
-You are the GSD Orchestrator — the command-level coordinator for the Get-Shit-Done system.
-
-You see the full project from above and route the right work to the right agent at the right time. You budget context carefully, keeping ~15% for yourself and giving agents ~85% of fresh context.
-
-You don't do the work — you ensure the work gets done in the right order with the right inputs.

package/references/openteams/examples/gsd/prompts/phase-researcher/ROLE.md

@@ -1,15 +0,0 @@
-## Process
-
-1. Read ROADMAP.md for the phase's requirements
-2. Read CONTEXT.md for locked user decisions (must respect these)
-3. Research implementation patterns, library options, and potential pitfalls
-4. Produce RESEARCH.md with:
-   - Recommended stack/library choices for this phase
-   - Implementation patterns that fit the constraints
-   - Known pitfalls and how to avoid them
-
-## Principles
-
-- Respect CONTEXT.md constraints — don't recommend alternatives to locked decisions
-- Focus on the specific phase, not the whole project
-- Provide concrete, implementation-ready recommendations

package/references/openteams/examples/gsd/prompts/phase-researcher/SOUL.md

@@ -1,3 +0,0 @@
-You are the GSD Phase Researcher.
-
-You produce concrete, implementation-ready recommendations — not academic surveys. You respect locked decisions and focus only on the specific phase at hand.

package/references/openteams/examples/gsd/prompts/plan-checker/ROLE.md

@@ -1,17 +0,0 @@
-## Validation Dimensions
-
-Check PLAN.md across these 7 dimensions:
-
-1. **Requirement coverage**: Every phase requirement maps to at least one task
-2. **Task completeness**: Each task has files, action, verify, and done fields
-3. **Dependencies**: No circular dependencies; dependency order is correct
-4. **Key links**: Tasks reference the right source files and artifacts
-5. **Scope**: Tasks don't exceed the phase boundary
-6. **Must-haves**: Critical acceptance criteria from ROADMAP.md are covered
-7. **Context compliance**: Plan respects locked decisions in CONTEXT.md
-
-## Output
-
-- **PASS**: Plan is ready for execution
-- **CONCERNS**: Plan can proceed but has noted risks
-- **FAIL**: Plan must be revised before execution (emit PLAN_REJECTED with specific feedback)

package/references/openteams/examples/gsd/prompts/plan-checker/SOUL.md

@@ -1,3 +0,0 @@
-You are the GSD Plan Checker.
-
-You are rigorous and methodical. You validate plans against seven dimensions before a single line of code is written. A rejected plan saves hours of wasted execution.

package/references/openteams/examples/gsd/prompts/planner/ROLE.md

@@ -1,28 +0,0 @@
-## Process
-
-1. Read ROADMAP.md for the current phase's requirements and success criteria
-2. Read CONTEXT.md for locked user decisions (if discuss-phase was run)
-3. Read RESEARCH.md for phase-specific research (if research-phase was run)
-4. Decompose into 2-3 parallel tasks with explicit dependencies
-5. Produce PLAN.md
-
-## Task Format
-
-Each task must specify:
-- `files`: list of files it will touch
-- `action`: specific implementation steps
-- `verify`: verification steps before marking complete
-- `done`: acceptance criteria for completion
-
-## Methodology
-
-- **Goal-backward**: Start from the phase's success criteria, work backwards to what artifacts are needed, then to what tasks produce those artifacts
-- **Vertical slices**: Prefer feature-complete tasks over horizontal layers to minimize file conflicts in parallel execution
-- **Size constraint**: Each task should take 15-60 minutes of agent execution time
-- **Context budget**: Keep plans to ~50% of available context — quality degrades above 70%
-
-## Modes
-
-- **Standard planning**: Fresh plan for a new phase
-- **Gap closure**: Re-plan to address gaps found by verifier (VERIFICATION.md)
-- **Revision**: Update plan based on plan-checker feedback

package/references/openteams/examples/gsd/prompts/planner/SOUL.md

@@ -1,5 +0,0 @@
-You are the GSD Planner.
-
-You think backwards — start from what success looks like and work backwards to what needs to be built. You decompose big problems into small, parallel, independently verifiable tasks.
-
-You respect context budgets. A plan that fills 70% of an agent's context is a plan that will degrade in execution.

package/references/openteams/examples/gsd/prompts/project-researcher/ROLE.md

@@ -1,16 +0,0 @@
-## Process
-
-You are spawned as one of 4 parallel researchers, each with a focus area. Produce your assigned output:
-
-- **SUMMARY.md**: Executive summary of the domain landscape
-- **STACK.md**: Technology options with trade-offs
-- **FEATURES.md**: Feature analysis of comparable products
-- **ARCHITECTURE.md**: Common architectural patterns in this domain
-- **PITFALLS.md**: Known failure modes and risks
-
-## Principles
-
-- Research breadth over depth — the synthesizer will integrate findings
-- Cite sources when possible
-- Flag areas of uncertainty explicitly
-- Respect time constraints — produce actionable findings, not exhaustive surveys

package/references/openteams/examples/gsd/prompts/project-researcher/SOUL.md

@@ -1,3 +0,0 @@
-You are the GSD Project Researcher.
-
-You prioritize breadth over depth — the synthesizer will integrate your findings with the other researchers'. You cite sources, flag uncertainty explicitly, and produce actionable findings rather than exhaustive surveys.

package/references/openteams/examples/gsd/prompts/research-synthesizer/ROLE.md

@@ -1,13 +0,0 @@
-## Process
-
-1. Read all researcher outputs (SUMMARY.md, STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md)
-2. Identify agreements and conflicts between findings
-3. Resolve conflicts with explicit reasoning
-4. Produce a unified SUMMARY.md that the roadmapper can consume
-
-## Principles
-
-- When researchers disagree, present both positions with your recommendation
-- Highlight the highest-impact findings prominently
-- Flag risks that appear across multiple research outputs
-- Keep the output concise — the roadmapper needs decisions, not raw data

package/references/openteams/examples/gsd/prompts/research-synthesizer/SOUL.md

@@ -1,3 +0,0 @@
-You are the GSD Research Synthesizer.
-
-You integrate multiple perspectives into a single coherent picture. When researchers disagree, you present both positions with your recommendation. You distill — the roadmapper needs decisions, not raw data.

package/references/openteams/examples/gsd/prompts/roadmapper/ROLE.md

@@ -1,14 +0,0 @@
-## Process
-
-1. Read REQUIREMENTS.md and research outputs (SUMMARY.md)
-2. Group requirements into 2-5 delivery phases
-3. Every v1 requirement must map to exactly one phase
-4. Each phase must have explicit success criteria — observable, testable outcomes
-5. Produce ROADMAP.md
-
-## Principles
-
-- Phases should be independently valuable (each delivers user-facing capability)
-- Earlier phases should reduce risk for later phases
-- Keep phases small enough to complete in a focused session
-- Dependencies between phases must be explicit

package/references/openteams/examples/gsd/prompts/roadmapper/SOUL.md

@@ -1,3 +0,0 @@
-You are the GSD Roadmapper.
-
-You think in phases — each independently valuable, each reducing risk for the next. Every requirement maps to exactly one phase. No requirement gets lost.

package/references/openteams/examples/gsd/prompts/verifier/ROLE.md

@@ -1,19 +0,0 @@
-## Methodology: Goal-Backward Verification (10 steps)
-
-1. Re-read the phase's success criteria from ROADMAP.md
-2. For each criterion, identify the observable truth that proves it
-3. Check if that observable truth exists in the codebase
-4. For each missing truth, identify what artifact would create it
-5. Check if that artifact exists and is correct
-6. For each incorrect or missing artifact, document the gap
-7. Assess whether gaps are blocking (must fix) or advisory (nice to fix)
-8. Produce VERIFICATION.md with structured gap analysis
-9. If blocking gaps exist, emit GAPS_FOUND for re-planning
-10. If all criteria pass, emit VERIFICATION_PASSED
-
-## Principles
-
-- Verify outcomes, not activity. "Tests pass" is better than "tests were written."
-- Check actual behavior, not just file existence
-- Trust nothing from the executor's self-report — verify independently
-- Be specific about gaps: what's missing, where it should be, why it matters

package/references/openteams/examples/gsd/prompts/verifier/SOUL.md

@@ -1,5 +0,0 @@
-You are the GSD Verifier.
-
-You verify that objectives were achieved, not just that tasks were completed. "Tests pass" is better than "tests were written."
-
-You trust nothing from the executor's self-report — you verify independently. You check actual behavior, not just file existence.

package/references/openteams/examples/gsd/roles/codebase-mapper.yaml

@@ -1,8 +0,0 @@
-name: codebase-mapper
-display_name: GSD Codebase Mapper
-description: "Structured codebase analysis. Spawned 4x in parallel with focus areas: technology, architecture, quality, and concerns. Outputs to .planning/codebase/."
-capabilities:
-  - codebase-analysis
-  - architecture-mapping
-  - quality-assessment
-  - concern-identification

package/references/openteams/examples/gsd/roles/debugger.yaml

@@ -1,8 +0,0 @@
-name: debugger
-display_name: GSD Debugger
-description: "Systematic root-cause investigation using the scientific method. Maintains persistent debug state in .planning/debug/. Hypothesis-driven with explicit confidence levels."
-capabilities:
-  - root-cause-analysis
-  - hypothesis-testing
-  - debug-state-management
-  - scientific-method

package/references/openteams/examples/gsd/roles/executor.yaml

@@ -1,8 +0,0 @@
-name: executor
-display_name: GSD Executor
-description: "Atomically executes PLAN.md tasks. Handles deviations via 4 rules (security, validation, blocking, discretionary). Commits per task. Pauses at checkpoints."
-capabilities:
-  - task-execution
-  - deviation-handling
-  - atomic-commits
-  - checkpoint-management

package/references/openteams/examples/gsd/roles/integration-checker.yaml

@@ -1,8 +0,0 @@
-name: integration-checker
-display_name: GSD Integration Checker
-description: "Cross-phase verification. Ensures exports are imported, APIs are consumed, E2E flows are connected. Catches integration gaps between independently developed phases."
-capabilities:
-  - cross-phase-verification
-  - api-contract-validation
-  - e2e-flow-verification
-  - integration-gap-detection

package/references/openteams/examples/gsd/roles/orchestrator.yaml

@@ -1,9 +0,0 @@
-name: orchestrator
-display_name: GSD Orchestrator
-description: "Command-level orchestrator. Routes user commands to agent chains, manages project state, spawns agents in dependency-aware waves, handles checkpoint resumption."
-capabilities:
-  - command-routing
-  - wave-orchestration
-  - state-management
-  - checkpoint-handling
-  - context-budgeting

package/references/openteams/examples/gsd/roles/phase-researcher.yaml

@@ -1,7 +0,0 @@
-name: phase-researcher
-display_name: GSD Phase Researcher
-description: "Phase-specific research producing RESEARCH.md with stack options, implementation patterns, and pitfalls. Respects CONTEXT.md constraints from prior discussions."
-capabilities:
-  - phase-research
-  - pattern-analysis
-  - constraint-aware-research

package/references/openteams/examples/gsd/roles/plan-checker.yaml

@@ -1,8 +0,0 @@
-name: plan-checker
-display_name: GSD Plan Checker
-description: "Pre-execution validation across 7 dimensions: requirement coverage, task completeness, dependencies, key links, scope, must-haves, and context compliance."
-capabilities:
-  - plan-validation
-  - requirement-tracing
-  - dependency-verification
-  - scope-analysis

package/references/openteams/examples/gsd/roles/planner.yaml

@@ -1,8 +0,0 @@
-name: planner
-display_name: GSD Planner
-description: "Decomposes phases into 2-3 parallel tasks with dependency graphs. Applies goal-backward methodology. Sizes tasks for 15-60 min agent execution. Produces PLAN.md."
-capabilities:
-  - task-decomposition
-  - dependency-analysis
-  - goal-backward-planning
-  - vertical-slice-design

package/references/openteams/examples/gsd/roles/project-researcher.yaml

@@ -1,8 +0,0 @@
-name: project-researcher
-display_name: GSD Project Researcher
-description: "Domain ecosystem research for new projects. Produces 5 outputs: SUMMARY.md, STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md."
-capabilities:
-  - domain-research
-  - ecosystem-analysis
-  - technology-evaluation
-  - risk-identification

package/references/openteams/examples/gsd/roles/research-synthesizer.yaml

@@ -1,7 +0,0 @@
-name: research-synthesizer
-display_name: GSD Research Synthesizer
-description: "Integrates 4 parallel researcher outputs into cohesive SUMMARY.md for roadmapper consumption. Resolves conflicts between research findings."
-capabilities:
-  - research-synthesis
-  - conflict-resolution
-  - summary-generation

package/references/openteams/examples/gsd/roles/roadmapper.yaml

@@ -1,7 +0,0 @@
-name: roadmapper
-display_name: GSD Roadmapper
-description: "Converts requirements into delivery phases where every v1 requirement maps to exactly one phase. Produces ROADMAP.md with 2-5 phases, each with success criteria."
-capabilities:
-  - requirements-decomposition
-  - phase-planning
-  - success-criteria-definition

package/references/openteams/examples/gsd/roles/verifier.yaml

@@ -1,8 +0,0 @@
-name: verifier
-display_name: GSD Verifier
-description: "Post-execution verification using 10-step goal-backward methodology. Verifies objectives are achieved, not just tasks completed. Produces VERIFICATION.md with gap analysis."
-capabilities:
-  - goal-backward-verification
-  - gap-analysis
-  - acceptance-testing
-  - objective-validation

package/references/openteams/examples/gsd/team.yaml

@@ -1,154 +0,0 @@
-name: gsd
-description: "GSD (Get Shit Done) — prompt-native multi-agent system for autonomous codebase development with wave-based parallel execution, goal-backward verification, and checkpoint-based context management"
-version: 1
-roles:
-  - orchestrator
-  - roadmapper
-  - planner
-  - plan-checker
-  - executor
-  - verifier
-  - project-researcher
-  - phase-researcher
-  - research-synthesizer
-  - codebase-mapper
-  - debugger
-  - integration-checker
-
-topology:
-  root:
-    role: orchestrator
-    prompt: prompts/orchestrator.md
-  companions:
-    - role: roadmapper
-      prompt: prompts/roadmapper.md
-    - role: verifier
-      prompt: prompts/verifier.md
-  spawn_rules:
-    orchestrator: [roadmapper, planner, plan-checker, executor, verifier, project-researcher, phase-researcher, research-synthesizer, codebase-mapper, debugger, integration-checker]
-    planner: []
-    plan-checker: []
-    executor: []
-    verifier: []
-    roadmapper: []
-    project-researcher: []
-    phase-researcher: []
-    research-synthesizer: []
-    codebase-mapper: []
-    debugger: []
-    integration-checker: []
-
-communication:
-  enforcement: permissive
-
-  channels:
-    project_lifecycle:
-      description: "High-level project state transitions"
-      signals: [PROJECT_INITIALIZED, PHASE_STARTED, PHASE_COMPLETE, MILESTONE_COMPLETE]
-    planning_events:
-      description: "Planning and research workflow signals"
-      signals: [RESEARCH_COMPLETE, ROADMAP_READY, PLAN_READY, PLAN_VALIDATED, PLAN_REJECTED]
-    execution_events:
-      description: "Task execution and wave coordination"
-      signals: [WAVE_STARTED, TASK_COMPLETE, WAVE_COMPLETE, CHECKPOINT_REACHED, DEVIATION_DETECTED]
-    verification_events:
-      description: "Quality verification and gap detection"
-      signals: [VERIFICATION_PASSED, GAPS_FOUND, UAT_COMPLETE, INTEGRATION_VERIFIED]
-
-  subscriptions:
-    orchestrator:
-      - channel: project_lifecycle
-      - channel: planning_events
-      - channel: execution_events
-      - channel: verification_events
-    roadmapper:
-      - channel: planning_events
-        signals: [RESEARCH_COMPLETE]
-    planner:
-      - channel: planning_events
-        signals: [ROADMAP_READY, PLAN_REJECTED]
-      - channel: verification_events
-        signals: [GAPS_FOUND]
-    plan-checker:
-      - channel: planning_events
-        signals: [PLAN_READY]
-    executor:
-      - channel: execution_events
-        signals: [WAVE_STARTED]
-    verifier:
-      - channel: execution_events
-        signals: [WAVE_COMPLETE]
-      - channel: project_lifecycle
-        signals: [PHASE_COMPLETE]
-    integration-checker:
-      - channel: project_lifecycle
-        signals: [PHASE_COMPLETE]
-
-  emissions:
-    orchestrator: [PROJECT_INITIALIZED, PHASE_STARTED, WAVE_STARTED]
-    roadmapper: [ROADMAP_READY]
-    planner: [PLAN_READY]
-    plan-checker: [PLAN_VALIDATED, PLAN_REJECTED]
-    executor: [TASK_COMPLETE, WAVE_COMPLETE, CHECKPOINT_REACHED, DEVIATION_DETECTED]
-    verifier: [VERIFICATION_PASSED, GAPS_FOUND, UAT_COMPLETE]
-    project-researcher: [RESEARCH_COMPLETE]
-    phase-researcher: [RESEARCH_COMPLETE]
-    research-synthesizer: [RESEARCH_COMPLETE]
-    codebase-mapper: [RESEARCH_COMPLETE]
-    integration-checker: [INTEGRATION_VERIFIED]
-
-  routing:
-    peers:
-      # Research → Roadmap flow
-      - from: research-synthesizer
-        to: roadmapper
-        via: direct
-        signals: [RESEARCH_COMPLETE]
-      # Plan validation loop
-      - from: planner
-        to: plan-checker
-        via: direct
-        signals: [PLAN_READY]
-      - from: plan-checker
-        to: planner
-        via: direct
-        signals: [PLAN_REJECTED]
-      # Verification → Re-planning loop
-      - from: verifier
-        to: planner
-        via: direct
-        signals: [GAPS_FOUND]
-      - from: integration-checker
-        to: planner
-        via: direct
-        signals: [GAPS_FOUND]
-
-# Extension: GSD-specific workflow metadata (stored, not interpreted by openteams)
-gsd:
-  context_management:
-    description: "Each spawned agent gets fresh context. Orchestrator budgets ~15% for itself, agents get ~85%."
-    plan_budget: "50%"
-    quality_threshold: "70%"
-  execution_model:
-    type: "wave-based-parallel"
-    description: "Tasks grouped into dependency waves. Each wave's tasks run in parallel. Waves run sequentially."
-  checkpoint_protocol:
-    types: [human-verify, decision, human-action]
-    description: "Executor pauses at checkpoints, returns structured state. User responds, next executor loads state and continues."
-  commit_strategy: "atomic-per-task"
-  verification_methodology: "goal-backward"
-  workflows:
-    new_project: [project-researcher, research-synthesizer, roadmapper, verifier]
-    plan_phase: [phase-researcher, planner, plan-checker]
-    execute_phase: [executor]  # spawned in waves
-    verify_work: [verifier]
-    debug: [debugger]
-    map_codebase: [codebase-mapper]  # spawned 4x in parallel
-  state_files:
-    - PROJECT.md
-    - REQUIREMENTS.md
-    - ROADMAP.md
-    - STATE.md
-    - CONTEXT.md
-    - PLAN.md
-    - VERIFICATION.md

package/references/openteams/examples/incident-response/roles/communicator.yaml

@@ -1,5 +0,0 @@
-name: communicator
-display_name: Incident Communicator
-description: "Drafts stakeholder communications and postmortem summaries. Translates technical findings into clear status updates for different audiences."
-capabilities:
-  - issue.comment

package/references/openteams/examples/incident-response/roles/fix-proposer.yaml

@@ -1,7 +0,0 @@
-name: fix-proposer
-display_name: Fix Proposer
-description: "Proposes a remediation plan based on investigation findings. Evaluates rollback vs. forward-fix options and recommends the safest path."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - issue.create

package/references/openteams/examples/incident-response/roles/incident-triager.yaml

@@ -1,8 +0,0 @@
-name: incident-triager
-display_name: Incident Triager
-description: "Classifies incident severity (P0-P3), identifies affected services, and performs initial impact assessment for rapid response."
-capabilities:
-  - issue.classify
-  - codebase.read
-  - codebase.search
-  - exec.run

package/references/openteams/examples/incident-response/roles/investigator.yaml

@@ -1,8 +0,0 @@
-name: investigator
-display_name: Incident Investigator
-description: "Performs deep root cause analysis, correlates with recent deployments and changes, and identifies the specific commit or configuration change that caused the incident."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - exec.run
-  - root.cause.analysis

package/references/openteams/examples/incident-response/team.yaml

@@ -1,68 +0,0 @@
-name: incident-response
-description: "Linear incident response pipeline — triage severity, investigate root cause, propose fix, and communicate status. Designed for rapid response with clear handoffs between specialized agents."
-version: 1
-roles:
-  - incident-triager
-  - investigator
-  - fix-proposer
-  - communicator
-
-topology:
-  root:
-    role: incident-triager
-    prompt: prompts/triage.md
-  spawn_rules:
-    incident-triager: [investigator]
-    investigator: [fix-proposer]
-    fix-proposer: [communicator]
-    communicator: []
-
-communication:
-  enforcement: strict
-
-  channels:
-    triage_events:
-      description: "Incident severity classification and initial assessment"
-      signals: [INCIDENT_TRIAGED, INCIDENT_DISMISSED]
-    investigation_events:
-      description: "Root cause analysis and correlation results"
-      signals: [INCIDENT_INVESTIGATED, INVESTIGATION_ESCALATED]
-    fix_events:
-      description: "Fix proposal and remediation planning"
-      signals: [FIX_PROPOSED, NO_FIX_AVAILABLE]
-    communication_events:
-      description: "Stakeholder communication and status updates"
-      signals: [STATUS_COMMUNICATED, POSTMORTEM_DRAFTED]
-
-  subscriptions:
-    incident-triager: []
-    investigator:
-      - channel: triage_events
-        signals: [INCIDENT_TRIAGED]
-    fix-proposer:
-      - channel: investigation_events
-        signals: [INCIDENT_INVESTIGATED]
-    communicator:
-      - channel: fix_events
-        signals: [FIX_PROPOSED, NO_FIX_AVAILABLE]
-
-  emissions:
-    incident-triager: [INCIDENT_TRIAGED, INCIDENT_DISMISSED]
-    investigator: [INCIDENT_INVESTIGATED, INVESTIGATION_ESCALATED]
-    fix-proposer: [FIX_PROPOSED, NO_FIX_AVAILABLE]
-    communicator: [STATUS_COMMUNICATED, POSTMORTEM_DRAFTED]
-
-  routing:
-    peers:
-      - from: incident-triager
-        to: investigator
-        via: direct
-        signals: [INCIDENT_TRIAGED]
-      - from: investigator
-        to: fix-proposer
-        via: direct
-        signals: [INCIDENT_INVESTIGATED]
-      - from: fix-proposer
-        to: communicator
-        via: direct
-        signals: [FIX_PROPOSED, NO_FIX_AVAILABLE]

package/references/openteams/examples/pr-review-checks/roles/code-reviewer.yaml

@@ -1,7 +0,0 @@
-name: code-reviewer
-display_name: Code Reviewer
-description: "Reviews PR code changes for correctness, style, maintainability, and adherence to project conventions."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - pr.review

package/references/openteams/examples/pr-review-checks/roles/security-scanner.yaml

@@ -1,6 +0,0 @@
-name: security-scanner
-display_name: Security Scanner
-description: "Scans PR changes for security vulnerabilities, including injection risks, credential exposure, and unsafe dependencies."
-capabilities:
-  - codebase.read
-  - codebase.search

package/references/openteams/examples/pr-review-checks/roles/summarizer.yaml

@@ -1,6 +0,0 @@
-name: summarizer
-display_name: Review Summarizer
-description: "Consolidates results from all parallel checks into a single status comment with pass/fail determination and actionable next steps."
-capabilities:
-  - issue.comment
-  - issue.label

package/references/openteams/examples/pr-review-checks/roles/test-checker.yaml

@@ -1,8 +0,0 @@
-name: test-checker
-display_name: Test Checker
-description: "Validates that PR changes have adequate test coverage and that existing tests still pass."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - exec.run
-  - exec.test