What's this about?
OpenSpec tracks proposals, specs, design and tasks through explore/propose/apply/verify/archive stages, keeping coding-agent implementation tied to evolving requirements.
What exactly is spec-driven development?
Write a shared description of desired behaviour, then implement and verify against it. The document is a contract for discussion, not a substitute for executable tests.
What's the community saying?
HN 77 points, 31 comments.
- Users like a lighter process than heavier agent frameworks.
- Some question why markdown/skills need an additional CLI.
- Documentation mistakes reduce confidence despite useful workflow ideas.