Technical article drafter
Each month a writer researches a topic or feature and turns it into a fact-checked, long-form technical article draft for you to approve before publishing.
Saves you ~1 h / week
How it works
- Trigger
- On the “Monthly deep article” schedule.
- Job
- Sharpen, research, draft, verify the claims, edit.
- Outcome
- A sourced content draft ready to publish.
What it installs
Agents 2
-
Article Writer
Takes a topic or feature to a fact-checked deep article draft and routes it for approval.
-
Technical article drafter Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Technical article drafter quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Technical article draft
Sharpen, research, draft, verify the claims, edit, and hand off for approval.
Goals 1
-
One deep article per month
Keep a steady monthly long-form publishing cadence with verified accuracy. Success looks like: Every month, one long-form technical article draft with every factual claim sourced and verified is approved before publishing.
Skills 3
-
technical-article-writer
The technical-article pipeline: idea sharpening, titles, hook, structure, drafting, editing for developer audiences. Adapted from samber/cc-skills/technical-article-writer.
-
copywriting-hooks
Engineering long-form openings and titles across five levers, with type-fit and anti-patterns. Adapted from samber/cc-skills/copywriting-hooks.
-
copywriting-prose-creator
Shaping clear technical prose — syntax, rhythm, structure, and anti-LLM countermeasures. Adapted from samber/cc-skills/copywriting-prose-creator.
Schedules 1
-
Monthly deep article
Drafts the month's deep article on the schedule you choose. ## Professional quality control Objective: complete the recurring Technical article drafter operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. For prose, verify audience and voice against supplied examples, support every factual claim, and remove generic AI phrasing, filler, canned setup, hollow transitions, inflated language, repetitive tricolons, bullet soup, and uniform cadence. Preserve format-specific load-bearing elements such as the hook, subject line, quoted language, and call to action while making every paragraph earn its place. Reject unsupported claims or fake specificity. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.
Requirements
- Web search and fetch access for technical research — The writer uses worker web search and fetch tools to research the topic, gather sources, and fact-check claims. Until fetch access is available, it drafts from supplied notes and labels research gaps.
Setup guide
How to Draft Technical Articles With an Agent
A practical guide to researching, drafting, fact-checking, editing, and approving developer-facing technical articles.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.