mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-11 10:43:10 +08:00
be536c1a3e
tdd.md, e2e.md, and orchestrate.md in legacy-command-shims/commands/ still carried their full pre-shim command bodies concatenated below the shim headers: a stray '})' and orphaned code fence in tdd.md, leftover Playwright test bodies plus a foreign project-specific 'PMX-Specific Critical Flows' section in e2e.md, and orphaned report-template fragments in orchestrate.md. The trailing bodies also contradicted the shim headers by claiming the commands invoke agents directly. Truncate each file at the end of its Delegation section. The other nine legacy shims are clean 20-23 line shims and are untouched.
1021 B
1021 B
description
| description |
|---|
| Legacy slash-entry shim for dmux-workflows and autonomous-agent-harness. Prefer the skills directly. |
Orchestrate Command (Legacy Shim)
Use this only if you still invoke /orchestrate. The maintained orchestration guidance lives in skills/dmux-workflows/SKILL.md and skills/autonomous-agent-harness/SKILL.md.
Canonical Surface
- Prefer
dmux-workflowsfor parallel panes, worktrees, and multi-agent splits. - Prefer
autonomous-agent-harnessfor longer-running loops, governance, scheduling, and control-plane style execution. - Keep this file only as a compatibility entry point.
Arguments
$ARGUMENTS
Delegation
Apply the orchestration skills instead of maintaining a second workflow spec here.
- Start with
dmux-workflowsfor split/parallel execution. - Pull in
autonomous-agent-harnesswhen the user is really asking for persistent loops, governance, or operator-layer behavior. - Keep handoffs structured, but let the skills define the maintained sequencing rules.