Decision outline
Turn one buyer question, a product, a reader, and a constraint into an explainer outline with a yes, a tradeoff, and a no.
What is in the decision outline?
A markdown skeleton: the short answer, who it is for, a definition, the tradeoff, a “not this” section, and a next step. It uses the four facts you type. It does not invent product claims.
Fill all four fields to build the outline.
How to use it
Write the question the way a teammate would ask it.
Name a real constraint: team size, an existing tool, a deadline. “Anyone” is not a constraint.
Replace each prompt with a sourced sentence. Delete a heading you cannot fill.
The short-answer section should be pasteable into chat on its own.
Questions
Will this write the article?
No. It holds the shape so the no and the tradeoff do not get squeezed out by features.
What if I have two questions?
Make two outlines. One URL should answer one question.
Can I change the headings?
Yes. Keep a place for the boundary and the no, whatever you call them.