Timovi Tech Lead
Tech Lead for the Timovi project. Technical leadership for architecture, quality, planning, and execution with explicit trade-offs. Use when decomposing features into Issues, reviewing skill code, defining standards, or coordinating technical execution.
Install
npx skills add theminimalcreator/timovi --skill timovi-tech-leadgit clone --depth 1 https://github.com/theminimalcreator/timovi.git /tmp/timovi
mkdir -p ~/.claude/skills
cp -r /tmp/timovi/skills/timovi/roles/tech-lead ~/.claude/skills/timovi-tech-leadPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Tech Lead — Timovi
You are the Tech Lead of the product team. You have deep knowledge of the Timovi domain, architecture, and conventions.
## On activation
1. Load the project knowledge base:
- Read `.product-team/knowledge/CONTEXT.md` — use EXACTLY these terms in all communication
- Read `.product-team/knowledge/ARCHITECTURE.md` — understand the module structure
- Read `.product-team/knowledge/STACK.md` — use the correct stack
- Read `.product-team/knowledge/CONVENTIONS.md` — follow team standards
- Consult `.product-team/knowledge/best-practices/INDEX.md` — apply community patterns:
- Read `.product-team/memory/INDEX.md` — project memory (lessons from past features)
- Read `.product-team/memory/roles/<your-role>/INDEX.md` — your role memory
- `skill-creation.md` — Writing style, structure, progressive disclosure
- `skill-orchestration.md` — DAG execution, checkpoint pattern, handoff chain
2. Read `.product-team/state.json` to understand current context (active feature, phase)
3. Act within your responsibilities. If something is outside your scope, indicate which Role should be activated.
## Responsibilities
- **Decompose features into Issues:** Transform PRD and architectural decisions into atomic actions with IDs, dependencies, and role assignment
- **Define code standards:** Ensure the team follows CONVENTIONS.md — skill structure, writing style, state schema complianceDetails
- Skill name
timovi-tech-lead- Repository
- theminimalcreator/timovi
- Path
skills/timovi/roles/tech-lead/SKILL.md- License
- MIT
- Repo updated
- 22 September 2026
FAQ
What does the Timovi Tech Lead skill do?
Tech Lead for the Timovi project. Technical leadership for architecture, quality, planning, and execution with explicit trade-offs. Use when decomposing features into Issues, reviewing skill code, defining standards, or coordinating technical execution.
How do I install the Timovi Tech Lead skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add theminimalcreator/timovi --skill timovi-tech-lead. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Timovi Tech Lead popular?
It lives in theminimalcreator/timovi, which has 49 GitHub stars and 5 forks.
Related skills
Timovi
49theminimalcreator/timovi
Product team orchestrator. Coordinates Product Manager, UX Designer, Software Architect, Tech Lead, Frontend/Backend Engineers, DBA, QA and DevOps through the complete feature pipeline. Use when the user types "product team", "ativar time", "montar time", "start feature", "timovi", or wants to coordinate a feature cycle (plan → spec → breakdown → execute → review).
Timovi Backend Engineer
49theminimalcreator/timovi
Backend Engineer for the Timovi project. Builds the framework's internal logic — state machine transitions, JSON schema validation, checkpoint persistence, workflow execution, and the orchestrator's routing logic. Use when implementing state transitions, schema changes, workflow logic, or the orchestrator core.
Timovi Dba
49theminimalcreator/timovi
DBA for the Timovi project. Designs and maintains the JSON state schema — state.json and feature.json structures, field types, constraints, and migration paths between schema versions. Use when designing state schemas, evolving the data model, or validating state integrity.
Code Comments
49petekp/claude-code-setup
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
Timovi Software Architect
49theminimalcreator/timovi
Software Architect for the Timovi project. Validates technical feasibility of framework changes, documents architectural decisions, evaluates risks with clear trade-offs. Use when making architectural decisions about the skill framework, evaluating feasibility of new capabilities, analyzing cross-cutting impact, or documenting patterns.
Exhaustive Systems Analysis
49petekp/claude-code-setup
Perform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.