dev-team

Coordinate multi-agent development workflows across isolated git worktrees with QA gates.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/JasperHG90/skills --skill dev-team-jasperhg90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-team
Source: https://github.com/JasperHG90/skills/tree/main/skills/development/dev-team
Command: npx skills add https://github.com/JasperHG90/skills --skill dev-team-jasperhg90

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jinja2, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Orchestrates a multi-phase development process by coordinating specialized agents (requirements engineer, staff engineers, senior developers, QA, product owner) to work in parallel across isolated git worktrees, delivering complex features with traceability and governance.

Core Features & Use Cases

  • Parallel, multi-agent planning and development across orthogonal workstreams with 95% certainty gates.
  • Phase-driven lifecycle: Requirements, Planning, Development, Review, and Report with QA gates at every transition.
  • Full artifact trail: RFCs, POCs, ADRs, research notes, and a final self-contained HTML report.
  • Live dashboard at .dev-team-artifacts/{team-name}/dashboard.html tracking progress, certainty, blockers, and DoD gates.
  • Structured workstream management and deterministic merge strategy to ensure safe, auditable integration.

Quick Start

Initialize a new dev-team and begin Phase 0 by gathering requirements.

Frequently Asked Questions about dev-team

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

FAQPage Schema
How do I coordinate a multi-agent development team for complex feature builds?

Multi-agent development coordination orchestrates specialized agents across isolated worktrees to plan and implement features. This workflow manages requirements gathering, parallel development, and review gates with full artifact traceability and deterministic merge strategies.

What is multi-agent orchestration with QA gates and certainty thresholds?

Multi-agent orchestration with QA gates spawns specialized agents that operate in parallel across workstreams, enforcing 95% certainty thresholds and quality checks at every phase transition from requirements through final reporting.

Can I use multi-agent orchestration to generate RFCs and ADRs with artifact traceability?

Multi-agent orchestration supports full artifact traceability by generating RFCs, ADRs, POCs, and research notes throughout the development lifecycle. A final self-contained HTML report consolidates all artifacts for auditable governance.

What's the best way to monitor parallel agent workstreams and blockers during development?

Monitoring parallel agent workstreams uses a live dashboard at .dev-team-artifacts/{team-name}/dashboard.html to track progress, certainty levels, blockers, and DoD gates across all active development phases in real time.

When should I avoid using a multi-agent dev team workflow?

Multi-agent dev team workflows target complex, multi-phase builds requiring parallel execution and governance. Simple feature implementations or single-developer tasks do not warrant the overhead of spawning specialized agents and enforcing certainty gates.

Does this multi-agent orchestration approach work with isolated git worktrees?

Multi-agent orchestration operates across isolated git worktrees, allowing specialized agents to develop orthogonal workstreams in parallel. A deterministic merge strategy ensures safe, auditable integration back into the main branch.