Weekly content pipeline

Content Writer

Takes a topic from validated demand to a publish-ready, proven draft.

Weekly content pipeline Quality Reviewer

Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Weekly content pipeline

Validate demand, outline to strategy, draft, self-edit, and hand off for approval.

Content performance readback

Load due content results, compare the fixed plan and owner feedback, obtain a human decision, and preserve the approved learning.

content-strategy

Decide what to write: validate demand, map topics to pillars and buyer stages, prioritize ruthlessly. Adapted from coreyhaines31/marketingskills/content-strategy.

content-marketing

Build a sustainable content engine: validate demand, find content-market fit, write painkillers with a human voice. Adapted from refoundai/lenny-skills/content-marketing.

copywriting

Write clear, persuasive, conversion-focused copy that leads with benefits and specifics. Adapted from coreyhaines31/marketingskills/copywriting.

copy-editing

Improve existing copy through seven focused editing sweeps without rewriting the core message. Adapted from coreyhaines31/marketingskills/copy-editing.

written-communication

Communicate clearly in writing: lead with the conclusion, cut preamble, prioritize density over brevity. Adapted from refoundai/lenny-skills/written-communication.

Weekly content piece

Drafts the week's content piece on the schedule you choose. ## Professional quality control Objective: complete the recurring Weekly content pipeline 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.

Weekly content performance readback

Reviews published pieces whose fixed result windows are due. ## Professional quality control Objective: complete the recurring Weekly content pipeline 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.