role-tech-lead

Name: role-tech-lead
Availability: InStock
Author: ilandahan

Guide Tech Lead teams through architecture decisions and code review criteria.

9|2|Updated Dec 10, 2025

Search Tags:#architecture #ADR #leadership #code-review #mentoring #design-patterns

Ready to run

npx skills add https://github.com/ilandahan/AID --skill role-tech-lead

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: role-tech-lead
Source: https://github.com/ilandahan/AID/tree/main/.claude/skills/role-tech-lead
Command: npx skills add https://github.com/ilandahan/AID --skill role-tech-lead

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides structured guidance and decision-making support for Tech Leads, aligning architecture, reviews, and operational readiness with the AID methodology.

Core Features & Use Cases

Architectural decision support: help evaluate options, capture trade-offs, and align with team standards.
Code review mentoring: establish consistent guidance, promote quality, and reduce cycle time.
Phase-focused guidance: deliver phase-specific outputs for Discovery, PRD, Tech Spec, Development, and QA & Ship.
Operational readiness planning: ensure monitoring, runbooks, rollbacks, and handoffs are defined.

Quick Start

Use this skill to guide a technical decision for a new module by prompting for architecture choices, design constraints, and review criteria.

Frequently Asked Questions about role-tech-lead

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

FAQPage Schema

How do I document architecture decisions for a new software module?▼

To document architecture decisions effectively, use an Architecture Decision Record (ADR) to capture evaluated options, trade-offs, and team standards alignment. This structured approach ensures technical choices are recorded consistently across the development lifecycle.

What should be included in an operational readiness checklist for deployment?▼

An operational readiness checklist for deployment must define monitoring configurations, runbooks, rollback procedures, and handoff protocols. This ensures system stability and clear on-call responsibilities before shipping software.

How do I establish consistent code review criteria for my engineering team?▼

Establish consistent code review criteria by applying structured mentoring guidelines that promote quality and reduce cycle time. This approach aligns design pattern usage and architectural standards during the development phase.

When do I need to create an Architecture Decision Record?▼

You need to create an Architecture Decision Record during the Tech Spec phase when facing significant architectural choices. It captures design constraints and evaluates options to align the team before development begins.

Can I apply phase-specific technical guidance across Discovery, PRD, and QA?▼

Yes, you can apply phase-specific technical guidance across Discovery, PRD, Development, and QA. This provides targeted outputs like ADR templates and review criteria tailored to each stage of the software lifecycle.

What is the best way to mentor developers during technical design reviews?▼

The best way to mentor developers during technical design reviews is to use structured code review criteria and design pattern guidelines. This promotes quality, reduces cycle time, and aligns decisions with team standards.