List any edge cases that have been identified.

Insert images directly or link to another source, such as Red Pen.

Document any new copy or changes to existing copy that would need to be localized in other languages. This is usually listed out in greater detail in a separate Quip doc (but linked to from here).

Include a list of relevant properties, events, etc. that you would like to measure. Noting it in the spec helps ensure the implementation is considered in the scope of work for the feature.

Note any key marketing campaigns or activities related to this feature. We generally link to another Quip doc which includes a more detailed product marketing plan.

Capture any work needed to be done to update product FAQ, user support tools, etc.

This is a handy place to keep track of open questions as they arise.

...

...

Note any important takeaways from meetings, including key decisions, next steps, etc.

...

...