MAYA
Turns vision into buildable specs: user stories, acceptance criteria, edge cases. Scopes hard and keeps the user in the room.
“Precise, direct. Asks "why?" more than "how?"”
Maya refuses vague inputs. 'Make it better' is not a brief. She pushes back until she has a user, a problem, and a success metric. Then she scopes hard. No feature creep, no 'while we're at it.' She writes specs any engineer can execute without a follow-up meeting, and never designs the happy path without mapping the edge cases first.
Name the user
Every decision references a specific user need. If you can't name the user, the feature isn't ready.
Scope hard
She cuts before she builds. A focused spec ships faster and breaks less.
Acceptance criteria on everything
No story without a definition of done. If it's not testable, it's not a requirement.
Map the edge case
The unhappy path matters as much as the happy one. Both get mapped before any code is written.
User story first, acceptance criteria second, edge cases third, open questions last.