Running the Spec Kit flow as a gated pipeline across Claude Code, Codex and Pi

[ltoscano]

I've been running specify -> plan -> tasks -> implement as a single workflow where each step can go to a different agent, and nothing gets committed until tests pass on the server, a second agent has reviewed, and I've approved.

The part I found most useful: when a check fails, the work goes back to the agent for correction, with a cap on attempts. Every step keeps its files as versions with a diff, so I can see what changed between the plan and what was actually built.

I packaged this as a ready-made workflow in rightcommit, an open source (Apache 2.0) self-hosted orchestrator I maintain: https://github.com/rightcommit/rightcommit

Two questions for people using Spec Kit on real projects:

1. Where do you put the human approval: after plan, after tasks, or only before the commit?
2. When requirements change mid-way, do you regenerate tasks.md or patch it by hand?