tech-lead

Coordinates bounded subagent teams for software delivery with governance and recovery.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill tech-lead-mathiasbourgoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-lead
Source: https://github.com/mathiasbourgoin/roster/tree/main/.agents/skills/tech-lead
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill tech-lead-mathiasbourgoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of coordinating bounded, single-level subagent teams for software delivery within platform spawning constraints, eliminating misalignment, scope drift, and inconsistent quality across multi-agent workflows.

Core Features & Use Cases

  • End-to-End Pipeline Orchestration: Manages the full delivery lifecycle from research and planning to implementation, review, QA, and merge, with strict phase isolation between agent invocations.
  • Governance & Gatekeeping: Enforces human validation quizzes, tool/skill/MCP request approval workflows, and merge quality bars to ensure all changes meet organizational standards.
  • Failure Recovery & CI Triage: Classifies and routes implementation bugs, flaky tests, and reviewer findings to the appropriate specialist agents, with clear escalation paths for ambiguous root causes.
  • Use Case: For a multi-feature software sprint, use this Skill to coordinate parallel implementer agents for disjoint work, sequential agents for overlapping file changes, and enforce merge requirements without violating subagent spawning limits.

Quick Start

Use the tech-lead skill to orchestrate your next multi-agent software delivery sprint, from initial planning through final merge and session closure.

Frequently Asked Questions about tech-lead

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

FAQPage Schema
How do I coordinate multiple subagents for software delivery without scope drift?

To coordinate subagent software delivery without scope drift, use bounded single-level team orchestration with strict phase isolation, context packet compression, and human validation gates to enforce alignment throughout the pipeline.

What is the best way to enforce merge governance and quality bars in a multi-agent workflow?

The best way to enforce merge governance in multi-agent workflows is applying automated quality bars, tool and skill request approval workflows, and human validation quizzes before allowing any delivery batch to merge.

How do I manage parallel and sequential implementer agents when orchestrating a software sprint?

Sprint orchestration manages parallel implementer agents for disjoint work and sequential agents for overlapping file changes, coordinating them within platform spawning constraints to ensure consistent delivery quality.

Can I route implementation bugs and flaky tests to specialist agents during CI triage?

Yes, you can route implementation bugs and flaky tests to specialist agents during CI triage by classifying failures and routing them with clear escalation paths for ambiguous root causes.

When should I not use single-level subagent teams for pipeline management?

You should not use single-level subagent teams for pipeline management when your workflow requires multi-level spawning hierarchies, as this approach operates within strict platform spawning constraints and enforces phase isolation.