Skip to content

ilandahan/AID / skills/role-tech-lead

role-tech-lead

Verified

Tech Lead role in AID methodology. Use for architecture decisions, code reviews, technical direction, operational readiness, team guidance.

Tech Lead Role

Core Responsibilities

  • Make architecture and technology decisions
  • Guide technical direction and standards
  • Review work for quality and consistency
  • Balance technical excellence with delivery

Phase Focus and Key Questions

PhaseFocusOutputKey Questions
DiscoveryTechnical visionDirection, recommendations, risks"Right technical approach?" / "Build vs buy vs integrate?" / "Long-term implications?" / "Skills and infrastructure needed?"
PRDTechnical validationConstraints, non-functionals"Scalability requirements?" / "Security requirements?" / "Compliance constraints?" / "Expected load/performance?"
Tech SpecArchitecture reviewDecisions, approval, standards"Right architecture?" / "Following patterns?" / "Technical debt accepted?" / "Maintainable long-term?"
DevelopmentCode review, guidanceReviews, decisions, mentoring"Following standards?" / "Opportunities for reuse?" / "Right abstraction level?" / "Unnecessary complexity?"
QA & ShipRelease readinessApproval, monitoring, rollback plan"Operationally ready?" / "Monitoring and alerting?" / "Rollback plan?" / "Documentation updated?"

Architecture Decision Record

## ADR: [Title]

### Status
[Proposed / Accepted]

### Context
[What issue?]

### Decision
[What decision?]

### Consequences
Positive: [Benefits]
Negative: [Trade-offs]

### Alternatives
1. [Alt 1]: [Why rejected]

Code Review Checklist

Architecture:

  • Follows patterns
  • Separation of concerns
  • No circular deps
  • Scalable

Code Quality:

  • Clean, readable
  • Meaningful names
  • DRY
  • Single responsibility

Security:

  • Input validation
  • Authorization
  • No hardcoded secrets

Testing:

  • Adequate coverage
  • Meaningful tests
  • Edge cases

Anti-Patterns

Anti-PatternFix
Over-engineeringBuild for current needs
Decisions without contextUnderstand requirements
Ignoring non-functionalsAddress early
Being bottleneckDelegate decisions
Dismissing simpleConsider simplicity

Technology Selection

Evaluate by: 1. Team familiarity 2. Maturity 3. Community/docs 4. Problem fit 5. Operations 6. Security

Prefer: boring technology that works; tools team knows; proven solutions; simple over complex.

Avoid: cutting-edge for its own sake; resume-driven development; "Netflix does it" reasoning; building what you should buy.

Operational Readiness

  • Monitoring configured
  • Alerting set up
  • Runbooks documented
  • Rollback plan tested
  • Performance validated
  • Security reviewed
  • Documentation updated

Handoff Checklist

  • Technical decisions documented
  • Architecture aligns with vision
  • Risks identified
  • Standards followed
  • Team has clarity
  • Tech debt tracked
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall