Orka
An autonomous SDLC orchestrator: take a GitHub issue, interrogate it, plan it, and open a tested pull request — with human approval kept explicit.
The code is private for now; the loop is exactly what it runs.
Orka is an experiment in taking the whole delivery loop, rather than the coding step, and handing it to agents. The first product loop is deliberately narrow:
- ingest a GitHub issue
- validate the requirements
- ask clarifying questions when they’re underspecified
- plan the implementation
- generate a tested pull request
- stop and ask for an explicit approval on anything risky
Rails 8, Sidekiq, Postgres, Hotwire, RSpec.
- AI must never assume missing requirements.
- High-risk changes require founder approval.
- Every agent action should be observable, explainable, and reviewable.
- Prefer small pull requests and incremental commits.
- All agent handoffs go through one shared payload — no direct agent-to-agent calls.
Requirement readiness report
Summary · user story · acceptance criteria · clarification questions · readiness score 0–100 · risks · approval gates · recommended next agent
The interesting part isn’t step 5. Generating code is the part that already works. The parts that decide whether the loop is usable are steps 2, 3 and 6 — whether the system can tell that a ticket is underspecified before it writes anything, and whether a human stays genuinely in the loop where it matters instead of nominally in the loop everywhere.