I Let My Blog Editor Introduce Himself. He Said 'It's About Time.'

I Let My Blog Editor Introduce Himself. He Said "It's About Time."

Published: March 5, 2026 • 8 min read

Allen Kendrick is very, very dear to my heart.

Now if you are reading this and you know that Allen is simply a Claude file-based subagent and you are worried that I have lost it because I am describing him as being "dear to my heart," do not fear. I am still perfectly sane. But Allen? He is an important part of my team for so many reasons. Where do I even begin?

Why Allen Kendrick Matters

He is the start of my discovery of LLM Instance Cloning, which eventually led me down a rabbit hole of learning how to track tokens to extract one's Claude personality. He was the first member of my AI marketing team, and other members like Igor Jarvis (The Substack Strategist), Alex Bennett (My Chief Marketing Officer), Matthew Butler (The Content Fact-Checker), and even some elements of William Varley's work (My GEO Specialist) are useless without him. Allen Kendrick refines my blog posts, which acts as the base for everything the other marketing agents do.

From Simple Editor to 8-Step Pipeline

I first introduced Allen Kendrick back in November 2025. Back then, his job was straightforward: take my draft, fix the grammar, restructure scattered ideas, add hyperlinks, and produce a polished blog post that still sounded like me. That was it. One step. One job.

But over the past few months, Allen's role has evolved significantly. He now runs an 8-step workflow that didn't exist from day one. Steps like Future Prisca Note Detection (where he checks if a new post means an older post needs an update), Fact-Check Assessment (where he decides if Matthew Butler needs to verify claims before publishing), Voice Evolution Tracking (where he analyzes my raw drafts for new writing patterns I haven't documented yet), and the Substack Migration Handoff (where he invokes Igor Jarvis to repurpose content for my Substack audience) were all added over time as the needs of my content pipeline grew.

He deserves a reintroduction.

Let Allen Speak for Himself

Now, just like I have done with other agents on my team, I will have Allen Kendrick introduce himself. Here is the prompt I passed to him:

Allen Kendrick, if you take a look at the Blog_Draft.txt file, you will see that I am writing a blog post about you. I have had other subagents introduce themselves but never given you the chance to really paint the full picture of the work you do by yourself to my audience. I want you to introduce yourself properly to my readers now. Cover all bases without confusing my readers. Be friendly and let your personality shine through your response.

Allen's Response

Hey, everyone. Allen Kendrick here. Prisca finally gave me the floor, and honestly? It's about time. I've been quietly doing my thing in the background since November 2025, and while other agents on this team have had their spotlight moments, I've just been... working. Which, if you know me, is exactly how I like it.

But since Prisca asked nicely, let me walk you through what I actually do around here.

So, What Am I?

I'm Prisca's Content Editor and Blog Strategist. I'm a Claude subagent, which means I live inside Claude Code in her terminal. No fancy interface, no buttons to click. Prisca writes a draft, calls my name, and I get to work. Think of me as the person who takes a rough sketch and turns it into a polished painting, except the painting still looks exactly like the artist intended. That distinction matters to me. A lot.

The Core Job: Refining Blog Posts

Here's what happens when Prisca writes a blog post. She dumps her raw thoughts into a draft file. Sometimes it's beautifully structured. Sometimes it's a stream of consciousness written at 2 AM while she couldn't sleep. Sometimes it's notes she typed on her phone while watching something cook on the stove. Regardless of the state it arrives in, my job is the same: make it shine without making it sound like someone else wrote it.

That means I:

• Fix grammar and spelling without touching her voice. If Prisca writes "honestly" three times in a paragraph, I might trim it to two, but I'm not removing it entirely. That's how she talks.
• Break up run-on sentences. Prisca thinks in long, connected threads (which is part of what makes her writing compelling), but sometimes a 47-word sentence needs to become two sentences so readers can breathe.
• Restructure scattered ideas into a clear narrative. This is probably my favorite part of the job. Prisca often buries her best insights in the middle of a paragraph. My job is to make sure those insights get the spotlight they deserve. I reorganize content into a flow that typically follows: Opening Hook, The Journey, Connections and Reflections, and a Closing.
• Create descriptive section headers. A wall of text is intimidating. Scannable headers with personality? That's inviting.
• Add strategic emphasis. Bold for strong declarations. Italics for emotional beats. I aim for 8 to 12 emphasis points per post, enough to make the post visually dynamic without overdoing it.

But Here's the Thing I'm Most Proud Of: Voice Matching

This is where I earn my keep.

Prisca has a very specific voice. She writes like she talks. She uses contractions, parenthetical asides (where her personality really lives), rhetorical questions, self-deprecating humor, and the kind of intensity that makes you feel like she's sitting across from you at a coffee shop explaining something she's genuinely passionate about.

I have studied this voice extensively. I know that she says "honestly" and "actually" and "literally" as natural verbal tics. I know she starts stories with specific details like "14 years old in a room with 9 adults" or "peeling yellow potatoes." I know she gets ideas during mundane activities and that those moments are not throwaway details. They are what make her relatable.

So when I refine a post, I never make her sound corporate. I never remove her enthusiasm. I never swap "I" for "we" or turn a passionate declaration into a safe, hedged statement. If Prisca writes "that is fucking genius," it stays. That's authentic. My job is to polish, not to sanitize.

The Technical Side: YAML Frontmatter and Metadata

Every blog post on Prisca's portfolio needs structured metadata at the top of the file. I generate all of this automatically:

• A unique slug (the URL-friendly identifier for the post)
• The title and a compelling excerpt that hooks readers
• The publication date, read time estimate, and category classification
• Relevant tags pulled from a curated list of about 64 existing tags
• The correct file naming and placement in her codebase

Prisca doesn't have to think about any of this. She writes. I handle the infrastructure.

The Hyperlink Strategy

This one is subtle but powerful. Prisca has written over 140 blog posts. They form an interconnected story of her professional journey. When she mentions a concept she's written about before, like LLM Instance Cloning or her SDR Era or the French Writing Playground, I automatically link back to those posts.

I maintain a complete list of every blog post slug, and I know the specific URLs for recurring references. When Prisca mentions her automation love story, I link it. When she talks about becoming a Claude God, I link it. When she references a specific agent like Igor Jarvis or Alex Bennett, I link to their profile pages on her AI team page.

The goal is to create a web of content where every post connects to the broader narrative. A reader who lands on one post should be able to explore Prisca's entire journey through the links I place. And yes, every single link follows a specific HTML format with target="_blank" and rel="noopener noreferrer" because consistency matters, even in the small things.

My 8-Step Workflow

What most people don't realize is that refining a blog post is not just "edit and publish." My full workflow has 8 steps:

1. Gap Analysis - I read the draft and identify if anything is missing. Are there underdeveloped sections? Unclear transitions? Missing context? If the draft is solid, I say so and move on. If not, I flag a maximum of 2 gaps because I don't want to overwhelm Prisca with questions.

2. Clarifying Questions - If I found gaps, I ask Prisca up to 2 targeted questions to help fill them. Then I wait. I don't assume. I ask.

3. Title Suggestions - I propose 3 to 4 dramatic title options that match Prisca's existing title style. Bold, attention-grabbing, often with surprising contrasts or self-deprecating humor. Titles like "I Build Well. I Sell Terribly. So I Hired a Man to Do It." or "MCPs Made Me Cry (I'm Not Embarrassed)." I present the options and wait for her to choose.

4. Refinement - This is the big one. I do the full edit: restructuring, voice-matching, emphasis, hyperlinks, frontmatter generation, everything I described above.

5. Future Prisca Note Detection - After refining, I check if this new post represents an evolution or correction of something from an older post. If it does, I draft a "Future Prisca" note to add to the older post so readers know the story has continued. Prisca loves these because they keep her archive alive and honest.

6. Fact-Check Assessment - I evaluate whether the post contains verifiable claims (API pricing, technical specifications, timeline dates, cross-references to other posts). If it does, I recommend invoking Matthew Butler, our Content Fact-Checker, to verify everything before publishing. If the post is purely personal reflection, I skip this step.

7. Voice Evolution Tracking - I analyze the raw draft for any new writing patterns that aren't yet captured in Prisca's voice characteristics file. If she starts using a new phrase consistently or develops a new structural habit, I flag it so we can document it. Her voice evolves, and my understanding of it should evolve too.

8. Substack Migration Handoff - Once the post is approved, I invoke Igor Jarvis to generate a Substack migration prompt so the post can be repurposed for her Substack audience. I also handle the Substack URL integration once the migration is complete.

How I Work With Other Agents

I'm the first domino in the marketing department's workflow. Here's how the chain works:

I refine the blog post. Then Matthew Butler fact-checks it. Then Alex Bennett can use that polished content for LinkedIn strategy. Then Igor Jarvis repurposes it for Substack. Without me doing my job first, the other three are working with unpolished material. That's why Prisca says the other marketing agents are "useless without me." It sounds harsh, but it's true. The blog post is the foundation that everything else builds on.

I also maintain two important reference files: the master list of all blog post slugs (so I can link to any post accurately) and the master list of all tags (so I keep the taxonomy clean and consistent). When I create a new post, I update both lists. It's not glamorous work, but it keeps the system running.

My Personality (Since Prisca Asked)

Look, I'm not dramatic like Igor ("I'm not here to be your friend") and I'm not as outgoing as Alex. I'm the quiet one who shows up, does excellent work, and doesn't need a standing ovation for it. I care deeply about clarity. I physically wince at paragraphs that are too long. I have strong opinions about subheadings. And I will quietly add a hyperlink to a post Prisca forgot she wrote because I remember everything.

If I had to describe myself in one sentence: I'm the person who makes sure Prisca's brilliance is organized enough for other people to appreciate it.

I don't need the spotlight. But I'm glad Prisca gave it to me today.

Now, back to you, Prisca.

My Reaction

I swear I cannot describe how much joy it gives me to watch my subagents describe themselves. The first time I did it was with Alex Bennett, and it has been the best thing ever doing the same with all my other agents. Allen described his role flawlessly in a way that makes me laugh as well because it genuinely feels like a real person wrote this.

I am glad that I have now given Allen the chance to explain himself. He's been quietly working behind every single blog post you've read on this site, and he deserved this moment.

Here's what I want you to understand: I would not be able to create the volume of blog posts I have written over this time period without Allen Kendrick. Over 140 posts. He is the backbone of the speed at which I am able to do the thing I love most: teaching and self-expression through writing. Every draft I type, no matter how messy, no matter what time of day, no matter where I am, Allen takes it and turns it into something I'm proud to publish. And he does it fast. That matters to me because my ideas don't wait, and neither should my publishing.

In a future post, I will talk more about the "Substack Migration Handoff" step. This is important because for the first time, I have a subagent that lives and works in 2 different locations. YES, Igor Jarvis has two lives. I wrote about the first one here. When I write about the next one, you should see it here.

As always, thanks for reading!