skills.rest
HoaiAn0906
HoaiAn0906COMMUNITY
Explore all skills by this author →
GitHub

tech-lead

Document architecture decisions and standardize code-review criteria for engineering teams.

Updated Aug 27, 2026
Search Tags:#architecture#adr#leadership#code-review#mentoring#design-docs#team-coordination
One-click install
npx skills add https://github.com/HoaiAn0906/Anki --skill tech-lead-hoaian0906
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-lead
Source: https://github.com/HoaiAn0906/Anki/tree/main/.cursor/skills/tech-lead
Command: npx skills add https://github.com/HoaiAn0906/Anki --skill tech-lead-hoaian0906

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns technical strategy with business goals by documenting architecture decisions, standardizing code reviews, and coordinating team efforts to reduce friction and onboarding time.

Core Features & Use Cases

  • ADR governance: Create, track, and reference architecture decisions to maintain system clarity.
  • Code quality & reviews: Establish criteria, mentor juniors, and improve review consistency.
  • Technical planning & coordination: Plan across teams, align on priorities, and drive technical roadmaps.
  • Use Case: When scaling a service, the Tech Lead guides ADRs, reviews critical design choices, and coordinates mentoring to lift the whole team.

Quick Start

Ask the AI to generate an ADR for a proposed feature and outline a plan for architecture decisions, reviews, and mentoring.

Frequently Asked Questions about tech-lead

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

FAQPage Schema
How do I create and track architecture decision records for my engineering team?▼

Architecture decision records are created by documenting technical choices, establishing reference links, and tracking them to maintain system clarity. This approach codifies decisions to align technical strategy with business goals and reduce onboarding friction.

What is the best way to standardize code review criteria and mentor junior developers?▼

Standardizing code reviews involves establishing consistent review criteria and structuring mentoring activities to guide juniors. This improves code quality consistency across the engineering squad and aligns team efforts during technical execution.

How do I coordinate technical planning and cross-team roadmaps for software engineering projects?▼

Technical planning coordination aligns priorities across multiple engineering squads to drive technical roadmaps. It requires structuring cross-team planning activities to ensure architecture decisions and team efforts map directly to business objectives.

When do I need formal architecture decision records and design docs for my project?▼

Architecture decision records and design docs are needed when scaling a service or standardizing engineering leadership practices. They maintain system clarity during feature expansion, reduce friction, and codify critical design choices for future reference.

Can I use this approach to guide design reviews and team coordination for scaling services?▼

Yes, design reviews and team coordination are core leadership scenarios for scaling services. The process guides ADR creation, reviews critical design choices, and coordinates mentoring to systematically lift the entire engineering team's capabilities.

Related Skills

Explore More Software Engineering Skills→
abdullah1854abdullah1854
1

session-handoff

Generate Markdown Architectural Decision Records from structured inputs.

Community
Intermediate
retz8retz8

planning

Creates structured plans with goals, scope, milestones, owners, timelines, and dependencies for projects.

Community
Basic
SkillPanelSkillPanel
199

docs-manager

Manage project documentation and standards in the .maister/docs/ repository.

Official
Advanced
haxlyshaxlys

code-review-excellence

Structure code review feedback into actionable guidance with checklists and templates.

Community
Advanced