Requirements
Requirements are pages in the project's knowledge base, written and refined in the studio.
A requirement describes what to build and why, with acceptance criteria that QA can test. It lives in the project's knowledge base, so the team, the studio, and the agents read the same page.
The flow
- Draft a requirement in the studio: the problem, the users, the outcome, and testable acceptance criteria.
- Refine it with the team. The page is versioned in the knowledge base.
- Cut tickets from it when it's agreed. Each ticket links back to its requirement.
- Pass G0: a PO/PM confirms the requirement is complete and the tickets are ready. Labeling a ticket
readyhands it to the factory.
Planned
Writing requirements in the studio is being built. Until then, write them in the knowledge base directly and open the GitHub issues by hand.
What makes a good requirement
- One outcome per requirement; split when the acceptance criteria describe several.
- Acceptance criteria a tester can check on a running preview: what to open, what to do, what to see.
- Links to the decisions and research behind it, also in the knowledge base.