Replies: 1 comment 1 reply
-
|
The Plan → Implement → Review → Quality Gate pipeline is solid. One thing that makes these stages more reliable is giving each one a different instruction shape, not just a different task description. Plan stage wants a role that reasons about architecture, with constraints that prevent premature implementation choices. Implement stage wants a constrained coder role with a specific output_format so Review can parse it mechanically. Review stage needs a different role entirely, one that critiques rather than generates. Free-text prompts per stage tend to blur these distinctions over time. I've been building flompt for exactly this, a visual prompt builder that decomposes prompts into 12 semantic blocks (role, constraints, output_format, chain_of_thought, etc.) and compiles to Claude-optimized XML. Pipeline stages with typed block templates produce more predictable handoffs than prose. Open-source: github.com/Nyrok/flompt |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey!
I've been building LaneConductor — a workflow engine and Kanban dashboard that supports and extends the conductor
file/folder format.
It adds:
Currently using it locally but have a design for remote execution with a distributed architecture.
Running on Linux/Ubuntu — should work on WSL as well, though not tested.
Compatible with the existing conductor folder structure (conductor/tracks/NNN-slug/) so it works alongside the
standard Gemini CLI conductor pattern.
Would love feedback from the community — especially on file format compatibility and whether this aligns with
the direction you're taking the conductor pattern.
It's open source and I'd love to keep it aligned with the conductor path.
https://github.com/meller/laneconductor
https://laneconductor.com
Beta Was this translation helpful? Give feedback.
All reactions