tech-lead

Evaluate runtime dependencies and coding patterns in Conductor orchestrator projects.

371|38|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill tech-lead-ibrahim-3d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-lead
Source: https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers/tree/main/skills/leads/tech-lead
Command: npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill tech-lead-ibrahim-3d

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Tech Lead provides structured, decision-grade technical guidance for Conductor orchestrator projects, helping teams choose implementation approaches, dependencies, and coding patterns while maintaining safety rails.

Core Features & Use Cases

  • Autonomous advisory on implementation approaches, runtime dependencies, and coding patterns.
  • Evaluates dependency sizes and identifies when escalations are needed for large changes.
  • Documents decisions for auditability and reproducibility across tracks.

Quick Start

Ask the Tech Lead to review architecture decisions or dependency changes for a feature in progress.

Frequently Asked Questions about tech-lead

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

FAQPage Schema
How do I evaluate runtime dependencies for breaking changes in an orchestrator project?

To evaluate runtime dependencies, this advisory assesses dependency sizes against defined thresholds and enforces guardrails for breaking changes. It escalates complex architectural decisions with clear rationale when large changes are detected.

What is the best way to choose implementation approaches and coding patterns safely?

Choosing implementation approaches requires structured, decision-grade technical guidance that maintains safety rails. This advisory provides autonomous decision support for coding patterns while documenting decisions for auditability and reproducibility.

Can I get autonomous technical decision support for architecture choices without manual review?

Yes, autonomous technical decision support is available for architecture choices, dependency selections, and coding patterns. It guides safe, scalable technical decisions and escalates only complex decisions to the user with clear rationale.

How do I document engineering decisions for auditability across project tracks?

Documenting engineering decisions ensures auditability and reproducibility across tracks. This advisory documents technical decisions regarding implementation approaches and dependencies, providing structured guidance for the orchestrator project.

When should I escalate complex technical decisions instead of choosing a coding pattern directly?

You should escalate complex technical decisions when changes exceed size thresholds or break guardrails. This advisory evaluates dependency choices and escalates these complex decisions to the user with clear rationale instead of acting autonomously.