skills.rest
rhorba
rhorbaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-lead

Guides architecture decisions, code review standards, and tech stack selection using YAGNI principles.

Updated Aug 20, 2026
Search Tags:#architecture#code review#system design#tech stack#adr#technical debt#yagni
One-click install
npx skills add https://github.com/rhorba/RestoLedger --skill tech-lead-rhorba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-lead
Source: https://github.com/rhorba/RestoLedger/tree/main/skills/tech-lead
Command: npx skills add https://github.com/rhorba/RestoLedger --skill tech-lead-rhorba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineering teams often over-engineer solutions, adopt premature abstractions, or make inconsistent technical decisions without a structured framework. This Skill provides disciplined technical leadership guidance for architecture design, code review, and technology selection grounded in YAGNI principles. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Structured templates for documenting significant technical choices with context, options, and consequences. - YAGNI Decision Gate: A built-in check that filters out speculative features, premature microservices, and unnecessary infrastructure before proposals are made. - Code Review & Tech Debt Standards: Merge-blocking criteria, PR size guidelines, and a triage system for categorizing technical debt by severity. - Use Case: When deciding between microservices and a monolith for a three-person team, the Skill applies the YAGNI gate, recommends the monolith, and produces an ADR documenting the tradeoffs and review triggers. ## Quick Start Ask the tech lead to evaluate whether your current project needs microservices or a monolith and produce an architecture decision record.

Frequently Asked Questions about tech-lead

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

FAQPage Schema
How do I decide between microservices and a monolith?▼

Start with a monolith unless you have proven scaling or team-boundary needs. The YAGNI gate recommends microservices only after outgrowing a monolith, and Docker Compose before Kubernetes for small deployments.

How to write an architecture decision record (ADR)?▼

An ADR captures status, context, options considered with pros and cons, the decision, and consequences. Include a review trigger such as a traffic threshold so the team knows when to revisit the choice.

What should block a pull request in code review?▼

Block merges on security issues like unescaped input or hardcoded secrets, data loss risks, untested business logic, and breaking API contracts without versioning. Performance and readability concerns are advisory only.

When should I choose REST over GraphQL for an API?▼

Choose REST when you have a single client, a small team, and no dynamic query requirements. GraphQL adds learning curve and complexity that is only justified when client data-fetching patterns diverge significantly.

How do I triage technical debt in a sprint?▼

Classify debt into three tiers: blocking items fixed immediately, degrading items fixed within the sprint, and cosmetic items sent to the backlog. High-severity debt should have a fix plan within two sprints.

Related Skills

Explore More Software Engineering Skills→
foomakersfoomakers
6

refine-story

Refine user stories by adding acceptance criteria and technical analysis.

Official
Advanced
DenissvgnDenissvgn

architect

Automates architecture decision records and system design documentation for complex software projects.

Community
Basic
Codagent-AICodagent-AI
30

proposal-review

Pressure-test software development proposals for unexamined assumptions and unaddressed risks.

Official
Intermediate
tmchowtmchow
22

iterative:spike

Scope uncertain questions and build throwaway artifacts to validate ideas.

Community
Advanced