tandem-executor

Executes bounded tasks from supervisor briefs with strict scope boundaries and structured artifact reporting.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/alatyshau/duet --skill tandem-executor-alatyshau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tandem-executor
Source: https://github.com/alatyshau/duet/tree/main/packages/skills/modes/tandem-executor
Command: npx skills add https://github.com/alatyshau/duet --skill tandem-executor-alatyshau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When delegating work to a cold-start AI session, agents often drift outside the assigned scope, guess past ambiguities, or produce artifacts in inconsistent layouts that supervisors cannot verify or archive. This Skill enforces a strict contract-based execution model so delegated tasks stay inside their brief and return verifiable results. ## Core Features & Use Cases - Brief-driven execution: Treats the supervisor's brief (Goal, Context, Tasks, Artifacts, Boundaries, Done criterion) as a hard wall, blocking scope creep and side-quests. - Standardized output shapes: Enforces exactly two output forms — a single output.md at node root, or an output/ folder with a canonical summary.md index required for archival. - Structured escalation: Defines a BLOCKED protocol that writes concrete questions to work/questions.md instead of guessing past ambiguity. - Use Case: A supervisor delegates a documentation task to a fresh AI session; the executor reads the saga plan chain, produces only the specified artifacts, classifies node-level versus saga-level outputs in summary.md, and returns a short honest status report. ## Quick Start Give the agent a self-contained brief with goal, tasks, artifacts, boundaries, and a done criterion, then ask it to execute the task as a tandem executor and return a status report.

Frequently Asked Questions about tandem-executor

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

FAQPage Schema
How do I delegate a task to a cold-start AI session without scope creep?

Write a self-contained brief with Goal, Context, Tasks, Artifacts, Boundaries, and a Done criterion, then have the executor treat it as a hard wall. Any work not in the brief is out of scope, and pull toward extra work triggers a BLOCKED escalation instead of silent expansion.

What output structure should a delegated AI task produce?

A single artifact goes to output.md at the node root with no extra summary. Multiple artifacts go in an output/ folder with output/summary.md as the canonical index, which is required before the node can be archived.

What should an AI agent do when a task brief is ambiguous?

It should stop and escalate as BLOCKED rather than guess. The agent writes one concrete question per item to work/questions.md with what would unblock it, then returns a one-line BLOCKED status to the supervisor.

What belongs in an output summary.md file?

Three sections in order: node-level outputs with purpose and next reader, saga-level outputs listing every change outside the node folder with absolute paths, and open questions. It is a static index of what is on disk, not a work log of the session.

When should an executor not edit plan.md or archive a node?

The executor may only make the single state transition the brief explicitly names, such as flipping a node from WIP to POLISH. Archival and node closure are the supervisor's procedure and are never performed by the executor.