sequential-orchestration

Execute Kiro spec tasks sequentially with tmux-backed visibility.

4|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/PeterFile/my-common-skills --skill sequential-orchestration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sequential-orchestration
Source: https://github.com/PeterFile/my-common-skills/tree/main/sequential-orchestration
Command: npx skills add https://github.com/PeterFile/my-common-skills --skill sequential-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the serial execution of spec tasks, ensuring that each task runs one-at-a-time with full visibility, using a Python-based orchestrator and tmux.

Core Features & Use Cases

  • One-at-a-time execution: Runs dispatch units sequentially, simplifying debugging and auditing.
  • tmux visibility: Provides live visibility into task progress via tmux sessions.
  • Flexible specs & dependencies: Handles .kiro specs with subtasks and dependencies, adapting to complex workflows.
  • Quick Start: Use the orchestrator to run a given spec and observe step-by-step results.

Quick Start

Run the orchestrator against a sample spec:

  • python scripts/sequential_loop.py --spec .kiro/specs/my-feature

Frequently Asked Questions about sequential-orchestration

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

FAQPage Schema
How do I run Kiro spec tasks one at a time with tmux visibility?▼

To run Kiro spec tasks one at a time with tmux visibility, use the Python orchestrator script to execute a given spec serially. It dispatches tasks sequentially via the codeagent wrapper while providing live progress updates in tmux sessions.

What is the best way to orchestrate spec tasks in rate-limited environments?▼

The best way to orchestrate spec tasks in rate-limited environments is serial execution. Running dispatch units sequentially prevents quota exhaustion and ensures predictable, auditable progress when task execution is constrained by external limits.

Can I handle specs with subtasks and dependencies using sequential orchestration?▼

Yes, sequential orchestration handles .kiro specs with subtasks and dependencies. The Python orchestrator adapts to complex workflows by managing state and executing dependent dispatch units one-by-one to ensure proper task ordering.

Do I need tmux to execute dispatch units sequentially?▼

Yes, tmux is required to provide live visibility into task progress. The orchestrator uses tmux-backed sessions to display the step-by-step execution of spec tasks, allowing you to observe and audit the serial dispatch process in real time.

Why use serial execution instead of parallel dispatch for spec tasks?▼

Serial execution simplifies debugging and auditing by running tasks one at a time. Unlike parallel dispatch, serial orchestration provides predictable progress and prevents resource contention, making it ideal for rate-limited or quota-constrained environments.