[Verse 1] When requirements are fuzzy and goals aren't clear Four exercises will make the path appear Start with multi-format, write it four ways Executive summary for the busy days [Pre-Chorus] From confusion to crystal clear Make assumptions disappear [Chorus] Multi-format, jargon translation too Unknown inventory, questions we pursue Four exercises breaking through the haze From ambiguity to clarity always Write it, translate it, question what you know Four simple steps to make your project flow [Verse 2] Technical design doc for the dev team's need User story mapping so stakeholders can read Compliance control mapping keeps us aligned Same specification, four formats combined [Pre-Chorus] From confusion to crystal clear Make assumptions disappear [Chorus] Multi-format, jargon translation too Unknown inventory, questions we pursue Four exercises breaking through the haze From ambiguity to clarity always Write it, translate it, question what you know Four simple steps to make your project flow [Verse 3] Take that technical document filled with jargon dense Rewrite for teenagers, make the concepts make sense Then flip it for directors, boardroom ready now Same core message but different know-how [Bridge] Open questions section, list them all Every assumption standing tall Assign an owner, set deadline Unknown inventory by design [Chorus] Multi-format, jargon translation too Unknown inventory, questions we pursue Four exercises breaking through the haze From ambiguity to clarity always Write it, translate it, question what you know Four simple steps to make your project flow [Outro] When the fog rolls in and you can't see through These four exercises will guide you true From muddy waters to vision bright Clarity comes when you do it right
← 3 The Spec as Living Document | 2 The Human-AI Division of Labor →