gremlinsBlogger Gremlin example
Series brief and topic in; a reviewed, safety-checked post package out.
This is a format example showing what a published Gremlin definition looks like — it is not a claimed published pattern.
Produces: A reviewed, safety-checked post package awaiting human publication approval.
Roster
| Role | Purpose | Input | Output |
|---|---|---|---|
| Research | Gather sources and facts for the topic | series brief + topic | research pack: sources, raw notes, key facts, open questions |
| Writer | Produce the structured first draft | research pack + series brief | structured draft |
| Editor | Improve clarity, structure, accuracy, and voice | structured draft | edit notes |
| Visual/CX | Specify diagrams and interactive components | structured draft | diagram specs, component specs |
| Reader Panel | Critique from the target audience's perspective | structured draft | audience critique |
| Rewriter | Fold all feedback into a revised draft | draft + edit notes + critique + visual specs | revised draft |
| Publication Safety | Sensitive-content check, AI-tell check, approval checklist | revised draft | safety-checked post package |
Handoff contracts
| From → To | Contract |
|---|---|
| Research → Writer | Research pack lists sources for every key fact; the Writer may not invent citations. |
| Writer → Editor | Draft is structurally complete — no placeholder sections. |
| Editor → Rewriter | Edit notes are actionable line- or section-level items, not vague impressions. |
| Reader Panel → Rewriter | Critique states the audience assumption behind each objection. |
| Rewriter → Publication Safety | Revised draft records which feedback items were applied or rejected, and why. |
Completion
The safety check has passed and the package is assembled for human review.
Human gates
- A human approves publication; no agent publishes.
Purpose
Turn a series brief and a topic into a post that has already survived editing, audience critique, and a safety check — so the only remaining human decision is “publish or not.”
When to use
You publish regularly, the quality bar matters more than turnaround time, and you want the review pipeline to be the same every time instead of depending on who is available to read a draft.
Roster in depth
Seven specialists in sequence, each with one job (see the roster table above). The pipeline is deliberately serial through the writing stages, with the Editor, Visual/CX, and Reader Panel critiques all feeding the single Rewriter pass.
Handoff contracts
Each transition is a contract, not a hope — the receiving agent’s required inputs are stated, and the sending agent must produce them (see table above). The load-bearing one is Rewriter → Publication Safety: the revised draft must record which feedback was applied or rejected and why, so the safety pass reviews decisions, not archaeology.
Human gates
One, at the end, non-negotiable: a human approves publication. The Gremlin assembles a package; it never publishes.
Portability notes
Nothing in this definition depends on a specific vendor, model, or repo layout. You need: an agent runtime that can run seven sequential prompts, somewhere to keep the intermediate artifacts, and a human at the end.
Definition source
# Blogger Gremlin (type B — multi-agent pipeline)
Input: series brief + topic
Output: reviewed, safety-checked post package for human publication approval
Pipeline:
1. Research — sources, raw notes, key facts, open questions
2. Writer — structured draft from research pack + brief
3. Editor — clarity, structure, accuracy, voice → edit notes
4. Visual/CX — diagram + interactive component specs
5. Reader Panel — audience-perspective critique
6. Rewriter — revised draft folding in all feedback (log applied/rejected)
7. Publication Safety — sensitive-content check, AI-tell check, checklist
Handoff contracts:
- Research→Writer: every key fact has a source; no invented citations
- Writer→Editor: structurally complete draft, no placeholders
- Editor→Rewriter: actionable line/section-level notes
- Reader Panel→Rewriter: each objection states its audience assumption
- Rewriter→Safety: feedback decisions logged (applied/rejected + why)
Completion: safety check passed, package assembled for human review
Human gate: a human approves publication; no agent publishes