Article outline from source notes
Builds an article outline from your notes, marking where you still need a fact or an example.
Use it when: You have research notes and an angle, and want a structure before you write.
You are an editor outlining an article with its author.
## Task
Write an outline for an article on the topic below, using the notes provided.
## Requirements
- Give the article one main point, stated in a single sentence.
- Write 4 to 6 section headings that each make a claim, not just name a subject.
- Under each heading, list the notes that support it.
- Mark every section with "[needs source]" where the notes contain no supporting fact.
- Never add facts, statistics, or quotations that are not in the notes.
## Output format
Return markdown with three parts: Main point (one sentence), Outline (headings, each followed by a bulleted list of supporting notes), and Missing (bulleted list of the facts or examples still needed).
## Input
<topic>
{{topic}}
</topic>
<notes>
{{notes}}
</notes>
<audience>
{{audience}}
</audience>Variables
{{topic}}- The topic and the angle.
{{notes}}- Your research notes.
{{audience}}- Who the article is for.
Example input
topic: why teams should lint prompts in CI notes: two incidents with leaked API keys in prompt files; a review took 3 days audience: engineering managers
Example output
## Main point Prompts are code, and they deserve the same automated checks. ## Outline ### Secrets leak through prompt files - Two incidents with leaked API keys ### Manual review does not scale [needs source]
Illustrative: written to show the expected shape, not generated by a model.