post-loop-step

Execute deterministic post-loop state transitions and agent dispatches for development tracks.

Updated May 7, 2026

Search Tags:#automation #workflow #tdd #orchestration #conductor #teleoperator

Ready to run

npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill post-loop-step

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: post-loop-step
Source: https://github.com/AtaraxiaEpiphany/conductor/tree/main/skills/post-loop-step
Command: npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill post-loop-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the overhead of manual post-loop management in software development tracks by providing a code-driven teleoperator that handles state transitions, agent dispatching, and gate verification.

Core Features & Use Cases

Automated Workflow Execution: Executes deterministic post-loop steps like doc-sync, code review, and archival without requiring human intervention for every transition.
State Machine Integration: Interfaces directly with the track-state CLI to ensure atomic state mutations and consistent gate-stamp bookkeeping.
Use Case: After implementing a feature track, use this skill to automatically trigger the code reviewer, process the review results, and archive the track upon successful completion.

Quick Start

Invoke the post-loop-step skill by providing the name of the track you wish to finalize.

Frequently Asked Questions about post-loop-step

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

FAQPage Schema

How do I automate post-loop workflow orchestration in Conductor?▼

Automated post-loop orchestration in Conductor is handled by executing deterministic state transitions and agent dispatches to manage code reviews, doc-sync, and archival gates without manual intervention.

What is post-loop state transition management for development tracks?▼

Post-loop state transition management interfaces directly with the track-state CLI to ensure atomic state mutations, consistent gate-stamp bookkeeping, and audit trails for development tracks.

Do I need the track-state CLI to run Conductor post-loop steps?▼

Yes, you need the track-state CLI and the Conductor environment to maintain state consistency and audit trails when executing post-loop lifecycle steps for development tracks.

Can I automatically trigger code reviews and archival gates after a feature track?▼

You can automatically trigger code reviewers, process review results, and archive tracks upon successful completion by invoking the post-loop orchestration skill with the target track name.

What are the limitations of automating post-loop development track workflows?▼

Automated post-loop workflows rely on deterministic state transitions and require both the Conductor plugin environment and track-state CLI, limiting use outside this specific teleoperator orchestration ecosystem.