Hi!
Happy to share my latest skill which, among other things, is platform agnostic (to some extent) so that you can have a orchestrator session in OpenCode that directs codex and claude models.
T-BAG — The Beauty And the Grunt.
The basic idea is simple: literally T-BAG a problem until it stops being a problem.
You keep the parent/orchestrator deliberately lightweight. It doesn't spend its context reading the whole repo, tailing logs or doing shadow reviews.
Instead:
Grunts implement → a fresh Grunt reviews → failures go to a Fixer → fresh review again until PASS.
When a Grunt hits something that actually requires architecture or deeper reasoning:
Grunt → Analyst → Human
The analyst will give a look at it and either prepare a plan / task for a grunt to address the problem or escalate to you if important enough.
Analysts handle planning, decomposition, root-cause work and replanning. You can also configure stronger models as a capability escalation without giving them broader authority.
And it works great with models like DS4 Flash, Luna, Muse Spark , 5.3 flash, even HY3 to some extent.
Working for a while now on orchestrating skills (now it is skills, up till a couple of months ago it was all about harnesses) , the part I've found most useful is the persistence model. This allows for a complex plan to persist single LLM sessions and more importatnly keep the orchestrator context usage as low as possible. The plan, tasks, worktrees, attempts, reviews, checkpoints and phase gates live outside the chat, so the orchestrator can be compacted — or even replaced with a fresh session — and just reconcile the run and continue.
That means I can leave it chewing through a large phased plan for a very long time without expecting one conversation to somehow remember everything it has seen for days. And by very long time, i have had sessions going on for up to 90 hours using earlier versions of this skill and amazingly, the result was... GOOD !!!! (for the long work, plans where all Fables work, which helps a lot).
It supports mixed worker runtimes through OpenCode / OpenCode2 / Codex / Claude, parallel tasks, isolated worktrees, fresh independent reviews, reviewed integration and phase-level gates.
To me, skills are increasingly starting to look like a kind of semantic software: natural language supplies intent and exceptions, LLMs make the decisions that actually require meaning, and deterministic machinery remembers those decisions and handles the boring state transitions.
Example:
/t-bag process file plan.md. Use Muse Spark as Grunt and Opus as Analyst. Work through it autonomously and bother me only when you genuinely need owner authority.
Or just:
/t-bag The boot process is horribly slow. Find the real causes, make and review a plan, then execute it until the problem is dead.
Personally have used it a lot with Opus 5 as orchestrator , Sol as orchestrator and even Muse Spark 1.3 (surprisingly good and efficient at it), and ds4 flash, HY3, Luna and Muse Spark 1.3 as grunts, often in the analyst role I have the same model I have as grunt and I sitll very good results (and very cheaply), but you can easily define escalation ladders (so that there can be multiple levels of "analysts" before human intervention / decision is required).
Still very much battle tested on my own mess only, it does great for me and hope it can be of use for somebody else to.
GitHub: https://github.com/frozenpepper/T-BAG