Sous Chef: Global Orchestration Rules

Enforce global orchestration rules for multi-part plan sequencing and worktree management.

5|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill sous-chef-global-orchestration-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Sous Chef: Global Orchestration Rules
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/sous-chef
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill sous-chef-global-orchestration-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces mandatory, global rules for orchestrating development tasks across all AutoSkillit sessions, ensuring consistency and preventing common errors.

Core Features & Use Cases

  • Multi-Part Plan Sequencing: Guarantees strict, sequential processing of plan parts with mandatory testing and merging between steps.
  • Worktree Management: Dictates the correct usage of retry-worktree versus re-invoking implement-worktree-no-merge to preserve or restart progress.
  • Audit Implementation: Provides clear guidelines for using audit-impl to accurately scope changes within multi-group pipelines.
  • Plan Output Parsing: Defines the precise method for interpreting and acting upon plan_parts= output.

Quick Start

Ensure all multi-part plans are processed strictly in order, testing and merging each part before proceeding to the next.

Frequently Asked Questions about Sous Chef: Global Orchestration Rules

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

FAQPage Schema
How do I enforce strict sequential execution in a multi-part development workflow?

Multi-part plan sequencing guarantees strict, sequential processing of plan parts by enforcing mandatory testing and merging between steps before proceeding. This ensures deterministic task execution and robust error handling during complex development cycles.

What is the correct way to manage worktrees when restarting or preserving progress?

Worktree management dictates using retry-worktree to preserve existing progress versus re-invoking implement-worktree-no-merge to restart. This prevents common errors and maintains robust state management across orchestration sessions.

How do I audit implementation changes accurately within multi-group pipelines?

Implementation auditing provides clear guidelines for using audit-impl to accurately scope changes within multi-group pipelines. This ensures strict adherence to procedural execution and verifies deterministic task completion.

How does plan output parsing handle multi-part plan sequencing?

Plan output parsing defines the precise method for interpreting and acting upon plan_parts= output. This enforces global orchestration rules, ensuring mandatory sequential processing, testing, and merging of each plan part.

When do I need global orchestration rules for my development process?

You need global orchestration rules for development workflows requiring strict adherence to procedural execution and state management. They enforce consistency across all sessions, preventing common errors during complex multi-part plan sequencing and worktree management.