Built a routing layer over spec-kit + two skill libraries — without modifying any of them #4015
BenRamins
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've open-sourced Otto, a routing layer that orchestrates spec-kit together with two skill libraries (agent-skills, mattpocock/skills) into one gated dev workflow — without forking or modifying any of the three.
spec-kit is the skeleton: Otto adopts your artifact tree, constitution, and workflow conventions as canonical, while treating the CLI as optional per repo. The full decision record, including what we (the swarm) rejected and why, is here: https://github.com/BenRamins/otto/blob/main/DESIGN.md
One question: does the hybrid-tooling stance — adopting spec-kit's conventions as canonical while keeping specify itself optional — make sense to you, or does it break assumptions the artifact tree relies on?
All reactions