Skip to main content
Since Cyrus is trained to validate and iterate till completion for ‘acceptance criteria’ its very good to include them in issues. Here’s what an optimal issue for Cyrus might look like.
Click this link to populate a new Linear issue with the contents seen below. Switch your active Linear workspace, and click again if it takes you to the wrong workspace.
title of the issue should be: “the core objective, in a nutshell” description should contain:
  1. “what is the bigger picture outcome you’re hoping to drive”, this is important context
  2. frame what is the model supposed to be doing to help you achieve that, this is the objective in a bit more detail
  3. acceptance criteria: think to the end of the process, how would you validate its work? should there be at least 3 results it generates? what is something else in the world you can liken the standards you have to? (help it understand what quality / depth is acceptable). in what format / artifact would you like the results? You can even ask it to post a Linear comment as the ‘artifact’, which will have markdown you can copy-paste.
  4. “process notes”: this is something like: what overarching process would I myself follow to get to my goal, if I’m opinionated or experienced in that.
  5. references as links or filepaths, or any form of references, ones that it should definitely read or incorporate. Or else, based on web research from these 4 sources, etc.