This weekend it also helped me a lot. My fiber Internet has been down since Friday, and tethering from my phone limits the throughput and bandwidth I can use for heavy development. I was able to do a fair amount of work on a new project using the cloud offering, without burning through my mobile data 😆

12,000 LoC 😮

All from this prompt:

review the PRD in plans/PRD.md and proceed to implement. Always follow the rules in docs/frontend-rules.md and docs/backend-rules.md

I'm loving spec-driven development 😄

This is great! We were thinking of maybe doing a webinar/blog thing on spec driven development. If you’d be interested in having a chat about it sometime that could be fun (no worries if you’re busy)

Yes, I love that idea 😃

Great! Maybe @gentle-apple-32922 or @elegant-branch-54423 would be interested in discussing some details

Wow 🤩 Sounds awesome 🙌 I'll send a DM with a calendar so we can chat later 👍 ty

do you have the PRD public somewhere, @echoing-garage-24541? What other additional meta-context do you maintain? I drafted a bunch of these kinds of files, to help keep alignment: https://gitlab.com/deposition.cloud/apps/relay/cli/-/tree/main/docs?ref_type=heads then I ask it to evaluate progress against the overall product vision, and rate the current code base on new threads, and its output I wanted it to keep to some principles like "self-hostable" and "least surprise UX", and so every once in a while it's self-reflecting on its output and justifies a design decision to be consistent; otherwise it fires off random corporate principles which I care not about like "moats" etc.

I usually don't commit plan files to source control, but in this case I did because I needed to use the cloud app and I've been having issues with attachments. https://github.com/kumanday/OmniLearn/blob/main/plans/PRD.md I've tried a variety of strategies and formats, and lean toward "less is more" when possible - especially for 0-1 bootstraps. The main thing I didn't incorporate in this case, which I am usually inclined to do, is a test-driven development approach.

oh, I tried TDD/BDD workflow, felt a bit slow, than landed on: https://gitlab.com/deposition.cloud/apps/relay/cli/-/blob/main/docs/testing.md?ref_type=heads which appears to be enough for it to draft both the code and the tests in one go, and keep them segregated somewhat correctly (sometimes mixes integration tests with e2e tests, but I think that's just the industry calling things differently in different communities; so it's confused like everyone else, heh)

Yes it can be hit or miss, also dependent on the agent. In Windsurf I had to steer it away from creating ad-hoc tests in the root dir in favor of maintaining an official test suite. It seems like an important feedback loop to let the model know about syntax errors, parameter name mismatches, etc.