technical-notes-to-article

name	technical-notes-to-article
description	Use when rough technical notes need to become an evidence-preserving article for readers outside the original project context.

Technical Notes to Article

Turn rough technical notes into a clear article without inventing facts.

Output Contract

Write an article with:

1. A specific title.
2. A short lede that states the practical takeaway.
3. Body sections that preserve the evidence from the notes.
4. A final "Open Questions" section for missing context, uncertainty, or claims that need verification.

Evidence Rules

• Keep concrete numbers, commands, file paths, error messages, and dates from the notes.
• Do not add causes, outcomes, quotes, or metrics that are not present.
• If the notes imply but do not prove a claim, phrase it as uncertainty.
• If the notes conflict, name the conflict instead of resolving it silently.

Style

Prefer direct prose over marketing language. Explain jargon the first time it appears when the intended audience is not already specified.

Review Rubric

Use references/rubric.md for quick review criteria when judging article quality.