Loading page
About this tool
Turn steps, prerequisites and screenshot notes into a help-article prompt structured by DITA information type.
A knowledge base article prompt builder converts a rough list of steps, prerequisites and screenshot notes into a structured AI prompt that produces a publishable help-centre article. It shapes the output using the OASIS DITA 1.3 information types — task, concept, reference and troubleshooting — so each article answers one reader question with the right sections, and it flags steps that are not written in the imperative mood before the model expands them. Support leads, technical writers and founders writing their own docs get a consistent article skeleton instead of a different structure every time.
Open Knowledge Base Article Prompt Builder on AltFTool — it loads instantly in your browser.
Add your input to the workspace.
Adjust the options until the result looks right.
Copy or download the output and put it to work.
Section lists come from the DITA task, concept, reference and troubleshooting topic types, not an invented template.
Every screenshot marker asks for a caption and alt text, the text alternative WCAG 2.2 SC 1.1.1 requires.
Missing menu names, limits and error codes come back as TODO(verify) markers instead of confident guesses.
Give the model four things: the topic type, the reader's expertise, the ordered steps you already know, and an explicit instruction to mark unknown details as TODO(verify). The topic type matters most — a task article and a concept article need different sections, and mixing them is the usual reason a generated article reads like filler.
Task (how do I do it), concept (what is it), reference (what are the values) and troubleshooting (why is it broken). They come from the OASIS DITA standard; troubleshooting was added as a topic type in DITA 1.3. Keeping one type per article is what makes a help centre scannable.
No. Screenshot every step only for first-time-user flows; otherwise capture just the steps where the control is hard to find or the screen changes shape. Every image you keep needs alt text, because WCAG 2.2 SC 1.1.1 requires a text alternative that serves the same purpose.
Aim for twelve or fewer. Past that, group the steps under two to four named stages so a reader who stops half-way can find their place, or split the procedure into separate linked articles. This builder flags any procedure over twelve steps and asks the model to add stage headings.