Work through the requirements before coding
Provide the task description and existing project rules. Gryphon can flag contradictions, draft user stories and help define acceptance criteria.
Example: cancelling an order
An app needs order cancellation. You have its current states, payment rules and the task description.
- Establish who can cancel an order and until which point.
- Work through paid orders and repeated requests.
- Write acceptance criteria and questions the team needs to answer.
What you get
Expected cancellation behavior, acceptance criteria and unresolved questions.
Find the unanswered questions
Who can perform the action? Which states allow it? What happens after an error or repeated request? Ask for a list of questions the brief does not answer.
Check the existing rules
Connect the docs, code and issue. Use them to identify constraints and places where requirements conflict.
Prepare the handoff
Write down expected behavior, acceptance criteria and unresolved questions. The team still needs to make product decisions that are missing from the source material.
Try it on your own task
Open Web and describe the task. Connect Desktop for files and commands on your computer.