Blog Writer
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Turn an approved content brief and evidence set into an authored article with a clear reader promise, defensible claims, and publication-ready structure.
Use When
- Draft or substantially revise a blog post, article, tutorial, opinion piece, case study, or long-form guide.
- Convert an approved topic and evidence pack into publishable content.
Do Not Use When
- Use
blog-idea-generator when the task ends at topic options, angles, or a content backlog.
- Do not write source-dependent claims when the evidence pack is missing or unverifiable.
Inputs
| Artefact |
Source/provider |
Required? |
Missing-input behaviour |
| Content brief, audience, and publication goal |
Client or content lead |
Yes |
Stop and return the minimum questions needed to establish the reader promise. |
| Approved angle and evidence pack |
blog-idea-generator, research, or subject expert |
Yes for factual content |
Narrow the article or flag claims as not assessed; do not invent citations or experience. |
| Voice, length, SEO, and publication constraints |
Brand or editor |
Conditional |
State assumptions and avoid claiming brand or search compliance. |
Outputs
| Artefact |
Consumer |
Acceptance condition |
| Publication-ready article |
Editor and intended reader |
The opening earns attention, the body fulfils one reader promise, claims are sourced or qualified, and the ending gives a useful next step. |
Evidence Produced
| Evidence |
Consumer |
Acceptance condition |
| Claim and source check |
Editor |
Every load-bearing factual claim maps to a source or an explicit qualification. |
| Editorial quality check |
Publisher |
Structure, voice, links, metadata, and unresolved edits are recorded. |
Capability Contract
Read and search are required. Editing is allowed for authorised drafting and revision. Network research, publishing, image licensing, paid promotion, external messages, and claims of personal experience require explicit authority and evidence.
Degraded Mode
Fallback: when research, subject expertise, brand guidance, or publishing tools are unavailable, return the narrowest useful qualified draft, mark source and publication checks not assessed, and do not invent facts, quotes, experience, or SEO results.
Decision Rules
| Condition or choice |
Action |
Failure or risk avoided |
| Reader needs a practical sequence |
Use a guide or tutorial structure with tested steps |
Decorative advice with no usable path |
| Claim depends on data or current facts |
Verify and cite it at the point of claim |
Confident wrongness |
| Topic is opinion-led |
State the thesis, evidence, countercase, and limits |
Viewpoint-free filler |
| Only ideas are requested |
Route to blog-idea-generator |
Premature long-form drafting |
Workflow
- Confirm the audience, reader promise, angle, evidence, voice, and publication constraints.
- Select a structure that matches the reader's job and outline only sections that advance it.
- Draft with specific evidence, authored reasoning, varied rhythm, and explicit hard cases.
- Stop when a load-bearing claim, quotation, case, or personal experience cannot be supported.
- Recover by verifying, qualifying, removing, or reframing the affected passage.
- Edit for logic, voice, scanning, links, metadata, and the anti-slop gate before handoff.
Quality Standards
- The article makes one defensible promise and fulfils it without padded sections or search-engine mimicry.
- Sources, examples, counterarguments, edge cases, and the writer's actual point of view are visible.
Anti-Patterns
- Opening with a generic statement about a changing world. Fix: begin with the reader's concrete problem, tension, or evidence.
- Adding statistics without a source. Fix: cite a verified source or remove the number.
- Writing five interchangeable sections to reach a word count. Fix: keep only sections that advance the reader promise.
- Presenting borrowed experience as personal. Fix: attribute the case or label it as an example.
- Optimising keywords before the argument works. Fix: establish substance and reader usefulness first.
Worked Example
For an article on tender pricing, lead with the mismatch between proposed staff-days and fee totals, show a small traceable calculation, explain the evaluator risk, cover the case of reimbursables, and end with a pre-submission reconciliation check. Do not pad it with generic claims about competitive markets.
References
1---2name: blog-writer-33description: Use when drafting, revising, or finalising a publishable blog post, article, guide, case study, or thought-leadership piece; use blog-idea-generator when only topic discovery is required.4---56# Blog Writer7Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.89Turn an approved content brief and evidence set into an authored article with a clear reader promise, defensible claims, and publication-ready structure.1011<!-- dual-compat-start -->12## Use When1314- Draft or substantially revise a blog post, article, tutorial, opinion piece, case study, or long-form guide.15- Convert an approved topic and evidence pack into publishable content.1617## Do Not Use When1819- Use `blog-idea-generator` when the task ends at topic options, angles, or a content backlog.20- Do not write source-dependent claims when the evidence pack is missing or unverifiable.2122## Inputs2324| Artefact | Source/provider | Required? | Missing-input behaviour |25|---|---|---:|---|26| Content brief, audience, and publication goal | Client or content lead | Yes | Stop and return the minimum questions needed to establish the reader promise. |27| Approved angle and evidence pack | `blog-idea-generator`, research, or subject expert | Yes for factual content | Narrow the article or flag claims as not assessed; do not invent citations or experience. |28| Voice, length, SEO, and publication constraints | Brand or editor | Conditional | State assumptions and avoid claiming brand or search compliance. |2930## Outputs3132| Artefact | Consumer | Acceptance condition |33|---|---|---|34| Publication-ready article | Editor and intended reader | The opening earns attention, the body fulfils one reader promise, claims are sourced or qualified, and the ending gives a useful next step. |3536## Evidence Produced3738| Evidence | Consumer | Acceptance condition |39|---|---|---|40| Claim and source check | Editor | Every load-bearing factual claim maps to a source or an explicit qualification. |41| Editorial quality check | Publisher | Structure, voice, links, metadata, and unresolved edits are recorded. |4243## Capability Contract4445Read and search are required. Editing is allowed for authorised drafting and revision. Network research, publishing, image licensing, paid promotion, external messages, and claims of personal experience require explicit authority and evidence.4647## Degraded Mode4849Fallback: when research, subject expertise, brand guidance, or publishing tools are unavailable, return the narrowest useful qualified draft, mark source and publication checks `not assessed`, and do not invent facts, quotes, experience, or SEO results.5051## Decision Rules5253| Condition or choice | Action | Failure or risk avoided |54|---|---|---|55| Reader needs a practical sequence | Use a guide or tutorial structure with tested steps | Decorative advice with no usable path |56| Claim depends on data or current facts | Verify and cite it at the point of claim | Confident wrongness |57| Topic is opinion-led | State the thesis, evidence, countercase, and limits | Viewpoint-free filler |58| Only ideas are requested | Route to `blog-idea-generator` | Premature long-form drafting |5960## Workflow61621. Confirm the audience, reader promise, angle, evidence, voice, and publication constraints.632. Select a structure that matches the reader's job and outline only sections that advance it.643. Draft with specific evidence, authored reasoning, varied rhythm, and explicit hard cases.654. Stop when a load-bearing claim, quotation, case, or personal experience cannot be supported.665. Recover by verifying, qualifying, removing, or reframing the affected passage.676. Edit for logic, voice, scanning, links, metadata, and the anti-slop gate before handoff.6869## Quality Standards7071- The article makes one defensible promise and fulfils it without padded sections or search-engine mimicry.72- Sources, examples, counterarguments, edge cases, and the writer's actual point of view are visible.7374## Anti-Patterns7576- Opening with a generic statement about a changing world. Fix: begin with the reader's concrete problem, tension, or evidence.77- Adding statistics without a source. Fix: cite a verified source or remove the number.78- Writing five interchangeable sections to reach a word count. Fix: keep only sections that advance the reader promise.79- Presenting borrowed experience as personal. Fix: attribute the case or label it as an example.80- Optimising keywords before the argument works. Fix: establish substance and reader usefulness first.8182## Worked Example8384For an article on tender pricing, lead with the mismatch between proposed staff-days and fee totals, show a small traceable calculation, explain the evaluator risk, cover the case of reimbursables, and end with a pre-submission reconciliation check. Do not pad it with generic claims about competitive markets.8586## References8788- [Comprehensive blog-writing guide](references/comprehensive-blog-writing-guide.md)89- [Editorial standards](references/editorial-standards.md)90- [Writing craft](references/writing-craft.md)91- [Blog idea generator](../blog-idea-generator/SKILL.md)92- [Anti-slop guardrail](../../meta/anti-ai-slop/SKILL.md)93<!-- dual-compat-end -->
peterbamuhigire