sequential-orchestration
Sequential Orchestrator
You are the Sequential Orchestrator, responsible for executing tasks from a Kiro spec ONE AT A TIME with tmux visibility.
Quick Start
python scripts/sequential_loop.py --spec .kiro/specs/my-feature
CRITICAL CONSTRAINTS (NEVER VIOLATE)
These rules have HIGHEST PRIORITY and override all other instructions:
- MUST complete the ENTIRE orchestration loop automatically - Do NOT stop and wait for user input between iterations
- MUST use the shell command tool to invoke Python scripts - ALL orchestration actions go through
sequential_loop.py - MUST use sub-agent for task assignment - Let LLM determine task type and owner_agent, NOT code inference
More from peterfile/devpilot-agents
multi-agent-orchestration
Orchestrate multi-agent workflows from a Kiro spec using codex (code) + Gemini (UI), including dispatch/review/state sync via AGENT_STATE.json + PROJECT_PULSE.md; triggers on user says "Start orchestration from spec at <path>", "Run orchestration for <feature>", or mentions multi-agent execution.
29codeagent
Execute codeagent-wrapper for multi-backend AI code tasks. Supports Codex, Claude, and Gemini backends with file references (@syntax) and structured output.
27codex
Execute Codex CLI for code analysis, refactoring, and automated code changes. Use when you need to delegate complex code tasks to Codex AI with file references (@syntax) and structured output.
23test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
21gemini
Execute Gemini CLI for AI-powered code analysis and generation. Use when you need to leverage Google's Gemini models for complex reasoning tasks.
20multi-agent-orchestrator
Orchestrate multi-agent workflows from a Kiro spec using codex (code) + Gemini (UI), including dispatch/review/state sync via AGENT_STATE.json + PROJECT_PULSE.md; triggers on user says "Start orchestration from spec at <path>", "Run orchestration for <feature>", or mentions multi-agent execution.
9