team-executor

Resume and execute existing team-coordinate sessions with validated structure and state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the need to manually coordinate and rerun an existing team execution by safely resuming a previously planned team session and driving it through the remaining execution phases.

Core Features & Use Cases

  • Session Validation Before Execution: Verifies the session directory, required JSON files, and role-spec coverage, failing early with specific missing-component errors.
  • Executor-Only Orchestration: Loads an existing team-coordinate session, reconciles state, spawns team-worker agents, and advances the pipeline using callbacks and user wake commands.
  • Progress Control and Completion Handling: Supports status/check and resume/continue wake-ups, then produces a deliverables report and runs an interactive archive/keep/export completion action.

Quick Start

Run team-executor with the session path you want to execute, for example: "Skill(skill='team-executor', args='--session=/path/to/team-session-folder')".

Frequently Asked Questions about team-executor

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

FAQPage Schema
How do I resume a team execution session and run it to completion?

To resume a team execution session, invoke the executor with a mandatory --session argument pointing to your session folder. The tool validates the session structure, reconciles state, and orchestrates worker agents to drive the pipeline to completion.

What files are required to orchestrate pipeline execution with agent workers?

Orchestrating pipeline execution requires a team-session.json file, a task-analysis.json file, and a populated role-specs/ directory within the session folder. The executor performs strict pre-execution checks and fails early if any component is missing.

Can I check the progress of a background team orchestration task?

Yes, you can check the progress of a background team orchestration task. The executor supports status and check wake-up commands, allowing you to query the current state of the spawned team-worker agents and the overall pipeline advancement.

When should I use an automated session executor for role-specs?

You should use an automated session executor when analysis and role-generation phases are already finished, and the remaining work is pure execution. It eliminates manual coordination by safely resuming a planned team session and driving it through execution phases.

What happens after a team execution pipeline finishes running?

After a team execution pipeline finishes, the executor produces a deliverables report summarizing the outcome. It then runs an interactive completion action, allowing you to archive, keep, or export the final session results based on your workflow needs.