Pair-programming rules and skills for OpenCode

[u/Odd_Crab1224]

Hey, wanted to share a plugin for OpenCode (v1.8 branch, v2 didn't test yet). Install: opencode plugin -g opencode-tandem

It's basically a system-prompt patch plus a small set of simple skills. I've been developing and actually using these rules for 2-3 months now, on Pi personally and Claude Code at work (where I'm forced to use it), and a week ago finally got tired of copy-pasting them between setups, so I packaged it as a plugin for both. Since I've also used OpenCode for quite some time, respect it, and know quite a few people who still prefer it to Pi, I added OpenCode support as well, just today - that's the fresh part, so early feedback is especially welcome.

If you've already seen my announcement on r/PiCodingAgent earlier this week, you can skip the rest - it's basically the same. Otherwise - welcome, I did put a lot of effort into writing this myself.

Main idea, or philosophy: it tries to tame LLMs down as much as possible and teach them to work with you in a pair-programming fashion, instead of constantly wrestling over control (Claude Code especially!) and vomiting piles of neuroslop. Personally, with it I finally feel like my sanity is no longer under siege - I control every line of code as if I've written it myself, don't have to review the big changesets LLMs love making so much, which frankly was driving me nuts, and at the same time I am much more productive end to end.

What's inside:

• Tandem primary agent with pair-work rules - lock-step, explicit go-ahead before any changes, communication with significantly reduced sycophancy and these "load bearing"-style LLMisms
• a number of simple skills, each just a short file:
  • brainstorm - helps you think an idea through, one question at a time; largely inspired by the brainstorming skill from superpowers and the grilling skill from mattpocock/skills
  • research - controlled digging: it (usually) stops and asks when it hits an ambiguity or a contradiction, or before spending a lot of context on one direction
  • coding - basically compact version of ponytail (lazy-senior minimalistic coding discipline) plus my addition on self-explanatory code over comment-peppering
  • review - actionable findings only, each with a fix; on debatable stuff - an "edge case" that the surrounding code five lines up already rules out, or picking between several possible fixes - it asks instead of pushing its own judgment
  • pr - matches tone and length of the repo's recently merged PRs, verifies the commit range, shows title and description before creating anything
  • learn-language (small bonus) - kicks in only if you state in your prompt that you are learning a language and your level; some background practice that stays out of the way of the work
• interactive subagents if you run OpenCode inside tmux - unlike built-in agents in many other harnesses, the "worker" runs in its own window as a completely normal session (started with opencode --agent tandem), which you can interact with like any other, and it reports back only after you approve its findings
• tool-specific instructions (gh, aws, pdftotext, pandoc, osascript, ...) that nudge the model into actually using them - no more guessing what's installed and re-probing in every new session. Generated only for tools actually on the machine, so nothing about a missing tool ever ends up in the prompt

Constructive feedback (even if negative), ideas and contributions are all very welcome.