Guide Tech Lead teams through architecture decisions and code review criteria.
npx skills add https://github.com/ilandahan/AID --skill role-tech-lead
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
This skill provides structured guidance and decision-making support for Tech Leads, aligning architecture, reviews, and operational readiness with the AID methodology.
Use this skill to guide a technical decision for a new module by prompting for architecture choices, design constraints, and review criteria.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
lionbenjaminDocument non-negotiable technical constraints and governance for project scoping.
Snowflake-LabsA concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略
samjhechtDispatch a code-review subagent to verify implementation against plan or requirements.
racciolyDocument architectural decisions with ADRs to capture rationale and trade-offs.
