Skip to content

Sample: Azure Function + Squad — prompt-driven agent pipeline #213

Closed

Description

@bradygaster

Overview

Add a production-ready sample demonstrating an Azure Function + Squad integration.

Architecture

  1. HTTP POST Request → Azure Function receives a prompt
  2. Squad Assembly → defineTeam() + defineAgent() configure squad in-memory
  3. Prompt Processing → Squad team processes concurrently
  4. Response → HTTP 200 with structured agent outputs

Use Case: Content Review Squad

  • Analyst → Checks tone, readability, clarity
  • Subject Matter Expert → Validates technical accuracy
  • SEO Specialist → Recommends keywords/structure
  • Editor → Flags grammar, consistency, brand voice

Key Demonstrations

  • defineTeam(): SDK-First mode (no YAML)
  • defineAgent(): Per-agent prompts and capabilities
  • Streaming Response: Results as they complete
  • CostTracker: Token usage per agent
  • SkillRegistry: Automatic task routing

Acceptance Criteria

  • Runs on Azure Functions runtime v4 (Node.js 20+)
  • TypeScript + strict mode
  • Uses defineTeam()/defineAgent() builders (SDK-First)
  • README: local setup, Azure deployment, customization
  • Vitest suite: team assembly, HTTP contract, aggregation, errors
  • Local dev vs. Azure deployment examples
  • CLI equivalent documentation

Project Structure

samples/azure-function-squad/
├── index.ts (Azure Function HTTP trigger)
├── lib/ (team-builder, prompt-processor, types)
├── package.json
├── README.md
└── tests/

Activity

  1. added
    squadSquad triage inbox — Lead will assign to a member
    on Mar 5, 2026
  2. github-actions commented on Mar 5, 2026

    @github-actions
    Contributor

    🏗️ Squad Triage — Keaton (Lead)

    Issue: #213 — Sample: Azure Function + Squad — prompt-driven agent pipeline
    Assigned to: Hockney (Tester)
    Reason: Issue relates to testing/quality work

    @copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

    Team roster:

    • Keaton (Lead) → label: squad:keaton
    • Verbal (Prompt Engineer) → label: squad:verbal
    • Fenster (Core Dev) → label: squad:fenster
    • Hockney (Tester) → label: squad:hockney
    • McManus (DevRel) → label: squad:mcmanus
    • Kujan (SDK Expert) → label: squad:kujan
    • Edie (TypeScript Engineer) → label: squad:edie
    • Kobayashi (Git & Release) → label: squad:kobayashi
    • Fortier (Node.js Runtime) → label: squad:fortier
    • Rabin (Distribution) → label: squad:rabin
    • Baer (Security) → label: squad:baer
    • Redfoot (Graphic Designer) → label: squad:redfoot
    • Strausz (VS Code Extension) → label: squad:strausz
    • Saul (Aspire & Observability) → label: squad:saul
    • Kovash (REPL & Interactive Shell) → label: squad:kovash
    • Marquez (CLI UX Designer) → label: squad:marquez
    • Cheritto (TUI Engineer) → label: squad:cheritto
    • Breedan (E2E Test Engineer) → label: squad:breedan
    • Nate (Accessibility Reviewer) → label: squad:nate
    • Waingro (Product Dogfooder) → label: squad:waingro
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  3. bradygaster commented on Mar 5, 2026

    @bradygaster
    CollaboratorAuthor

    Implemented in samples/azure-function-squad/ — Content Review Squad with SDK-First builder pattern. Committed to dev at 14af372.

  4. added 4 commits that reference this issue on Mar 9, 2026
    557ca43
    bc9fe0e
    0df7c54
    96c83c5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    go:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a member

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions