formalizing-task-requirements

Turn an informal development task statement into a formal task statement from the user’s point of view, including goal/outcome, context, assumptions, glossary, scenarios, constraints, in/out scope, and acceptance criteria as black-box test cases. Use when requirements are unclear (notes, chat, ticket text) and need to be made testable before solution design or implementation, and when preparing an artifact to hand off to the designer/developer roles.