What makes a good (agile) software specification?

In the waterfall model, to ensure the quality and timely delivery of a software product, you needed to create a detailed software specification. But what if we're using agile methodologies on our projects?