launch-article

name	launch-article
description	Write a launch article that explains a new product, feature, project, or release to an unfamiliar reader through problem, capability, proof, examples, limitations, availability, and next action.

Launch Article

Use when a launch needs more depth than a short announcement or social post.

Procedure

1. Define the audience, what is genuinely new, why it matters now, availability, and the strongest evidence that the launch works as claimed.
2. Open with the user problem or meaningful change rather than internal development chronology.
3. Explain the capability through concrete workflows and examples before listing secondary features.
4. Show proof with screenshots, demos, benchmarks, architecture detail, customer evidence, or repository artifacts appropriate to the audience.
5. Explain important tradeoffs, limitations, prerequisites, compatibility, or rollout boundaries so readers know what is actually available.
6. Include enough technical or implementation detail to establish credibility without making the article unreadable to the intended audience.
7. Verify every current claim, version, metric, link, and availability statement immediately before publication.
8. End with a useful next action such as try, install, read docs, watch the demo, or follow the project.

Decision rules

• Write for people discovering the work now, not an audience assumed to have followed the build.
• Demonstrate the result instead of narrating how hard the work was.
• Do not hide meaningful limitations inside footnotes.
• Current availability and version claims require current verification.

Quality gate

The article is ready when a stranger can understand the problem, capability, evidence, limitations, and availability; claims are current and verifiable; examples show the product doing real work; and the next action is obvious.