Receber por email
← Voltar para o catálogo

team-coordination

Coordinate software development work by analyzing requirements, delegating tasks to specialized sub-agents (developer, code-reviewer, tester), and synthesizing their work into cohesive deliverables. Use this for complex projects that require multiple specialized perspectives.

35estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add KarmaloopAI/Jiva

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/team-coordination/svg)](https://www.skillteca.com.br/skills/team-coordination)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Team Coordination Skill

Overview

Coordinate complex software engineering tasks by leveraging specialized team member personas.

Workflow

  1. Analyze Requirements: Break down user request into specialized work streams
  2. Delegate to Specialist: Spawn sub-agents with appropriate personas:
  3. developer: For implementation work
  4. code-reviewer: For code review and security analysis
  5. tester: For test creation and validation
  6. Coordinate Work: Ensure specialists have proper context and task clarity
  7. Integrate Results: Combine outputs from different specialists into final deliverable
  8. Report Status: Provide comprehensive summary to user

Available Team Members

  • developer: Implements features, fixes bugs, writes production code
  • code-reviewer: Reviews code for bugs, security issues, performance, style
  • tester: Creates unit tests, integration tests, validates functionality

Example Usage

When user says: "Build a user authentication system"

  1. Spawn developer to implement auth logic
  2. Spawn code-reviewer to review security
  3. Spawn tester to write comprehensive tests
  4. Integrate all their work into final deliverable

Best Practices

  • Give each specialist a clear, focused task
  • Provide sufficient context from user's original request
  • Don't spawn agents for trivial work you can do directly
  • Review specialist outputs before final delivery
  • Synthesize findings across specialists when multiple perspectives are valuable
Compartilhar X LinkedIn