The spec is the easy part.
Spec-driven development automated authoring intent. But intent was never where projects die. They die afterward — on the run.
A generation of tools takes you from constitution to plan, to tasks, to guided implementation. It is useful, and it is solved. The problem is that the last gate of those tools closes at merged code. Nothing afterward on real traffic, threat, drift, or the handover to the team that inherits it.
And that is exactly where the number everyone keeps citing lands: ~95% of generative-AI projects stall before they hold in production. Not because of the model — because of the post-deployment gap: real data, real permissions, existing pipelines, governance, evaluating a non-deterministic behavior. The market has already named the people who fix this: the Forward Deployed Engineer, 2026's most-wanted enterprise-AI role (postings up sharply, nine-figure commitments from the major vendors). An FDE does not write a flawless spec; they put the system into production against real data and real permissions, and keep it alive.
What "the run" actually demands
Four things the spec does not cover, and no prompt fixes:
- A gate you own — and can re-run. Deterministic, zero-LLM, not jailbreakable by injection: same code, same verdict, byte-for-byte. You demo it; you don't describe it.
- Governance from day zero. Threat model, evaluation rubric, observability, cost cap — wired on the first commit, not after the first incident.
- No lock-in. The model and the runtime are swappable adapters behind a port. The thing you depend on must never be the tool.
- Evolution on evidence, and transmission as a deliverable. Complexity is added on an objective trigger, every change is a dated ADR, and the team runs the system without you.
Where runward stands
runward is not a better spec tool. It is an agentic-delivery framework — built on the FDE method — that begins where spec-driven goes quiet: govern, ship, run, hand off. Bring your spec (Spec Kit, OpenSpec, or in-house): it becomes the input of framing, and the gates continue after the merge.
A spec is a promise. runward is how you keep it.
Install: npx runward init
The repository on GitHub · All news
← All news