Usual of tech writing - set up a false premise, answer with bad solution, and then summarily tear it to shreds. I work in an agile environment, and our ticketin

Usual of tech writing - set up a false premise, answer with bad solution, and then summarily tear it to shreds. I work in an agile environment, and our ticketing system is Jira/Confluence. And I do not see what this person is talking about. 1. Agile tickets include a 'Story', which says "As $person, I'd like to be able to do XYZ." The very ticket entails a basic line of sanity checking to prevent 'do ticket->close ticket->dont care' loop. 2. One rarer things with Agile is 'Desk Check' ( https://www.techopedia.com/definition/18825/desk-check https://www.techopedia.com/definition/18825/desk-check ). This is when a new thing by devs is done, and then they pull the designer AND qa at the dev's desk and do a sanity check on the very card, before it moves on. This solves design misunderstandings and potential QA misunderstandings/bad process before continuing. 3. Spikes are done to determine how big a major thing can be. It's a first round rough draft of 'how big is this feature, really'? The result from a spike can then be made into an epic. The epic is a way a person doing tickets can understand the big picture.