Turn source material and a target audience into clear docs, help, or knowledge-base content — gather the material, outline the piece, write it section by section, then check it for clarity and gaps.
Most 'write me an article' prompts return confident filler — fluent paragraphs ungrounded in any source, padded to length, and vague where it counts. General content writing is a real job with steps: start from actual source material, write for a specific reader, structure before drafting, and check that the result is clear and complete. The code-documentation workflow doesn't fit here — it explains code, and a help article or knowledge-base page isn't code. This workflow does the content-writing job in order — gather and ground the material, outline, draft section by section, then check clarity and gaps — so the piece reads clearly and stays anchored to what's true.
Each step uses an existing NewPrompt tool, pre-filled by a matching resource. Open the resource to read it, or jump straight into the tool with the inputs ready.
Gather and ground the source material
Package the source — notes, docs, transcripts, product facts — with clear labels and grounding rules, so the writing stays anchored to what's true instead of inventing it.
Outline the piece
Break the content into an outline — the sections, their order, and what each must cover for the target reader — before writing a word, so the draft has a spine.
Write the content section by section
Draft the content in a consistent structure, section by section, grounded in the source material and written for the audience — not padded with filler to hit a length.
Check clarity, structure, and gaps
Check that the draft holds together — consistent structure, no missing context, claims grounded in the source — and flag what to fix before it ships.
Documentation, help, or knowledge-base content written from real source material — gathered and grounded, outlined, drafted section by section, and checked for clarity and missing context — so it reads clearly and stays anchored instead of padded or invented.
The AI Content Writing Workflow writes general prose — guides, help articles, knowledge-base pages — from source material that isn't code; the Code Documentation Workflow reads and explains code. Same documentation-generation capability, different material: content for readers to follow versus docs that mirror how the code works.
The Content Strategy Workflow decides what to publish and why across a program; this workflow writes one piece well — gather source, outline, draft section by section, check clarity and gaps. Strategy picks the topics; this is the writing craft once you know a specific article or page needs to exist.
The workflow is built against that: step 1 grounds the writing in your source material, step 3 writes from it rather than padding, and step 4 checks for ungrounded claims and missing context. Your judgment on accuracy and voice is still what makes it publishable.
A structured draft of documentation, help, or knowledge-base content — outlined into sections, written section by section from your source material, and checked for clarity, consistent structure, and missing context. It's a grounded draft ready for your final review and voice pass, not auto-published content; you edit and ship it.
Your source material and your reader. Step 1 packages the notes, docs, transcripts, or product facts the piece must be grounded in; the outline and draft are written for a specific target audience. Without real source, the AI pads with filler — the grounding rules in step 1 are what prevent that.
Work the four steps in order in your own AI tool: gather and ground the source material, outline the sections, draft the content section by section, then check clarity, structure, and gaps. Each step links a NewPrompt prompt and tool; you run the prompts and own the final review before publishing.
Complete build journeys that include this workflow as a stage.
The full path to an AI meeting assistant — define the use case, turn transcripts into structured notes, extract decisions and action items, classify follow-ups, write a shareable summary, evaluate accuracy, then ready it for the team.
The full path to docs people can actually navigate — plan the doc set, structure the site, write the guides and the API reference, then ship it as a coherent documentation site.
The full path to knowledge that's findable by people and AI — plan the taxonomy, structure it for search, write the articles, tag the metadata, make it retrievable, then ship it maintainable.
Generate documentation that matches the code instead of drifting from it — have AI explain what the code really does, write it up as structured docs, then validate the format holds.
Decide what to publish and why before you write a word — set the business goals and audience, map needs to topics, brief the priority pieces, then turn it into a content plan you publish against.
Organize a site so people and crawlers find things — inventory the content, group it into a real hierarchy, design the sitemap and navigation, then document the information architecture for the build.