u/the-tiny-prince

I use Linear for everything. The problem was that after I wrote an issue, the rest of my workflow was pure chaos — some Claude Code sessions, some copy-paste, some "I'll just vibe this one out." Every issue followed a different path to done and I had no consistency across the team.

So I built Workbench: a mono-repo template that plugs into Linear and runs a structured pipeline on every issue.

https://preview.redd.it/owvqj3fbxl2h1.jpg?width=1280&format=pjpg&auto=webp&s=c3dcd063de0ec97be5b2a04ad0f7d1a5334c0608

How the Linear integration works:

The pipeline reads issue labels to track stage. When you run /implement FOO-123, it checks the current label — if it's research, it skips ticketing and picks up from there. Each stage updates the label as it completes, so the issue is always sitting at the right status. You can stop mid-pipeline, come back next week, and /implement FOO-123 resumes exactly where you left off.

The full flow:

• /ticket — Q&A with you about scope, boundaries, acceptance criteria. Writes a structured ticket doc and labels it ticket.
• /research — Scours the codebase for relevant files, patterns, and dependencies. Labels it research.
• /plan — Produces a phased implementation plan with testable "done when…" statements. Labels it plan.
• /execute — Implements each phase sequentially, tracks deviations. Labels it execute.
• /review — Validates the diff against the plan. Pass/fail gate. Labels it review.
• /commit — Atomic commits with conventional messages and Linear issue trailers. Labels it done.

Each stage is a separate sub-agent with a specific prompt and isolated context. Reviewer has no idea what Executer was thinking — it just sees plan vs diff. No rubber-stamping.

The config lives in .workbench/settings.yml:

project_management: linear

That's it. Set it once and every slash command talks to Linear.

It's currently built for OpenCode. Claude Code support is next on the list. There's also GitHub Issues support if you're hybrid.

https://github.com/workbench-codes/workbench

Curious how other Linear users are handling the handoff between "issue written" and "code shipped." Are you using any automation between Linear and your AI tools, or is it still manual copy-paste? Anyone tried wiring up Linear webhooks to trigger agent runs?

About a month ago I realized I was spending the first 10 minutes of every AI coding session doing the same thing: explaining the project layout, which conventions we use, what issue we're working on, where to find the auth module. Again.

At some point I wrote a markdown file with all of it. Then that file got stale. Then my teammate's file was different from mine. Then our CI pipeline started failing because the agent on his machine had different linter rules than the agent on mine.

https://preview.redd.it/cutbj9r3wl2h1.jpg?width=1280&format=pjpg&auto=webp&s=1c4f076c827dbcfb82fdd342090cad70ba4ec910

So I built Workbench. It's a mono-repo template — you clone it once, it wires your actual project repos in as git submodules, and you get a standardized dev environment that both humans and AI agents share.

The core idea is a pipeline of slash commands:

/ticket → /research → /plan → /execute → /review → /commit

Each step is a separate sub-agent with a specific job. Planner plans. Executer executes. Reviewer reviews. They don't share a context window, so Planner doesn't whisper sweet nothings to Reviewer — Reviewer just sees the plan vs the actual diff and either passes or fails it.

Currently works with OpenCode. Linear and GitHub Issues as project management backends. There's a CLI (workbench --init) that walks you through setup and a sync command for pulling updates when the template improves.

https://github.com/workbench-codes/workbench

What I'm wrestling with right now:

• The pipeline works but I don't have good metrics yet. "It feels faster" isn't a number.
• OpenCode-only is limiting. Claude Code support is next but I'm still figuring out how to cleanly abstract the agent layer so slash commands aren't tied to one tool.
• The sync mechanism (workbench --sync) pulls managed files from the source repo, but I have no way to handle merge conflicts if someone customized their local commands. Right now it just overwrites.

Would love honest feedback from anyone who's tried to structure their AI coding workflow. What's your setup look like? Anyone else fighting the configuration drift problem across a team? Roasts welcome — it's early and I'd rather hear what's broken now than six months from now.

I'm running a workshop in Sydney (Stone & Chalk, Haymarket) for people who aren't technical — founders, operators, anyone who wants to get their first AI agent or automation up and running without needing to code.

Getting that first agent set up and finding the right foundation can be a real challenge for non-technical people, and I want to make it approachable.

If anyone's done something similar or has tips on making AI accessible to a non-tech audience, I'd love to hear them!

I'm running a workshop next month to help non-technical founders get their first Hermes agent or automation up and running. The goal is to take someone from zero to having a working agent they actually understand.

I've found the initial setup and finding the right foundation is the hardest part for non-technical people — way more than the concepts themselves.

For those who've taught AI agents to beginners: what worked? What did you wish you knew before your first workshop? Any pitfalls to avoid when the audience can't fall back on terminal skills?

I'm running a workshop in Sydney (Stone & Chalk, Haymarket) for people who aren't technical — founders, operators, anyone who wants to get their first AI agent or automation up and running without needing to code.

Getting that first agent set up and finding the right foundation can be a real challenge for non-technical people, and I want to make it approachable.

If anyone's done something similar or has tips on making AI accessible to a non-tech audience, I'd love to hear them!

I’m planning a workshop in Sydney for people who aren’t tech-savvy to help them get their first Hermes agent or automation up and running. I reckon getting the agent set up for the first time and finding the right foundation can be a real challenge for non-technical founders. It’s going to be my first Hermes workshop, so I’d love to hear any tips you might have