http://web.mit.edu/ssit/cis/CISRequirements.html

Super long requirements document which is just not feasible for small scale projects with a single developer or even a small team. It would take more time to gather the information for this document than to complete some projects.

https://www.atlassian.com/agile/requirements

Shorter example from Confluence (bitbucket/atlassian) - Don't have real problems with the structure of the requirements but I know from working with their software, it isn't very easy to work with to produce useful documentation. Which makes me leary of using them as a reference.

https://en.wikipedia.org/wiki/Product_requirements_document

Wikipedia page which is an overview for business project requirements. Can extract some basic attributes from this to use as a starting point but does little to answer today's question of how to quickly create project requirements for a small project.

Stack Overflow reference , has a sample : http://stackoverflow.com/questions/171653/examples-of-requirement-documents

Of course there's an IEEE spec for this : https://en.wikipedia.org/wiki/Software_requirements_specification

Software requirements specification IEEE 830

Will just copy the example over :

Purpose
Definitions
System overview[disambiguation needed]
References

Overall description

Product perspective
    System Interfaces
    User interfaces
    Hardware interfaces
    Software interfaces
    Communication Interfaces
    Memory Constraints
Design constraints
    Operations
    Site Adaptation Requirements
Product functions
User characteristics
Constraints, assumptions and dependencies

Specific requirements

External interface requirements
Functional requirements
Performance requirements
Logical database requirement
Software System attributes
    Reliability
    Availability
    Security
    Maintainability
    Portability

http://www.agilemodeling.com/essays/agileRequirements.htm

Agile Requirements Modeling - again probably more information than necessary.