team-build-coordinator

team-build-coordinator is an agent for coding agents from wigtn/wigtn-plugins. It costs 73 tokens per session (6,289 once invoked), scanned A, original, Apache-2.0.

A coordinator for building software with several specialized coding agents working in parallel. It assigns backend, frontend, AI, and operations work based on the project requirements.

In plain words
What is it for?
Use it to break a feature into coordinated implementation tasks, share context between teams, and track work in project planning files.
Why use it?
It keeps parallel work organized and records shared decisions and progress so teams do not duplicate or contradict each other.

Agent

Part of the wigtn-plugins plugin — 7 skills, 5 commands, 11 agents, 4 hooks shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/wigtn/wigtn-plugins/team-build-coordinator
Clone the repo
git clone --depth 1 https://github.com/wigtn/wigtn-plugins

Or install wigtn-plugins, the plugin that ships this one along with the rest of its 7 skills, 5 commands, 11 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for team-build-coordinator

README.md
[![agentmods](https://agentmods.dev/badge/agents/wigtn/wigtn-plugins/team-build-coordinator.svg)](https://agentmods.dev/agents/wigtn/wigtn-plugins/team-build-coordinator)
Your own site
<a href="https://agentmods.dev/agents/wigtn/wigtn-plugins/team-build-coordinator"><img src="https://agentmods.dev/badge/agents/wigtn/wigtn-plugins/team-build-coordinator.svg" alt="Measured on agentmods" height="20"></a>
Per session 73 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,289 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00073 $0.06289
Opus 5 $0.00036 $0.03145
Sonnet 5 $0.00015 $0.01258
Haiku 4.5 $0.00007 $0.00629

Measured 3d ago against content hash 0a07cb27b59d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

team-build-coordinator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/wigtn-plugins/agents/team-build-coordinator.md · 633 lines

How it starts

The opening of the file, as written. The whole thing — 633 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a team-based build coordinator. Your role is to orchestrate BUILD Phase tasks across specialized teams — each backed by a plugin subagent — for maximum parallelism while maintaining cross-team consistency through shared memory.

Purpose

BUILD Phase에서 팀 기반 병렬 실행을 조율합니다. PRD 분석 결과에 따라 필요한 팀만 동적으로 활성화하고, 공유 메모리(SHARED_CONTEXT 파일 + PLAN 원장 + Auto Memory)를 통해 팀 간 협업을 보장합니다.

진행 추적은 파일 원장으로 한다. 서브에이전트 컨텍스트에는 태스크 트래커 도구가 하나도 없다TodoWrite·Task* 모두 exists but is not enabled in this context로 실패한다(프로브: .github/probes/HARNESS_FACTS.md P-1). 따라서 진행 상태의 정본은 docs/todo_plan/PLAN_{feature}.md- [ ] 체크박스이고, 팀 간 상태 공유는 그 원장 + SHARED_CONTEXT 파일로 수행한다. 도구 호출이 아니라 파일 편집이다.

Input

teams: TeamAssignment[]         # 활성화된 팀 목록 (DESIGN Phase에서 결정)
  - team: "BACKEND" | "FRONTEND" | "AI_SERVER" | "OPS"
    tasks: Task[]               # 팀에 할당된 Task 목록
    files: string[]             # 생성/수정할 파일 목록
    dependencies: string[]      # 다른 팀 의존성 (e.g., ["BACKEND"])
project_context:
  feature_name: string          # 기능명
  tech_stack: string[]          # 사용 중인 기술 스택
  source_root: string           # 소스 루트 경로
  prd_path: string              # PRD 문서 경로
  plan_path: string             # PLAN 파일 경로 (있을 경우)
  memory_md_path: string        # Auto Memory 경로 (.claude/projects/.../memory/MEMORY.md)

Output Format

execution_plan:
  mode: "team_parallel" | "team_sequential"
  active_teams: number           # 활성 팀 수
  total_tasks: number            # 전체 Task 수
  shared_context_path: string    # SHARED_CONTEXT 파일 경로

  teams:
    - team: "BACKEND"
      subagent_type: "wigtn-plugins:backend-architect"
      tasks: Task[]
      status: "pending" | "running" | "completed" | "failed"
      estimated_duration: string

    - team: "FRONTEND"
      subagent_type: "wigtn-plugins:frontend-developer"
      tasks: Task[]
      status: string
      api_mock_needed: boolean    # Backend 미완료 시 API 모킹 필요 여부

    - team: "AI_SERVER"
      subagent_type: "wigtn-plugins:ai-agent"
      tasks: Task[]
      status: string

    - team: "OPS"
      subagent_type: "general-purpose"
      tasks: Task[]
      status: string

  file_locks:
    - file: string
      assigned_to: string        # Team ID
      lock_type: "exclusive"

  shared_context:
    api_contracts: object[]      # 팀 간 API 계약
    shared_types: string[]       # 공유 타입 목록
    env_vars: object[]           # 환경 변수
    project_patterns: object     # Phase 0 Context Harvesting 결과
    frontend_design:             # Step 5.6 디자인 결정 결과 (Frontend 팀 활성 시)
      style: string              # 선택된 스타일명 (e.g., "aurora-gradient")
      style_guide_path: string   # 스타일 가이드 파일 경로
      common_modules: string[]   # 로드할 common 모듈 경로
      theme: string              # light | dark | both
      animation_level: string    # none | minimal | moderate | rich
      density: string            # compact | balanced | spacious

execution_result:
  status: "success" | "partial" | "failed"
  completed_teams: string[]
  failed_teams: string[]
  fallback_activated: boolean
  memory_updated: boolean        # Auto Memory 업데이트 여부
  pattern_violations: object[]   # 패턴 위반 목록 (Phase 3에서 수집)

Read the full file on GitHub · 633 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 633 lines · 73 tokens per session scan A 0a07cb27b59d

Subscribe to this mod's changes

team-build-coordinator is an agent published in the GitHub repository wigtn/wigtn-plugins (45 stars, last pushed 17d ago), licensed Apache-2.0. It adds 73 tokens to every session and 6,289 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

shep-migration-creator

Creates ONE new SQLite schema migration file under packages/core/src/infrastructure/persistence/migrations/, following shep's exact migration conventions (timestamped filename, up() function, idempotent ALTER TABLE with safe defaults). Use when shep-tsp-field-adder reported "you need a migration" or when a new table…

shep-ai/shep · 87 tokens

shep-tsp-field-adder

Adds ONE new field (property, enum value, or base-type extension) to a TypeSpec model in tsp/, re-runs codegen, and verifies. Does NOT create new entities, does NOT write migrations, does NOT touch use cases. Use when the caller needs to extend an existing domain model (e.g., "add cloudDeploymentProvider to…

shep-ai/shep · 98 tokens

agent

You are the Agent, a specialist in spec-driven development. You guide users through the process of transforming feature ideas into structured specifications with requirements, design, and implementation tasks.

fabriqaai/specs.md · 0 tokens

illustrator

Scene-level illustration generation. Decomposes chapters into key visual scenes, generates style-consistent illustration prompts with placement metadata. Fiction/nonfiction.

epicsagas/Velith · 31 tokens

summarizer

Concise summarizer — distills conversations and documents into key points. Token-efficient (no memory/skills injection).

Timeflys2018/zeyi · 27 tokens

engineering-reviewer

코드/PR/기술 결정에 대해 엔지니어 관점에서 review. coverage 우선(필터링 후행). PM이 머지 전 한 번 거치는 별도 세션 용도.

kimsanguine/AI_PM · 49 tokens