3 ms·

I use openspec and love it. I’m doing 5-7x with close to 100% of code AI generated, and shipping to production multiple times a day. I work on a large sass app

by recroad 7mo ago

I use openspec and love it. I’m doing 5-7x with close to 100% of code AI generated, and shipping to production multiple times a day. I work on a large sass app with hundreds of customers. Wrote something here: https://zarar.dev/spec-driven-development-from-vibe-coding-to-structured-development/ https://zarar.dev/spec-driven-development-from-vibe-coding-t...

sarchertech 7mo ago
>large sass app >hundreds of customers
- recroad 7mo ago
  Large codebase. Yeah man, I have a small business, trying to grow but not easy going up against Ticketmaster.
  - sarchertech 7mo ago
    A ticketmaster competitor doesn’t sound like a huge technical challenge unless you’re operating at scale. So my first question would be why do you have a large codebase so with so few customers?
    - duskdozer 7mo ago
      He's 5-7xing code output with the help of ~100% AI. More lines. More vibes. More velocity. Rocketship emoji.
      - recroad 7mo ago
        Less vibes. In SDD you have to meticulously review your specs.
        _se 7mo ago
        Really, REALLY make no mistakes!!!
brendanmc6 7mo ago
This is a great post, thanks for sharing! Over the last couple months I fell into my own unique (but similar) spec driven workflow and couldn’t help but start building my own tooling around it. Since you’ve clearly thought so much about this I would really value any feedback / criticism / reactions you have. https://acai.sh https://acai.sh I find the added structure of yaml + requirement ids helps tremendously compared to plain markdown - https://acai.sh/writing-specs https://acai.sh/writing-specs I am still a few days away from open sourcing the stack (CLI / API & Server), plan is to gather as much feedback as I can and decide if this is worth maintaining.
reedlaw 7mo ago
This is the second endorsement I've seen today. I gave OpenSpec a shot and was dismayed by the Explore prompt. [1] Over 1,000 words with verbose, repetitive instructions which will lead to context drift. The examples refer to specific tools like SQLite and OAuth. That won't help if your project isn't related to those. I do like the basic concept and directory structure, but those are easy enough to adopt without all the cruft. 1. https://github.com/Fission-AI/OpenSpec/blob/main/src/core/templates/workflows/explore.ts#L9 https://github.com/Fission-AI/OpenSpec/blob/main/src/core/te...

by recroad 7mo ago

sarchertech 7mo ago

>large sass app >hundreds of customers

recroad 7mo ago
Large codebase. Yeah man, I have a small business, trying to grow but not easy going up against Ticketmaster.
- sarchertech 7mo ago
  A ticketmaster competitor doesn’t sound like a huge technical challenge unless you’re operating at scale. So my first question would be why do you have a large codebase so with so few customers?
  - duskdozer 7mo ago
    He's 5-7xing code output with the help of ~100% AI. More lines. More vibes. More velocity. Rocketship emoji.
    - recroad 7mo ago
      Less vibes. In SDD you have to meticulously review your specs.
      - _se 7mo ago
        Really, REALLY make no mistakes!!!

brendanmc6 7mo ago

This is a great post, thanks for sharing! Over the last couple months I fell into my own unique (but similar) spec driven workflow and couldn’t help but start building my own tooling around it. Since you’ve clearly thought so much about this I would really value any feedback / criticism / reactions you have. https://acai.sh https://acai.sh I find the added structure of yaml + requirement ids helps tremendously compared to plain markdown - https://acai.sh/writing-specs https://acai.sh/writing-specs I am still a few days away from open sourcing the stack (CLI / API & Server), plan is to gather as much feedback as I can and decide if this is worth maintaining.

reedlaw 7mo ago

This is the second endorsement I've seen today. I gave OpenSpec a shot and was dismayed by the Explore prompt. [1] Over 1,000 words with verbose, repetitive instructions which will lead to context drift. The examples refer to specific tools like SQLite and OAuth. That won't help if your project isn't related to those. I do like the basic concept and directory structure, but those are easy enough to adopt without all the cruft. 1. https://github.com/Fission-AI/OpenSpec/blob/main/src/core/templates/workflows/explore.ts#L9 https://github.com/Fission-AI/OpenSpec/blob/main/src/core/te...