FR version is available. Content is displayed in original English for accuracy.
Well, we got this results with it:
- Phase 2A: 67 static assertions (Python script, runs in CI)
- Phase 2B: 15 behavioral tests (live Claude Code session)
- Phase 2C: 53 generation quality checks across 3 end-to-end flows
All of these passed and the CI also passed (after a few tries).
I made it to suit my way of prompting and coding and based it off kiro's SDD management, but I want it to be publicly available and used by many people. According to claude some of the testers need to fit the following criteria:
1. Developer starting a real new project from scratch
2. Solo dev with an active side project (greenfield or partial codebase)
3. Team lead whose team uses multiple AI tools
4. Developer with an existing codebase and no written specs
5. Developer who actively uses 3+ AI coding tools
It's actually a blind test, no guiding, just try it if you can, I'd really appreciate your help.
The repo is here: https://github.com/FredAntB/Spec-Driven-Development
Discussion (2 Comments)Read Original on HackerNews
- Overall the approach is sound, to generate various levels of documents from requirements to finer grained ones
- I'm not sure if that's intended, but I got asked about four questions and then the model one shot all three documents at once, ideally you'd work on one at a time, then once you're happy generate the next level of documents
- The prompting by the model was very shallow, it didn't ask enough questions so the requirements were off. I was expecting more questions so that the model had more information to work with
- I don't think there's any versioning of documents but that would be useful
- Dispatching subagents to review the generated plans would be nice
Overall it's pretty reasonable, I can see it being pretty useful. Send me an email if you need more details.