Ralph Specum Requirements

It resolves the active spec, reads any research context, and delegates the actual requirements writing to a product manager sub-agent instead of doing it itself. It then validates the output, updates progress tracking, and stops with an approval gate unless you're running in quick mode. The handoff is clean: you get user stories, acceptance criteria, and functional requirements in requirements.md, then you explicitly approve, request changes, or continue to design. It's opinionated about separation of concerns, which keeps the coordinator thin but means you need the full Ralph system for this to do anything useful.