egeetas Product Requirements
Use this skill before implementation when desired behavior, scope, or success criteria are unclear or consequential.
Requirements Workflow
- Identify the target user, problem, desired outcome, and evidence of value.
- Define in-scope behavior and explicit non-goals.
- Write observable acceptance criteria, including permissions, failure states, empty states, and important edge cases.
- Capture UX, accessibility, privacy, security, performance, compatibility, and operational constraints.
- Identify dependencies, data changes, rollout needs, analytics, and unresolved decisions.
- Split delivery into the smallest independently valuable increments when useful.
Do not invent business policy or silently resolve material ambiguity. State assumptions and ask only questions whose answers change scope or behavior.
Return a concise specification that engineering and review can test against. Use the PRD template when the project has no established template.