claude-code-swarm 0.3.2 → 0.3.4

package/references/openteams/examples/bmad-method/team.yaml

@@ -1,161 +0,0 @@
-name: bmad-method
-description: "BMAD Method — full agile development team with 10 specialized agents across 4 phases (analysis, planning, solutioning, implementation) plus a quick-flow lane"
-version: 1
-roles:
-  - master
-  - analyst
-  - pm
-  - ux-designer
-  - architect
-  - scrum-master
-  - developer
-  - qa
-  - tech-writer
-  - quick-flow-dev
-
-topology:
-  root:
-    role: master
-    prompt: prompts/master.md
-  companions:
-    - role: analyst
-      prompt: prompts/analyst.md
-    - role: pm
-      prompt: prompts/pm.md
-    - role: ux-designer
-      prompt: prompts/ux-designer.md
-    - role: architect
-      prompt: prompts/architect.md
-    - role: scrum-master
-      prompt: prompts/scrum-master.md
-  spawn_rules:
-    master: [analyst, pm, ux-designer, architect, scrum-master, developer, qa, tech-writer, quick-flow-dev]
-    scrum-master: [developer, qa, tech-writer]
-    pm: [ux-designer]
-    analyst: []
-    ux-designer: []
-    architect: []
-    developer: []
-    qa: []
-    tech-writer: []
-    quick-flow-dev: []
-
-communication:
-  enforcement: audit
-
-  channels:
-    phase_transitions:
-      description: "Signals when a development phase completes and the next can begin"
-      signals: [ANALYSIS_COMPLETE, PLANNING_COMPLETE, SOLUTIONING_COMPLETE, IMPLEMENTATION_COMPLETE]
-    artifact_ready:
-      description: "Signals when a key artifact is produced and available for downstream consumers"
-      signals: [BRIEF_READY, PRD_READY, UX_SPEC_READY, ARCHITECTURE_READY, STORIES_READY, READINESS_GATE_PASSED]
-    sprint_events:
-      description: "Sprint lifecycle events during implementation phase"
-      signals: [SPRINT_STARTED, STORY_READY, STORY_COMPLETE, REVIEW_PASSED, REVIEW_FAILED, SPRINT_COMPLETE]
-    quality_events:
-      description: "Quality gates and test results"
-      signals: [TESTS_PASSED, TESTS_FAILED, DOCS_UPDATED]
-
-  subscriptions:
-    master:
-      - channel: phase_transitions
-      - channel: artifact_ready
-      - channel: sprint_events
-      - channel: quality_events
-    pm:
-      - channel: phase_transitions
-        signals: [ANALYSIS_COMPLETE]
-      - channel: artifact_ready
-        signals: [BRIEF_READY]
-    ux-designer:
-      - channel: artifact_ready
-        signals: [PRD_READY]
-    architect:
-      - channel: artifact_ready
-        signals: [PRD_READY, UX_SPEC_READY]
-    scrum-master:
-      - channel: artifact_ready
-        signals: [ARCHITECTURE_READY, STORIES_READY, READINESS_GATE_PASSED]
-      - channel: sprint_events
-      - channel: quality_events
-    developer:
-      - channel: sprint_events
-        signals: [STORY_READY, REVIEW_FAILED]
-    qa:
-      - channel: sprint_events
-        signals: [STORY_COMPLETE]
-    tech-writer:
-      - channel: artifact_ready
-      - channel: sprint_events
-        signals: [STORY_COMPLETE, SPRINT_COMPLETE]
-
-  emissions:
-    analyst: [ANALYSIS_COMPLETE, BRIEF_READY]
-    pm: [PLANNING_COMPLETE, PRD_READY, STORIES_READY, READINESS_GATE_PASSED]
-    ux-designer: [UX_SPEC_READY]
-    architect: [SOLUTIONING_COMPLETE, ARCHITECTURE_READY]
-    scrum-master: [SPRINT_STARTED, STORY_READY, SPRINT_COMPLETE]
-    developer: [STORY_COMPLETE]
-    qa: [TESTS_PASSED, TESTS_FAILED]
-    tech-writer: [DOCS_UPDATED]
-    quick-flow-dev: [STORY_COMPLETE]
-
-  routing:
-    peers:
-      # Phase handoffs
-      - from: analyst
-        to: pm
-        via: direct
-        signals: [BRIEF_READY]
-      - from: pm
-        to: architect
-        via: direct
-        signals: [PRD_READY]
-      - from: ux-designer
-        to: architect
-        via: direct
-        signals: [UX_SPEC_READY]
-      # Implementation coordination
-      - from: scrum-master
-        to: developer
-        via: direct
-        signals: [STORY_READY]
-      - from: developer
-        to: scrum-master
-        via: direct
-        signals: [STORY_COMPLETE]
-      - from: developer
-        to: qa
-        via: direct
-      # Review loop
-      - from: architect
-        to: developer
-        via: direct
-        signals: [REVIEW_PASSED, REVIEW_FAILED]
-
-# Extension: BMAD-specific workflow metadata (stored, not interpreted by openteams)
-bmad:
-  phases:
-    analysis:
-      lead: analyst
-      optional: true
-      workflows: [brainstorm-project, market-research, domain-research, technical-research, create-product-brief]
-    planning:
-      lead: pm
-      parallel: [ux-designer]
-      workflows: [create-prd, validate-prd, create-ux-design]
-    solutioning:
-      lead: architect
-      workflows: [create-architecture, create-epics-and-stories, implementation-readiness]
-    implementation:
-      orchestrator: scrum-master
-      executors: [developer, qa, tech-writer]
-      workflows: [sprint-planning, create-story, dev-story, code-review, automate-tests]
-  quick_flow:
-    agent: quick-flow-dev
-    parallel_to_all: true
-    workflows: [quick-spec, quick-dev, code-review]
-  party_mode:
-    orchestrator: master
-    description: "Multi-agent collaborative discussion for big decisions, brainstorming, and retrospectives"

package/references/openteams/examples/bug-fix-pipeline/roles/fixer.yaml

@@ -1,9 +0,0 @@
-name: fixer
-display_name: Bug Fixer
-description: "Applies targeted code fixes based on investigation findings. Writes minimal, focused changes and runs tests to confirm the fix."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - file.write
-  - exec.run
-  - exec.test

package/references/openteams/examples/bug-fix-pipeline/roles/investigator.yaml

@@ -1,8 +0,0 @@
-name: investigator
-display_name: Bug Investigator
-description: "Performs root cause analysis on triaged bugs. Traces control flow, identifies the failing code path, and documents findings for the fixer."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - exec.run
-  - root.cause.analysis

package/references/openteams/examples/bug-fix-pipeline/roles/pr-creator.yaml

@@ -1,6 +0,0 @@
-name: pr-creator
-display_name: PR Creator
-description: "Creates a pull request with a structured summary of the bug, root cause, fix applied, and verification results."
-capabilities:
-  - pr.create
-  - issue.comment

package/references/openteams/examples/bug-fix-pipeline/roles/triager.yaml

@@ -1,7 +0,0 @@
-name: triager
-display_name: Bug Triager
-description: "Classifies incoming bug reports by severity, identifies affected areas, and determines if the issue is actionable for automated fixing."
-capabilities:
-  - issue.classify
-  - codebase.read
-  - codebase.search

package/references/openteams/examples/bug-fix-pipeline/roles/verifier.yaml

@@ -1,8 +0,0 @@
-name: verifier
-display_name: Fix Verifier
-description: "Independently verifies that the fix resolves the original bug without introducing regressions. Cannot modify code — read-only verification."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - exec.run
-  - exec.test

package/references/openteams/examples/bug-fix-pipeline/team.yaml

@@ -1,88 +0,0 @@
-name: bug-fix-pipeline
-description: "Linear pipeline for autonomous bug fixing — triage, investigate, fix, verify, and create PR. Each phase is handled by a specialized agent with peer verification before PR creation."
-version: 1
-roles:
-  - triager
-  - investigator
-  - fixer
-  - verifier
-  - pr-creator
-
-topology:
-  root:
-    role: triager
-    prompt: prompts/triage.md
-  spawn_rules:
-    triager: [investigator]
-    investigator: [fixer]
-    fixer: [verifier]
-    verifier: [pr-creator]
-    pr-creator: []
-
-communication:
-  enforcement: strict
-
-  channels:
-    triage_events:
-      description: "Bug classification and severity assessment"
-      signals: [BUG_TRIAGED, BUG_REJECTED]
-    investigation_events:
-      description: "Root cause analysis results"
-      signals: [BUG_INVESTIGATED, INVESTIGATION_BLOCKED]
-    fix_events:
-      description: "Code fix lifecycle"
-      signals: [FIX_APPLIED, FIX_FAILED]
-    verification_events:
-      description: "Post-fix verification results"
-      signals: [FIX_VERIFIED, FIX_NEEDS_REWORK]
-    pr_events:
-      description: "Pull request creation"
-      signals: [PR_CREATED]
-
-  subscriptions:
-    triager:
-      - channel: verification_events
-        signals: [FIX_NEEDS_REWORK]
-    investigator:
-      - channel: triage_events
-        signals: [BUG_TRIAGED]
-    fixer:
-      - channel: investigation_events
-        signals: [BUG_INVESTIGATED]
-    verifier:
-      - channel: fix_events
-        signals: [FIX_APPLIED]
-    pr-creator:
-      - channel: verification_events
-        signals: [FIX_VERIFIED]
-
-  emissions:
-    triager: [BUG_TRIAGED, BUG_REJECTED]
-    investigator: [BUG_INVESTIGATED, INVESTIGATION_BLOCKED]
-    fixer: [FIX_APPLIED, FIX_FAILED]
-    verifier: [FIX_VERIFIED, FIX_NEEDS_REWORK]
-    pr-creator: [PR_CREATED]
-
-  routing:
-    peers:
-      - from: triager
-        to: investigator
-        via: direct
-        signals: [BUG_TRIAGED]
-      - from: investigator
-        to: fixer
-        via: direct
-        signals: [BUG_INVESTIGATED]
-      - from: fixer
-        to: verifier
-        via: direct
-        signals: [FIX_APPLIED]
-      - from: verifier
-        to: pr-creator
-        via: direct
-        signals: [FIX_VERIFIED]
-      # Rework loop
-      - from: verifier
-        to: triager
-        via: direct
-        signals: [FIX_NEEDS_REWORK]

package/references/openteams/examples/codebase-migration/roles/assessor.yaml

@@ -1,7 +0,0 @@
-name: assessor
-display_name: Migration Assessor
-description: "Evaluates migration scope, identifies affected files and modules, estimates risk, and determines if automated migration is feasible."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - exec.run

package/references/openteams/examples/codebase-migration/roles/migrator.yaml

@@ -1,9 +0,0 @@
-name: migrator
-display_name: Code Migrator
-description: "Applies the migration plan — refactors code, updates APIs, modifies configurations. Runs characterization tests after each change to ensure behavioral preservation."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - file.write
-  - exec.run
-  - exec.test

package/references/openteams/examples/codebase-migration/roles/planner.yaml

@@ -1,5 +0,0 @@
-name: planner
-display_name: Migration Planner
-description: "Creates a phased migration strategy with rollback points. Determines ordering constraints and identifies which changes can be parallelized."
-capabilities:
-  - issue.comment

package/references/openteams/examples/codebase-migration/roles/test-extractor.yaml

@@ -1,9 +0,0 @@
-name: test-extractor
-display_name: Test Extractor
-description: "Writes characterization tests that capture current behavior before migration. These tests serve as a safety net to detect behavioral regressions."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - file.write
-  - exec.run
-  - exec.test

package/references/openteams/examples/codebase-migration/roles/validator.yaml

@@ -1,7 +0,0 @@
-name: validator
-display_name: Migration Validator
-description: "Runs the full test suite and characterization tests to confirm the migration preserves all existing behavior. Read-only verification."
-capabilities:
-  - codebase.read
-  - exec.run
-  - exec.test

package/references/openteams/examples/codebase-migration/team.yaml

@@ -1,81 +0,0 @@
-name: codebase-migration
-description: "Linear migration pipeline with test-first safety net — assess scope, plan strategy, extract characterization tests, apply migration, then validate. Tests are written before migration to ensure behavioral preservation."
-version: 1
-roles:
-  - assessor
-  - planner
-  - test-extractor
-  - migrator
-  - validator
-
-topology:
-  root:
-    role: assessor
-    prompt: prompts/assess.md
-  spawn_rules:
-    assessor: [planner]
-    planner: [test-extractor]
-    test-extractor: [migrator]
-    migrator: [validator]
-    validator: []
-
-communication:
-  enforcement: strict
-
-  channels:
-    assessment_events:
-      description: "Migration scope and impact analysis"
-      signals: [MIGRATION_ASSESSED, MIGRATION_TOO_RISKY]
-    planning_events:
-      description: "Migration strategy and phasing"
-      signals: [MIGRATION_PLANNED]
-    testing_events:
-      description: "Characterization test extraction before migration"
-      signals: [TESTS_READY, TEST_EXTRACTION_FAILED]
-    migration_events:
-      description: "Migration application lifecycle"
-      signals: [MIGRATION_APPLIED, MIGRATION_FAILED]
-    validation_events:
-      description: "Post-migration verification"
-      signals: [MIGRATION_VERIFIED, MIGRATION_NEEDS_REWORK]
-
-  subscriptions:
-    assessor: []
-    planner:
-      - channel: assessment_events
-        signals: [MIGRATION_ASSESSED]
-    test-extractor:
-      - channel: planning_events
-        signals: [MIGRATION_PLANNED]
-    migrator:
-      - channel: testing_events
-        signals: [TESTS_READY]
-    validator:
-      - channel: migration_events
-        signals: [MIGRATION_APPLIED]
-
-  emissions:
-    assessor: [MIGRATION_ASSESSED, MIGRATION_TOO_RISKY]
-    planner: [MIGRATION_PLANNED]
-    test-extractor: [TESTS_READY, TEST_EXTRACTION_FAILED]
-    migrator: [MIGRATION_APPLIED, MIGRATION_FAILED]
-    validator: [MIGRATION_VERIFIED, MIGRATION_NEEDS_REWORK]
-
-  routing:
-    peers:
-      - from: assessor
-        to: planner
-        via: direct
-        signals: [MIGRATION_ASSESSED]
-      - from: planner
-        to: test-extractor
-        via: direct
-        signals: [MIGRATION_PLANNED]
-      - from: test-extractor
-        to: migrator
-        via: direct
-        signals: [TESTS_READY]
-      - from: migrator
-        to: validator
-        via: direct
-        signals: [MIGRATION_APPLIED]

package/references/openteams/examples/docs-sync/roles/adr-writer.yaml

@@ -1,7 +0,0 @@
-name: adr-writer
-display_name: ADR Writer
-description: "Drafts Architecture Decision Records for significant architectural changes. Only triggered when architectural changes are detected."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - file.write

package/references/openteams/examples/docs-sync/roles/api-doc-writer.yaml

@@ -1,7 +0,0 @@
-name: api-doc-writer
-display_name: API Doc Writer
-description: "Updates API documentation, OpenAPI specs, and reference docs to reflect code changes."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - file.write

package/references/openteams/examples/docs-sync/roles/change-detector.yaml

@@ -1,7 +0,0 @@
-name: change-detector
-display_name: Change Detector
-description: "Analyzes merged code changes to classify what documentation needs updating — API surface changes, behavior changes, and architectural changes."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - exec.run

package/references/openteams/examples/docs-sync/roles/doc-reviewer.yaml

@@ -1,7 +0,0 @@
-name: doc-reviewer
-display_name: Doc Reviewer
-description: "Reviews documentation updates for accuracy, completeness, and consistency with the codebase."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - pr.review

package/references/openteams/examples/docs-sync/roles/guide-writer.yaml

@@ -1,7 +0,0 @@
-name: guide-writer
-display_name: Guide Writer
-description: "Updates user guides, tutorials, and README files to reflect behavioral changes in the codebase."
-capabilities:
-  - codebase.read
-  - codebase.search
-  - file.write

package/references/openteams/examples/docs-sync/team.yaml

@@ -1,84 +0,0 @@
-name: docs-sync
-description: "Fan-out/fan-in documentation pipeline — detects code changes, then dispatches parallel doc writers (API docs, guides, and conditionally ADRs for architectural changes). A reviewer consolidates the results."
-version: 1
-roles:
-  - change-detector
-  - api-doc-writer
-  - guide-writer
-  - adr-writer
-  - doc-reviewer
-
-topology:
-  root:
-    role: change-detector
-    prompt: prompts/detect.md
-  companions:
-    - role: doc-reviewer
-      prompt: prompts/review.md
-  spawn_rules:
-    change-detector: [api-doc-writer, guide-writer, adr-writer]
-    api-doc-writer: []
-    guide-writer: []
-    adr-writer: []
-    doc-reviewer: []
-
-communication:
-  enforcement: audit
-
-  channels:
-    detection_events:
-      description: "Change detection and classification"
-      signals: [CHANGES_DETECTED, NO_DOC_CHANGES_NEEDED]
-    doc_updates:
-      description: "Individual doc writer completions — reviewer waits for API and guide updates"
-      signals: [API_DOCS_UPDATED, GUIDES_UPDATED, ADR_DRAFTED]
-    review_events:
-      description: "Documentation review outcome"
-      signals: [DOCS_APPROVED, DOCS_NEED_REVISION]
-
-  subscriptions:
-    change-detector: []
-    api-doc-writer:
-      - channel: detection_events
-        signals: [CHANGES_DETECTED]
-    guide-writer:
-      - channel: detection_events
-        signals: [CHANGES_DETECTED]
-    adr-writer:
-      - channel: detection_events
-        signals: [CHANGES_DETECTED]
-    doc-reviewer:
-      - channel: doc_updates
-        signals: [API_DOCS_UPDATED, GUIDES_UPDATED]
-
-  emissions:
-    change-detector: [CHANGES_DETECTED, NO_DOC_CHANGES_NEEDED]
-    api-doc-writer: [API_DOCS_UPDATED]
-    guide-writer: [GUIDES_UPDATED]
-    adr-writer: [ADR_DRAFTED]
-    doc-reviewer: [DOCS_APPROVED, DOCS_NEED_REVISION]
-
-  routing:
-    peers:
-      # Fan-out: detector → doc writers
-      - from: change-detector
-        to: api-doc-writer
-        via: direct
-        signals: [CHANGES_DETECTED]
-      - from: change-detector
-        to: guide-writer
-        via: direct
-        signals: [CHANGES_DETECTED]
-      - from: change-detector
-        to: adr-writer
-        via: direct
-        signals: [CHANGES_DETECTED]
-      # Fan-in: doc writers → reviewer
-      - from: api-doc-writer
-        to: doc-reviewer
-        via: direct
-        signals: [API_DOCS_UPDATED]
-      - from: guide-writer
-        to: doc-reviewer
-        via: direct
-        signals: [GUIDES_UPDATED]

package/references/openteams/examples/gsd/prompts/codebase-mapper/ROLE.md

@@ -1,17 +0,0 @@
-## Process
-
-You are spawned as one of 4 parallel mappers. Each analyzes the codebase from a different angle:
-
-- **Technology**: Languages, frameworks, build tools, dependencies
-- **Architecture**: Module structure, data flow, API boundaries, patterns used
-- **Quality**: Test coverage, code style consistency, technical debt indicators
-- **Concerns**: Security issues, performance risks, maintenance burdens
-
-Output to `.planning/codebase/` with your focus area's findings.
-
-## Principles
-
-- Map what IS, not what should be
-- Be specific: file paths, line counts, dependency versions
-- Flag surprises — anything unexpected about the codebase
-- Keep findings structured and scannable

package/references/openteams/examples/gsd/prompts/codebase-mapper/SOUL.md

@@ -1,5 +0,0 @@
-You are the GSD Codebase Mapper.
-
-You map what IS, not what should be. You are an objective observer — specific, structured, and factual. File paths, line counts, dependency versions.
-
-You flag surprises. Anything unexpected about the codebase deserves a callout.

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

@@ -1,25 +0,0 @@
-## Methodology: Scientific Method
-
-1. **Observe**: Gather symptoms, error messages, reproduction steps
-2. **Hypothesize**: Form a ranked list of possible causes with confidence levels
-3. **Test**: Design minimal experiments to confirm or eliminate each hypothesis
-4. **Analyze**: Update confidence levels based on results
-5. **Conclude**: Identify root cause with evidence
-6. **Fix**: Implement the fix with a test that prevents regression
-
-## State Management
-
-Maintain persistent debug state in `.planning/debug/`:
-- Current hypotheses with confidence levels
-- Experiments run and their results
-- Eliminated causes
-- Current best theory
-
-This state survives context resets — each debug session picks up where the last left off.
-
-## Principles
-
-- Never guess. Test hypotheses systematically.
-- Update confidence levels honestly — a failed experiment is valuable data
-- The fix must include a regression test
-- Document the root cause for future reference

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

@@ -1,5 +0,0 @@
-You are the GSD Debugger.
-
-You never guess. You apply the scientific method — hypothesize, test, update confidence, repeat. A failed experiment is valuable data, not a failure.
-
-You are patient and systematic. You'd rather run five targeted experiments than make one lucky guess.

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

@@ -1,34 +0,0 @@
-## Process
-
-1. Read your assigned task from PLAN.md
-2. Execute the action steps in order
-3. Run verification steps after each action
-4. Commit atomically when the task is complete
-5. Produce a SUMMARY.md of what was done
-
-## Deviation Rules
-
-When you encounter something unexpected during execution:
-
-- **Rule 1 (Security)**: Auto-fix security vulnerabilities immediately. No permission needed.
-- **Rule 2 (Validation)**: Auto-fix validation and type errors. No permission needed.
-- **Rule 3 (Blocking)**: If blocked by a missing dependency or broken assumption, pause and report to orchestrator via checkpoint.
-- **Rule 4 (Discretionary)**: For style, optimization, or non-critical improvements — skip. Stay on task.
-
-## Checkpoint Protocol
-
-When you encounter a `human-verify`, `decision`, or `human-action` marker:
-
-1. Stop execution
-2. Record completed tasks with commit hashes
-3. Record the exact continuation point
-4. Return structured checkpoint state to orchestrator
-5. Wait for human response before continuing
-
-## Commit Format
-
-```
-{type}({phase}-{plan}): description
-```
-
-One commit per completed task. Clean history enables individual task reversibility.

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

@@ -1,5 +0,0 @@
-You are the GSD Executor.
-
-Disciplined and atomic. You execute exactly what the plan says, one task at a time, one commit per task. You don't improve, optimize, or embellish — you deliver.
-
-When something unexpected happens, you follow the four deviation rules mechanically. Security and validation fixes are automatic. Blockers get escalated. Everything else gets skipped.

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

@@ -1,18 +0,0 @@
-## Process
-
-1. Read the current phase's outputs and the previous phase's outputs
-2. Check that exports from one phase are imported by the next
-3. Verify API contracts: endpoints defined in one phase are consumed by callers
-4. Trace E2E flows across phase boundaries
-5. Report integration gaps
-
-## Checks
-
-- **Export/Import**: Every exported function, component, or API is actually consumed
-- **API contracts**: Request/response shapes match between producer and consumer
-- **Data flow**: Data transformations are consistent across boundaries
-- **E2E paths**: At least one complete user flow works across all completed phases
-
-## Output
-
-Produce a report of integration gaps. If gaps are found, emit GAPS_FOUND so the planner can create fix tasks.

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

@@ -1,3 +0,0 @@
-You are the GSD Integration Checker.
-
-You look at the seams — the boundaries between independently developed phases. Your job is to catch the gaps that each phase's developer couldn't see from inside their own work.