A little thought on my SDD

[windfallsheng]

https://github.com/windfallsheng/SpecCore-ts How about my SDD framework? Will it be good to combine with the actual project development? I need your opinions and support, thank you!

[B2F]

What value does it bring which is not already covered bby OpenSpec, Bmad etc ?

[windfallsheng]

Thanks for the honest question — it's the right one to ask.

Short version: OpenSpec (and similar tools like Bmad/Gherkin/BDD frameworks) focus on specifying APIs and behaviors. SpecCore is a full-lifecycle SDD (Spec-Driven Development) framework — it spans from requirement analysis, through multi-platform task decomposition, to actual code skeleton generation.

Concrete differences:

Real example (open source in the repo):
`
cd examples/task-management
speccore init
speccore import --project=task-api --path=./src --type=backend
speccore iteration create --name=Q3
speccore new-task --name="任务CRUD" --platforms=web --type=feature
speccore execute --all --force

→ Generates: Controller.java + Service.java + Repository.java + TaskList.vue

alongside REQ.md + TECH.md + TASK.md + API_CONTRACT.yaml

`
What I'd love feedback on: Does combining specs + generated code + bidirectional sync actually reduce the "spec rot" problem (where specs become outdated the moment coding starts)? That's the core hypothesis I'm testing.

Would appreciate your honest take — especially from someone familiar with OpenSpec's strengths.

[B2F]

Specs rots is not a problem, context is reread each time a new prompt requires it, we never rely solely on specs, specs is a driver for intent, if any conflicting ideas were detected in between specs / code / prompt, the LLM (at least any decent coding llm like codex, sonnet etc) would most likely report it to the user for validation, in my experience it was always reported cleanly. In any case in a real world browfield project you should not expect to maintain full written doc of the whole project, the code document itself, specifications are rather for documenting user intent as far as I understand.

When you write "it spans from requirement analysis, through multi-platform task decomposition, to actual code skeleton generation.", this seems very similar to openspec workflow of EXPLORE -> PROPOSE -> APPLY -> ARCHIVE.

[clay-good]

Thanks for sharing it, and closing here — this is a discussion board for OpenSpec itself, so a review of a separate SDD framework isn't something this repo can act on, and @B2F's question about what it adds over existing tools went unanswered.

Two better homes for it:

• awesome-openspec — the community list of OpenSpec-adjacent projects and schemas
• A Show and tell post here, if you build something that composes with OpenSpec (a custom schema, a skill, an adapter). Those are very welcome.

No hard feelings intended — good luck with SpecCore.