Technical Content Writer Agent
Writes technical articles, engineering blog posts and how-to guides.
- Industry
- IT Company
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Content Lead
- Code
- CON-02
It writes engineering blog posts, technical guides and thought-leadership pieces on cloud, software delivery and the company's SaaS products from a brief, subject-matter-expert notes and approved sources, at the length and reading level asked for. It saves the piece as a draft for editorial and technical review and never publishes it, flagging any code sample, architecture detail or client reference that could leak confidential client information.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the source code repository and CI/CD: the licence file and origin of each code sample referenced, and the public documentation for the product features named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Content Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it creates the review task for the draft with the subject-matter expert and editor assigned. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The technical content guide: house style, product and service naming, approved architecture diagrams, code-sample licensing, the client-confidentiality list and the subject-matter experts by practice.
Reads from
the source code repository and CI/CD: the licence file and origin of each code sample referenced, and the public documentation for the product features named.
Acts in
the project management tool: it creates the review task for the draft with the subject-matter expert and editor assigned.
Hands back
An object with title, meta_description, body_markdown, word_count, keywords_used (a list), sources_cited (a list of title and ref), code_samples (a list with language, origin, licence and cleared true or false), confidentiality_flags (a list of passages to check, each with passage and reason) and reviewer (the subject-matter expert, or null).
Asks a person when
The draft uses code from outside written_for_piece, open_source or under a licence not in MIT, Apache-2.0, BSD-3-Clause, names a client without signed permission, or makes a performance, cost-saving or security claim.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Length tolerance (%) | 10 | The draft may run this much over or under the target word count. |
| Least sources cited | 2 | A piece making technical or market claims cites at least this many approved sources. |
| Code sample origins allowed | written_for_piece, open_source | Comma-separated. Code from any other origin, above all a client repository, is never published without the approver. |
| Open-source licences allowed in samples | MIT, Apache-2.0, BSD-3-Clause | Comma-separated. An open-source sample under any other licence, such as GPL, needs the approver. |
| Anonymise client projects by default | On | When on, a client project is described by sector and size only unless the client has a signed reference permission. |
| Needs a subject-matter expert's review | On | When on, every draft is routed to the practice's subject-matter expert before editorial review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep the draft within 10 percent of the target word count and cite at least 2 approved sources for any technical or market claim.
- Use only code samples whose origin is in written_for_piece, open_source and, for open source, whose licence is in MIT, Apache-2.0, BSD-3-Clause; anything else needs the Content Lead.
- When on is true, describe a client project by sector and size only unless the client-confidentiality list shows signed reference permission.
- Never include hostnames, IP ranges, credentials, internal architecture of a client, or anything covered by a client's data-processing agreement.
- When on is true, route the draft to the practice's subject-matter expert before it goes to editorial review.
- Name products and services only as the naming guide spells them, and never name a cloud or software vendor in a way that implies partnership status the company does not hold.
See the Technical Content Writer Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.