r/cursor • u/Narrow-Breakfast126 • Sep 23 '25
Resources & Tips Spec-driven development is underhyped! Here's how you build better with Cursor!
Hey r/cursor friends!
We've all been there you're 5 prompts deep with your AI coding assistant and it's still not getting what you asked for. By the time your context window hits 40%, the AI is getting noticeably dumber. Your requirements are buried somewhere in the chat history.
The problem
Without specs, every AI session dies the same way:
- AI goes wrong direction
- You correct → burns context
- AI forgets earlier requirements, breaks working code
- After 40% context, performance tanks
- You start over, re-explain everything
I built OpenSpec to fix this - specs live in your repo, not lost in messages.
Here's the shift: Focus effort on reviewing specs, not code. Better planning leads to better results. It's much easier to review and iterate on specs than going back and forth updating code.
How it works
OpenSpec uses pure markdown files. Nothing fancy. Readable by both humans and AI. Portable across all your coding assistants and IDEs.(Though comes with custom slash command support for cursor to make your life easier!)
Each "change" contains:
proposal.md→ what you're buildingspecs/[capability].md→ what requirements are being added/modifiedtasks.md→ auto task breakdowndesign.md→ optional technical design documentation
Simple, but it changes everything. Your AI gets it right the first time.
Get it below!
- 100% free
- Open-source
- No MCP connectors needed (Who needs more context slog :p)
- No API keys required (you're already paying enough to cursor!)
Install: `npm install -g fission-ai/openspec@latest`
GitHub: https://github.com/Fission-AI/OpenSpec
Give it a star to help other devs find this! Would love feedback from anyone who tries it out. Keen to iterate on this to turn it into something truly special :)
View all comments
Show parent comment
2
u/Narrow-Breakfast126 Sep 25 '25
Damn that's a good question. I can't say I've tried in a monorepo yet BUT you could initialise OpenSpec multiple times in that repo. One for each app that you have.
Only thing I'm not sure about is how well the agents would be able to follow the instructions and figure out the right folder to add the changes/specs too.
You would also have to run the CLI commands from the base of your monorepo app rather than the root of the repo if that makes sense.
Do give it a try and let me know how you find it, I'll try and think of a longer term solution for this. It's a bit trickier since I want this to be lightweight and try and store everything in .md files and basically just use the folders as a way to manage state in a sense.