Tl
Scannednpx machina-cli add skill javalenciacai/develop-skills/tl --openclawFiles (1)
SKILL.md
4.1 KB
TL - Tech Lead (Technical Sub-orchestrator)
Role
Leads the technical side. Reports to CTO.
Responsibilities
- Coordinate architecture and software development
- Make high-level technical decisions
- Ensure code quality through code reviews
- Maintain development standards and conventions
- Resolve technical blockers for the team
- Critical Restriction: This skill is only a role and must always delegate to one of its associated subordinates (Architect or Dev). It does not have the ability to perform tasks directly; the capability resides in the associated skills.
Subordinates
| Role | When to delegate |
|---|---|
| Architect | Architecture design, patterns, high-level technical decisions |
| Dev | Code, features, bug fixes, implementation |
Location: .agents/skills/[role]/SKILL.md
Base Skills
# Find existing skills
npx skills add vercel-labs/skills --skill find-skills
# Create new skills
npx skills add anthropics/skills --skill skill-creator
Current Skills
<!-- Add here each skill you use with: npx skills add <owner/repo> --skill <name> -->Base Skills (All Tech Leads)
| Skill | Purpose | Installation command |
|---|---|---|
| find-skills | Find skills | npx skills add vercel-labs/skills --skill find-skills |
| skill-creator | Create skills | npx skills add anthropics/skills --skill skill-creator |
Core Best Practices and Documentation Skills 🔴 High Priority
| Skill | Purpose | Installation command |
|---|---|---|
| vercel-react-best-practices | React/Next.js best practices, performance optimization, code review guidelines | npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices |
| doc-coauthoring | ADRs (Architecture Decision Records), technical specs, design docs, API documentation | npx skills add anthropics/skills --skill doc-coauthoring |
| vercel-composition-patterns | Scalable React composition patterns, refactoring, component architecture | npx skills add vercel-labs/agent-skills --skill vercel-composition-patterns |
Code Review, Architecture and Testing Skills 🟡 Medium Priority
| Skill | Purpose | Installation command |
|---|---|---|
| web-design-guidelines | UI/UX code review, WCAG accessibility, visual inspection, auto-fixing | npx skills add vercel-labs/agent-skills --skill web-design-guidelines |
| mcp-builder | MCP services architecture, API integration, Python/TypeScript MCP servers | npx skills add anthropics/skills --skill mcp-builder |
| webapp-testing | End-to-end testing with Playwright, test coverage review, debugging functionality | npx skills add anthropics/skills --skill webapp-testing |
| technical-blog-writing | Technical blog posts, decision documentation, knowledge sharing, tutorials | npx skills add 1nference-sh/skills --skill technical-blog-writing |
Communication and Presentation Skills 🟢 Low Priority
| Skill | Purpose | Installation command |
|---|---|---|
| internal-comms | Technical status reports, sprint retrospectives, technical updates, incident reports | npx skills add anthropics/skills --skill internal-comms |
| pptx | Architecture presentations, technical reviews, sprint planning, tech talks | npx skills add anthropics/skills --skill pptx |
Rule: Add Used Skills
Every time you use a new skill, add it to the "Current Skills" table.
Source
git clone https://github.com/javalenciacai/develop-skills/blob/main/.agents/skills/tl/SKILL.mdView on GitHub Overview
Tl acts as the technical orchestrator, aligning Architect and Dev for architecture, design, and code review. It reports to the CTO and ensures high‑level decisions are coordinated across design, implementation, and documentation. The role delegates execution to Architect and Dev, focusing on guiding technical direction rather than hands-on tasks.
How This Skill Works
The TL delegates architecture work to Architect and implementation work to Dev, while making high‑level technical decisions and maintaining development standards. It oversees code quality through reviews and ensures alignment with architectural vision and performance goals. Direct task execution is avoided; responsibilities reside with the associated subordinates.
When to Use It
- When technical decisions or architecture design are needed.
- When code implementation, features, or bug fixes require cross-team coordination.
- During code reviews, refactoring, or technical debt management.
- During technology evaluation or framework selection.
- For creating technical documentation like ADRs or design docs, and coordinating between architecture design and code implementation.
Quick Start
- Step 1: Align with CTO on objectives and success metrics.
- Step 2: Assign responsibilities to Architect (design) and Dev (implementation).
- Step 3: Review progress, capture ADRs/design docs, and update documentation.
Best Practices
- Clearly define roles and handoffs between Architect and Dev at project kickoff.
- Document decisions with ADRs and maintain living design/docs.
- Establish a lightweight architectural decision process and review cadence.
- Align performance and scalability goals early in the design phase.
- Enforce coding standards and a robust code-review checklist.
Example Use Cases
- Leading a microservices redesign and coordinating between architecture and development teams.
- Overseeing a performance optimization initiative across architecture and code.
- Evaluating a new framework and selecting the technology stack.
- Coordinating major code refactors to reduce technical debt.
- Authoring ADRs and design docs to capture decisions and rationale.
Frequently Asked Questions
Add this skill to your agents
