orchestratelisted

# /orchestrate Generic orchestration skeleton: plan → issue → worktree → implementation → review → PR, with model-tiered delegation and issue-comment resumption. The **project-specific bits** (test/lint commands, commit-time gate, sensitive paths, TDD policy) come from a **project profile**, not from this file. > **Not a line-synced mirror.** A project-local skill with the same name (`orchestrate`) shadows > this one (project scope wins over global; see Step 0 guard). There is **no obligation to keep > this in sync** with any project's version — back-port *principles* only, never mechanics. A > project that needs richer, self-contained orchestration should ship its own `orchestrate` skill. > > **Subagent budget (inlined so this skill is self-contained).** Hard output-token caps (not > configurable): Opus 4.x 32,000 / Sonnet 4.x·5 64,000 / Haiku 4.x 8,192 / Fable 5 undocumented > (quality lever, not budget). Split delegated work at soft ~800 changed lines OR ~8 files OR ~5 > review axes; hard-split above 1500 lines / 12 files / 7 axes. Budget exhaustion is silent (the > final report just goes missing). For more depth read this kit's `rules/subagent-usage.md` (or > `~/.claude/rules/subagent-usage.md` if installed); if absent, use the defaults above. ## Constants - `PLAN_MARKER`: `<!-- claude-orchestrate-plan -->` — machine-readable marker embedded in issue plan comments for resumption detection. (Projects with their own `orchestrate` use their own marker; a plan created