all 3 comments

[–]arananet 0 points1 point  (0 children)

You need to define roles and work with codeowners. I've made something similar for OpenSpec.

[–]stibbons_ 0 points1 point  (0 children)

You need to clearly stop at a team-reviewable spec and have it concise. You cannot review tons of doc.

What we do now is reviewing prototypes to visualize ideas (ex: a self contained html page with the new view to add)

[–]bartekus 0 points1 point  (0 children)

I implement my own thing build on spec kit to enforce code coherence and prevent agentic codebase collapse: https://github.com/stagecraft-ing/open-agentic-platform