The tagged-union / function-call point is where I keep ending up too. Once a config needs “one of these shapes” or “this thing with these arguments”, data formats grow conventions on top (type: keys, YAML !tags, $ref), and every consumer reimplements them.

I’ve been building Forma (https://forma-lang.com), a small typed Lisp aimed at that zone. Everything is (head args...), so a tagged value and a call are the same syntax, and you declare the vocabulary yourself:

  (job nightly-export
    :schedule "0 3 * * *"
    :retry (backoff :max 5))

job and backoff are forms you define with typed holes. The checker reports errors at the line you wrote, even after macro expansion. The output is plain JSON (or generated Effect TypeScript, but could target any language), so the app reading it doesn’t embed the language.

Unless there's context, I'm never clicking on a naked youtube link.

Are you worried google is going to hack you or something?

He was told they were never gonna give up.

Try https://www.conductor.build/

Claude Code et al. asks clarifying questions in plan mode before implementing. This will eventually extend to jira comments

You think the business line stakeholder is going to patiently hang out in JIRA, engaging with an overly cheerful robot that keeps "missing the point" and being "intentionally obtuse" with its "irrelevant questions"?

This is how most non-technical stakeholders feel when you probe for consistent, thorough requirements and a key professional skill for many more senior developers and consultants is in mastering the soft skills that keep them attentive and sufficiently helpful. Those skills are not generic sycophancy, but involve personal attunement to the stakeholder, patience (exercising and engendering), and cycling the right balance between persistence and de-escalation.

Or do you just mean there will be some PM who acts as proxy between for the stakeholder on the ticket, but still needs to get them onto the phone and into meetings so the answers can be secured?

Because in the real world, the prior is outlandish and the latter doesn't gain much.

Businesses do whatever’s cheap. AI labs will continue making their models smarter, more persuasive. Maybe the SWE profession will thrive/transform/get massacred. We don’t know.

What do you mean by eventually?

this already exists.

Seems like the best competitor to Conductor at the moment. They did a great job.

Take a look at https://conductor.build/ - they really pioneered this whole direction of using git worktrees. Cursor will soon look like their app, Opencode will soon look like their app, etc.

I tried that, I couldn't get it to authenticate properly since I need to run some commands before running claude code. I also don't like that they rolled an entire UI when the terminal UI is good enough, it's just the parallelization of workflows that needed automation. Git worktrees were launched in 2015

Have a look at https://github.com/aperoc/toolkami if you want a single, file implementation of a TUI parallel agent interface.

I think if Atlassian could really build something like Vibe-Kanban right into JIRA, it would be absolutely incredible.

Then we wouldn't need our Kanban board AND a separate board for just that.

Or I guess if these tools integrated into JIRA and suggested tickets, that could be nice.

I am a Kanban person and I use Trello. I couldn't find a Trello MCP that worked so I built https://github.com/billyjones75/cueit which is basically a Kanban board for coding agents.

You should check out their MCP server: https://support.atlassian.com/atlassian-rovo-mcp-server/docs...

I’ve been using it for months. It’s great. But it actually stopped working today (giving many 503 errors). Not sure why.

oh, and also closed source

afaict macOS only (there's a waitlist for windows and nothing for linux)

I migrated from ts-rest to Effect/HttpApi. It's an incredible ecosystem, and Effect/Schema has over taken my domain layer. Definitely a learning curve though.

I believe Effect Schema fully supports Standard Schema, the issue is that it supports much more than Standard Schema, so not all schemas will work and thus provide compile time errors.

Yes that's correct, it's more powerful but we wanted to maintain full compatibility just for the future as well. But if you're all in on the Effect ecosystem, it's quite nice.

I think the main issue is they accidentally created an incredible consumer brand with ChatGPT. They should sell that asset to World.

You should check out https://effect.website/

It might help you implement some of these ideas