Spec-Driven Development for Data Practitioners In the next edition of ☕ Kedro Coffee Chat 🔶, @Rashida Kanchwala will explore spec-driven development and how OpenSpec can be combined with Kedro to build reliable, well-defined data workflows. 📅 When: 08 May, 1 PM (GMT+1) youtube YouTube: linkedin LinkedIn: https://www.linkedin.com/events/7458142146634698752/ 📣 These sessions are public and open to everyone. Join us live or catch the recording afterwards.

Thanks a lot @Rashida Kanchwala and @Sajid Alam, it was very interesting and I had not heard of OpenSpec. I was a bit late to ask any question, hope it's OK to ask one here! Would you push openspec folder to git? As you mentioned, it includes all the history of specs so there would be some benefit of having all future contributors (human or agent) having access to it. But in practice, before coding agents, we were sometimes writing specs, but I feel like most project would have it on separate repos or tools (thing like confluence or notion) to avoid the clutter. What's your opinion?

@Guillaume Tauzin definitely. In my view, it makes most sense for it to live alongside your code in the GitHub repo. At the moment, the OpenSpec page still mentions that “OpenSpec for teams” is in development. We’ve been considering it for the Kedro team as we build out new features as well. That said, some open source teams (like ARK) are already using it and seem to be finding it really valuable. Here’s a link to ARK’s repo with OpenSpec: https://github.com/mckinsey/agents-at-scale-ark/tree/main/openspec

Interesting! Thanks a lot :)