Requirements planning
A workspace for writing product requirements and acceptance criteria in a consistent, structured form. Anthony Rensfield designed and built it.
- Status
- In development
- Built with
- Go, Next.js, PostgreSQL, AWS
The problem
Requirements written as free text drift. The same need is described in different ways, wording is vague, and negative statements are easy to misread. That makes requirements hard to review, test, and keep up to date.
What we built
Authors write each requirement from defined parts, such as who it applies to and what they must do, chosen from a controlled vocabulary. The application guides the author through each part in order, so every requirement follows the same structure. Acceptance criteria are attached to the requirement they verify.
How it is built
- A Go backend holds the authoritative state. It validates each change, decides what the author edits next, saves the result, and sends updates to everyone viewing the project.
- A Next.js frontend stays connected over WebSocket, so changes appear immediately.
- Data is stored in PostgreSQL, and the application is deployed on AWS.
Where it stands
A working application under development. The screenshots show a sample project, not customer data.