A template I'd use on any side project before telling an agent to implement something: User: who is allowed to do this? Starting state: what data and permissions exist? Action: what exactly does the person do? Visible result: what should they see? Failure case: what happens if a dependency is unavailable? Evidence: how will someone else check it? An example you could run today: User: the workspace owner. Starting state: a test workspace with one ordinary member. Action: remove that member. Visible result: the owner sees a clear confirmation. Failure case: if the write fails, the screen must not say the member was removed. Evidence: check the member's access from a separate session, not just the confirmation message. The last line is the one that does the work. It makes you decide whether you're checking what a person sees or just trusting the agent's account of what it did. I'm James and I make Just Every, a collection of free MIT-licensed apps that coding agents write against promises like these. The write-up is at https://justevery.com/process and the collection is at https://justevery.com. What would you change in the six lines?   submitted by   /u/withmagi [link]   [comments]