The 2 Requirements for Squad work Inclusion in RefApp

By 2025, we’ve now seen that Squads who do these two things have more successfully adopted features and less post-release chaos:

1. Docs: Help others know how to configure the feature. This will help prevent your squad contributors from being inundated with basic questions post-release; and, members are more likely to help you maintain the feature if they can use it!

   1. MVP template here____

   2. Example here_______ (we encourage using the README for dev/config docs; for end-user guidance, please use the Wiki).

   3. Example here of how to use a free AI LLM to write some minimum docs_____.

2. Testing: Manual testing has been done by squad members. Ideally automated tests (eg E2E tests) have been written for, at least, happy path. This is so important because (1) more people can help contribute to the squad to help with testing (just ask!); and (2) the world-wide community counts on work in the RefApp meeting a basic level of trust-worthy-ness.

Let’s work together! If your squad is struggling with either of these, don’t be shy or embarrassed. You can:

• Ask for help in the weekly O3 Squad calls - there may be people who

• Bring specific questions to the daily O3 Dev Coffee Chats (e.g. “How would we write a unit test for this?”)