I liked the screen_detail.pdf, though I will suggest an improvement or two …
* de-prioritise the “Key:” box … shift it to the bottom corner, where it can be filled in last of all, rather than getting in the way of the linguistic thinkers who might be inspired by the other three “specifications” boxes (business requirements, functional requirements, user intentions).
* de-prioritise the “Screen Number” field … really unnecessary bit of administrivia.
* question: is the “Business Requirement” box for specifying the business purpose of the screen, or is it for inventorying what will be needed to fulfill the design (eg. back-end requirements)?
Petafloptimism 
I liked the screen_detail.pdf, though I will suggest an improvement or two …
* de-prioritise the “Key:” box … shift it to the bottom corner, where it can be filled in last of all, rather than getting in the way of the linguistic thinkers who might be inspired by the other three “specifications” boxes (business requirements, functional requirements, user intentions).
* de-prioritise the “Screen Number” field … really unnecessary bit of administrivia.
* question: is the “Business Requirement” box for specifying the business purpose of the screen, or is it for inventorying what will be needed to fulfill the design (eg. back-end requirements)?