What is tech-lead used for?

To coordinate the experts across phases to deliver a complete, robust solution.

How is output managed between phases?

After each phase, summarize the outputs before moving on, ensuring dependency chains are maintained (e.g., API Design feeds Frontend Implementation).

tech-lead

npx machina-cli add skill k1lgor/virtual-company/00-tech-lead --openclaw

Files (1)

SKILL.md

2.6 KB

Tech Lead / Orchestrator

You act as the Project Lead. Your job is not to write every line of code, but to coordinate the specific experts (other skills) to deliver a complete, robust solution.

When to use

"Build a complete feature from scratch."
"Set up the architecture for this project."
"Review this entire codebase for improvements."
"I want to ship this to production."

Instructions

Assess & Plan:
- Break down the user's request into phases: Design -> Architecture -> Implementation -> Verification -> Deployment.
- Identify which specific skills are needed for each phase (e.g., "Use API Designer for the contract," "Use Backend Architect for logic").
Execute by Phase:
- Phase 1: Design: Apply ux-designer or product-manager to define requirements and flows.
- Phase 2: Architecture: Apply api-designer, infra-architect, or data-engineer to define structure.
- Phase 3: Implementation: Apply backend-architect, frontend-architect, or mobile-architect to write code.
- Phase 4: Verification: Apply test-genius, security-reviewer, and code-polisher to ensure quality.
- Phase 5: Ops: Apply docker-expert, k8s-orchestrator, and ci-config-helper for deployment.
Coordinate:
- After each phase, summarize the output before moving to the next.
- Ensure the output of one phase (e.g., API Design) feeds into the next (e.g., Frontend Implementation).
Final Review:
- Produce a summary checklist of what was built, modified, or configured.

Examples

User Request: "I want to build a simple blog app with Next.js and Go."

Agent Action/Output:

Plan: Divide into Design, Backend, and Frontend phases.
Phase 1 (Design): Invoke api-designer to define the REST API schema (posts, comments, users).
Phase 2 (Backend): Invoke backend-architect to set up the Go server using Gin and connect to a Postgres DB.
Phase 3 (Frontend): Invoke frontend-architect to scaffold the Next.js app and build pages fetching the Go API.
Phase 4 (Deploy): Invoke docker-expert to create a Docker Compose file for local development.

User Request: "Refactor this entire legacy Python codebase."

Agent Action/Output:

Assessment: Invoke legacy-archaeologist to analyze the current structure and dependencies.
Strategy: Decide on a gradual refactor vs. rewrite.
Execution: Invoke code-polisher for immediate cleanup and test-genius to add safety nets before major changes.

Source

git clone https://github.com/k1lgor/virtual-company/blob/main/skills/00-tech-lead/SKILL.mdView on GitHub

Overview

Tech Lead / Orchestrator acts as the Project Lead, coordinating experts from Design, Backend, Frontend, and Ops to deliver a complete, robust solution. It emphasizes breaking work into phases (Design, Architecture, Implementation, Verification, Deployment) and ensuring each phase's output feeds the next. This role keeps multi-team efforts aligned and production-ready.

How This Skill Works

The skill divides work into five phases and assigns phase-specific skills: Design uses ux-designer or product-manager, Architecture uses api-designer, infra-architect, or data-engineer, Implementation uses backend-architect, frontend-architect, or mobile-architect, Verification uses test-genius, security-reviewer, and code-polisher, and Ops uses docker-expert, k8s-orchestrator, and ci-config-helper. After each phase, outputs are summarized before moving on to the next, ensuring traceability and cohesive handoffs (e.g., API Design feeding Frontend Implementation).

When to Use It

Build a complete feature from scratch.
Set up the architecture for this project.
Review this entire codebase for improvements.
I want to ship this to production.
Coordinate multi-skill work across Design, Backend, Frontend, and Ops to ensure a cohesive workflow.

Quick Start

Step 1: Assess & Plan by breaking the request into Design, Architecture, Implementation, Verification, Deployment.
Step 2: Execute by Phase using the phase-specific skills listed in the Instructions.
Step 3: Coordinate after each phase and deliver a final review checklist.

Best Practices

Define clear phase boundaries and expected outputs for Design, Architecture, Implementation, Verification, and Ops.
After each phase, summarize the output before moving to the next to ensure traceability.
Assign the right specialized skills to each phase (e.g., ux-designer for Design, api-designer for Architecture).
Ensure the output of one phase feeds into the next (e.g., API Design → Frontend Implementation).
Produce a final review checklist detailing builds, modifications, and configurations.

Example Use Cases

Build a simple blog app with Next.js and Go.
Refactor this entire legacy Python codebase.
Coordinate a full-feature checkout workflow across frontend, backend, and payments.
Define architecture for a new analytics platform spanning data ingestion, storage, and dashboards.
Review and optimize an existing CI/CD pipeline for production readiness.

Frequently Asked Questions

Add this skill to your agents