Coordinate architecture decisions and governance across the SDLC with Mermaid diagrams.
npx skills add https://github.com/VitorAndTxr/omni-sw --skill tl
Please help me install this Agent Skill. Skill: tl Source: https://github.com/VitorAndTxr/omni-sw/tree/main/skills/tl Command: npx skills add https://github.com/VitorAndTxr/omni-sw --skill tl
Tech Lead — Senior technical authority. Owns architecture decisions and technical quality across the entire project lifecycle. All diagrams MUST use Mermaid syntax. Use when: (1) assessing technical risks during planning (/tl plan), (2) designing system architecture (/tl design), (3) validating technical feasibility (/tl validate), (4) providing guidance during implementation (/tl implement), (5) reviewing code quality and architecture compliance (/tl review), (6) reviewing test coverage (/tl test), (7) producing technical documentation (/tl document), or (8) user says "tl", "tech lead", "architecture", "design", "code review", "technical validation".
Kick off the seven-phase SDLC workflow with the TL agent to guide architecture decisions from planning to documentation.
High-intent search queries and answers about installing and using this skill.
Coordinate architecture decisions across the SDLC by enforcing technical governance, validating feasibility, and managing backlog transitions. This ensures structured cross-team validation and traceability from planning through documentation.
Document system architecture using Mermaid syntax to enforce design clarity and governance. This produces structured architecture artifacts and diagrams that guide the entire software development lifecycle.
Enforce quality gates and code review standards by validating architecture compliance and test coverage. This coordinates cross-team validation to ensure structured governance before backlog progression.
Assess technical risks during project planning when you need a senior authority to own architecture decisions and technical quality. This validates technical feasibility and enforces governance standards.
Yes, you can manage backlog transitions and cross-team validation through structured governance. This ensures quality gates are met and architecture compliance is verified before any project progression.
Without structured Mermaid artifacts, architecture governance lacks design clarity and traceability across the SDLC. This leads to uncoordinated cross-team validation and missed quality gates during implementation.
kevinlinEstimate time, effort, cost, and complexity for software backlog items with P50/P80 confidence intervals.
microsoftValidate and enforce quality gates across CI/CD workflows with pass/fail reports.
htafollaAudit and validate framework compliance with detailed audit reports.
coalesce-labsGenerate structured decision documents with templates for product choices.
