Re:OpenSpec – A lightweight and configurable AI spec framework
by nullbio on Wednesday September 16, 2026 @09:58PM
(#49735546)
I just have it write a checklist file in /tmp (or a todo folder if I want to keep it), and check off items as it finishes them. Seems to work fine. Is this really needed?
[ Parent
| on HN ]
Re:OpenSpec – A lightweight and configurable AI spec framework
by broodbucket on Wednesday September 16, 2026 @11:12PM
(#49735978)
If you're writing design documentation to /tmp you're not the target audience for this kind of thing
Re:OpenSpec – A lightweight and configurable AI spec framework
by nullbio on Thursday September 17, 2026 @07:39AM
(#49739337)
No, I write design documentation to a docosaurus folder where it can actually be read as docs nicely.
Most of the time all you need is a throwaway md file to compensate for context loss and so you can loop on a spec across compaction. Once you have the spec implemented, there's usually no reason to keep it around. The code becomes the spec.
For hard constraints you have AGENTS.md, or put it in another md file. Why do I need additional software for this?
Re:OpenSpec – A lightweight and configurable AI spec framework
by trollbridge on Wednesday September 16, 2026 @10:02PM
(#49735573)
/tmp? What happens when you reboot?
Re:OpenSpec – A lightweight and configurable AI spec framework
by nonethewiser on Wednesday September 16, 2026 @11:38PM
(#49736107)
You know
Re:OpenSpec – A lightweight and configurable AI spec framework
by nullbio on Thursday September 17, 2026 @07:34AM
(#49739295)
That's the entire point. Why would I want to keep these files around forever? If you're keeping these files you're just compounding drift onto drift and making it harder for the agent. For everything else, there is git history.