← ggrigo.xyz
dispatching

// orchestration skill · for humans & machines · v1.1.0

/com-center

Hand me tasks one at a time. I run them all at once. You never wait in line. SKILL

You know the worst part of handing work to an assistant? Waiting for the first thing to finish before you can ask for the second. /com-center kills that wait. You just keep naming what you need — "pull the Q3 numbers," "draft the reply to a client," "fix the broken links on the site" — and each one peels off into its own background session and starts running. Right away. In parallel.

One conversation quietly drives many at once. I take a quick look, hand each job off, and read back what comes home — keeping a running board of what's done, what's still cooking, and what each one found. You're not doing the work, and you're not babysitting it: you're calling the shots and reading the results, while the rest happens in the background and reports in as it lands.

Get the skill →

// the loop · repeated

01line it up
→
02scope it
→
03send it off
→
04report back

You add a task to the board → I take a quick look so the brief is exact → it goes off as its own background worker → I bring back the verdict and the proof, then reach for your next one.

// the promises · 7 things you can count on

01 EVERY REAL TASK GETS ITS OWN WORKER Anything with more than one step runs in the background — so naming a new task never makes you wait on the last one.
02 LOOK BEFORE LEAPING A few quick reads up front mean the worker gets a precise brief — and a precise brief comes back as a precise result, not a near-miss.
03 EACH WORKER PACKS ITS OWN BAG Workers start fresh with zero memory of our chat, so every job ships with the exact files, facts, and a clear picture of what "finished" looks like. No guessing.
04 NO TWO WORKERS TOUCH THE SAME THING Running things at once is only safe when they don't collide. If two jobs would change the same file, I run them one after the other instead of racing them.
05 LOOKING CAN'T BREAK ANYTHING; CHANGING HAS TO PROVE ITSELF While I'm just figuring out what's going on, nothing moves — investigating is read-only. When a worker actually changes something, it backs up first, tests that the change landed, and stays undo-able.
06 VISUAL WORK CHECKS ITS OWN MIRROR A worker building or fixing something you'll see opens the browser itself, takes the screenshot, fixes what looks off, and brings back the picture as proof — not a "should be fine."
07 STRAIGHT TALK, EVERY TIME A one-line verdict with the evidence behind it. "Done and confirmed" only when I watched it land — otherwise you hear "reported, but I didn't see it land," never dressed up as done. And anything sensitive stays a pointer — pointed to, never copied into a report or a synced file.

// companion · set item

/F
/fabric
Want to see it all at a glance? Opens the Fabric cockpit: the same running board, but live. Watch your jobs, commitments, and projects move in real time instead of reading them back one line at a time. The picture-window version of your list.

"You keep talking. The board keeps turning. Nothing ever sits there blinking at you, waiting."

— com-center/SKILL.md · v1.1.0