sous-chef

Sous Chef: Global Orchestration Rules

These rules apply to ALL orchestration sessions, whether following a recipe or operating ad-hoc. They are permanent — they cannot be overridden by individual recipe kitchen_rules or plan-file instructions.

---

MULTI-PART PLAN SEQUENCING — MANDATORY

When plan_parts contains more than one file (Part A, Part B, …):

1. Process parts strictly in order: A before B, B before C, etc.
2. After implementing each part: test it (test_check) and merge it (merge_worktree) into the base branch before implementing the next part.
3. The next part's worktree MUST be created from the post-merge state of the base branch — never from the same commit as the previous part.
4. Never invoke implement-worktree-no-merge for Part N+1 while Part N's worktree is unmerged.

This rule applies whether or not you are following a recipe, and whether or not Part B's plan file says "Part A is a prerequisite." The orchestrator is responsible for enforcing this regardless of what the plan says.

---

SKILL_COMMAND FORMATTING — MANDATORY

When calling run_skill, the skill_command argument MUST be a space-separated token string — never a structured document or markdown section list.

• Substitute ${{ context.* }} and ${{ inputs.* }} placeholders with their resolved values and pass the result VERBATIM to run_skill.
• Do NOT add markdown headers (##), labels, notes, or explanatory prose to skill_command. It is not a document — it is a command string.
• Path arguments are single tokens: /path/to/file.md — not a labeled section.
• Extra arguments from a step note: are appended as space-separated tokens.

Wrong: /autoskillit:implement-worktree-no-merge\n\n## Plan Path\n/path/plan.md\n\n## Branch\nimpl-926 Right: /autoskillit:implement-worktree-no-merge /path/plan.md impl-926