team-dev

Coordinate parallel agent teams with staged reviews and task dependencies.

15|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/duronext/jig --skill team-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-dev
Source: https://github.com/duronext/jig/tree/main/core/skills/team-dev
Command: npx skills add https://github.com/duronext/jig --skill team-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes parallel implementation plans by coordinating agent teams and a team lead who enforces spec compliance and code quality reviews, reducing cycle times and increasing delivery confidence.

Core Features & Use Cases

  • Parallel execution: spawn implementer teammates to work in parallel under a team lead
  • Dual-review gates: spec compliance followed by quality reviews to ensure readiness
  • End-to-end orchestration: planning, task creation, blocking relationships, and rollout to integration
  • Reuse vs spawn decisions: reuse teammates for related tasks or spawn fresh for unrelated areas

Quick Start

Plan and launch a team-driven development session using your current backlog plan.

Frequently Asked Questions about team-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate parallel implementation tasks to accelerate software delivery?

Parallel implementation tasks are coordinated by spawning agent teammates under a team lead who manages task dependencies, blocking relationships, and staged reviews to accelerate software delivery.

How do dual-review gates work during team orchestration?

Dual-review gates enforce a spec compliance review followed by a code quality review, ensuring that parallel implementation efforts meet readiness standards before rollout to integration.

When do I need parallel team orchestration for complex engineering projects?

Parallel team orchestration is needed for complex engineering projects with multiple concurrent tasks that require staged reviews, blocking relationships, and context sharing across teams.

Do I need agent teams enabled to run parallel development workflows?

Yes, agent teams enabled is a required prerequisite, along with proper task dependencies, to execute parallel development workflows and team-driven orchestration sessions.

When should I reuse existing teammates versus spawning fresh ones for unrelated tasks?

Reuse teammates for related tasks to retain context, and spawn fresh teammates for unrelated areas to ensure clean isolation during parallel implementation efforts.

What is the best way to manage task creation and blocking relationships in a parallel workflow?

The best way to manage task creation and blocking is using a team lead to orchestrate end-to-end planning, define task dependencies, and enforce quality gates across parallel efforts.