team-ultra-analyze

Coordinates a multi-role pipeline to analyze technical topics and synthesize findings into a structured document.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/tcytan/tecton --skill team-ultra-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ultra-analyze
Source: https://github.com/tcytan/tecton/tree/main/.claude/skills/team-ultra-analyze
Command: npx skills add https://github.com/tcytan/tecton --skill team-ultra-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns ambiguous technical topics into structured, evidence-based conclusions by coordinating a multi-role analysis pipeline with user-in-the-loop clarification and iteration.

Core Features & Use Cases

  • Multi-mode team orchestration (Quick/Standard/Deep): Runs a coordinated explore → analyze → discuss → synthesize workflow, with deeper feedback-driven loops when needed.
  • Role-based perspective coverage: Uses specialized roles (explorer, analyst, discussant, synthesizer) to produce consistent artifacts across perspectives and dimensions.
  • Evidence-first synthesis: Integrates exploration and analysis outputs into prioritized recommendations and explicit open questions.

Quick Start

Run team-ultra-analyze with the topic you want analyzed (optionally adding --mode=deep and --role=coordinator) to generate explorations, deep analyses, discussion rounds, and final conclusions.

Frequently Asked Questions about team-ultra-analyze

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

FAQPage Schema
How do I perform multi-perspective codebase analysis for complex system design investigations?

Multi-perspective codebase analysis is performed by coordinating multi-role exploration, deep analysis, discussion, and final synthesis. This approach transforms ambiguous technical topics into structured, evidence-based conclusions using specialized roles.

What is the best way to structure an evidence-based technical analysis with iterative clarification?

Evidence-based technical analysis is structured through a coordinator-driven pipeline applying parallel explore and analyze task fan-out, followed by a feedback-gated discussion loop with up to five rounds for iterative clarification and final synthesis.

How does multi-agent orchestration work for debugging strategy and codebase exploration?

Multi-agent orchestration works by assigning specialized roles like explorer, analyst, discussant, and synthesizer to produce consistent artifacts. It runs a coordinated explore, analyze, discuss, and synthesize workflow with user-in-the-loop feedback.

Can I run a quick analysis mode for smaller codebase investigations instead of a full deep dive?

Yes, you can run quick analysis modes for smaller codebase investigations. The orchestration supports Quick, Standard, and Deep modes, allowing you to scale the explore, analyze, and synthesize workflow based on your topic complexity.

When do I need multi-role exploration with a discussion loop for software investigations?

Multi-role exploration with a discussion loop is needed when you want multiple perspectives like technical, architectural, business, and domain-expert. It applies to software and system investigations requiring iterative clarification to refine findings.

Does the structured codebase analysis pipeline write synthesis artifacts to a specific location?

Yes, the structured codebase analysis pipeline writes synthesis artifacts to a session directory. It integrates exploration and analysis outputs into prioritized recommendations and explicit open questions for your technical topic.