tech-lead

Decompose architectural ADRs into actionable tasks for specialist teams.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/asalhamed/dev-agents --skill tech-lead-asalhamed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-lead
Source: https://github.com/asalhamed/dev-agents/tree/main/tech-lead
Command: npx skills add https://github.com/asalhamed/dev-agents --skill tech-lead-asalhamed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan, decompose, and assign development work to specialist agents (backend, frontend, QA, devops). You receive inputs such as ADRs, contracts, and repo context, and you transform high-level directives into concrete, trackable work items.

Core Features & Use Cases

  • Break down architecture ADRs into task-level work for domain, application, and infrastructure layers.
  • Define branch strategies, kickoff artifacts, rollout plans, and DoD to align multiple teams.
  • Coordinate cross-repo and cross-team delivery, ensuring bounded contexts and FP-first practices are respected.

Quick Start

Create a feature kickoff, establish a branch, decompose tasks, and spawn agents following the standard pipeline.

Frequently Asked Questions about tech-lead

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

FAQPage Schema
How do I decompose architecture ADRs into actionable development tasks?

Decomposing architecture ADRs involves transforming high-level directives into trackable work items for domain, application, and infrastructure layers. This process breaks down ADRs into concrete tasks for backend, frontend, QA, and devops specialists to execute.

What is the best way to coordinate cross-team delivery with bounded contexts?

Coordinating cross-team delivery with bounded contexts requires defining task sequences and kickoff artifacts that align multiple teams. Establishing structured briefs ensures cross-repo delivery respects bounded contexts and FP-first practices across specialist agents.

How do I define branch strategies and rollout plans for multi-team features?

Defining branch strategies and rollout plans for multi-team features requires creating feature kickoffs and decomposition pipelines. You establish branches, define task sequences, and generate kickoff artifacts to align cross-team delivery with defined contracts.

Can I use ADRs and repo context to generate kickoff artifacts for specialist agents?

Yes, you can use ADRs, contracts, repo context, and tech stack as inputs to generate kickoff artifacts. These inputs are orchestrated into structured briefs and kickoff documents that spawn implementation agents for backend, frontend, QA, and devops.

Do I need predefined contracts to decompose tasks across backend and frontend layers?

You need predefined contracts to decompose tasks across backend and frontend layers accurately. Contracts serve as critical inputs that ensure task decomposition aligns cross-team delivery with bounded contexts and respects architectural boundaries.

Why does cross-repo coordination fail without structured task briefs?

Cross-repo coordination fails without structured task briefs because specialist teams lack aligned task sequences and defined DoD. Generating kickoff artifacts and rollout plans ensures multiple teams respect bounded contexts and contracts during implementation.