team-techlead

Simulate a TechLead role to design architecture and generate design documentation.

19|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/DangQuangSE/team-development-skills --skill team-techlead
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-techlead
Source: https://github.com/DangQuangSE/team-development-skills/tree/main/virtual-team-skill/skills/team-techlead
Command: npx skills add https://github.com/DangQuangSE/team-development-skills --skill team-techlead

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simulates the role of a TechLead in a virtual software development team, handling system architecture, technology stack selection, and producing design documentation.

Core Features & Use Cases

  • System Architecture: Design the system architecture based on provided BA artifacts.
  • Technology Stack: Select the technology stack with justification.
  • Documentation: Create ERDs, sequence diagrams, and ADRs.
  • Quality Control: Validate BA artifacts for consistency and completeness.

Quick Start

Run the team-techlead command with the project slug and level.

Frequently Asked Questions about team-techlead

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

FAQPage Schema
What is a tech lead's role in system architecture and design documentation?

A tech lead handles system architecture, technology stack selection, and produces design documentation like ERDs, sequence diagrams, and ADRs to translate business requirements into technical blueprints.

How do I generate system architecture and ERDs from business analysis artifacts?

You can generate system architecture and ERDs by parsing BA artifacts as input, analyzing them for consistency, and running an automated tech lead simulation to output design documentation files.

What is the best way to document technology stack selection and architecture decisions?

The best way to document technology stack selection is by generating a tech-stack.md file with justifications and creating Architecture Decision Records to capture design decision-making context.

Do I need business analysis artifacts to start system design and architecture documentation?

Yes, you need business analysis artifacts as input to validate consistency and completeness before generating architecture.md, ERD.md, and sequence-diagrams.md files for the project.

Can I use a virtual team setup for software architecture and sequence diagram generation?

Yes, you can simulate a virtual software development team environment where a tech lead role automates sequence diagram generation and architectural design tasks from parsed requirements.

What limitations exist when simulating a tech lead for design documentation?

Limitations include relying entirely on the quality of input BA artifacts, as the simulation validates and parses these artifacts to make design decisions without human engineering judgment.