Working on title based features :/ without requirements

Current project at work is going something like this. Designer / UX comes up with a basic design. Then we are expected to implement it without any proper discussion on the actual flow needed or why our how that feature is useful or requirements that is needed to implement it.

Recently, UX guy put a checkbox and a grouping icon button in a table design and told list items should be able to group. But there was never a discussion or further details on what happens in UI when list items are selected and then clicked on that group icon.

@HoloDreamer I feel you mate ... Its tough devvin like this

A friend of mine had an idea for an application that connects to a game he mods. He was going to make me CTO and I’ll get a percentage of the profits. I told him since I’m not getting paid up front that he needs to write out the requirements for me so I can do the Class Diagram and try to figure out what he wants.

I would vaguely explain to me what the application would do and that I should start there... I ended up dropping it and losing a friend because still today I have no idea what the application does.