A marketing lead has Claude Code draft six weekly meeting docs and reviews every line

The task

Every Sunday evening the marketing lead prepares the team for the week. That means reviewing last week's results across the funnel for two business lines, checking the status of each initiative agreed the week before, and writing documents for six recurring meetings. Before this system the session was scattered, the task board was never fully built out, and the meeting documents gave the team too little clarity on priorities.

What they did

The lead built a Claude Code skill, a set of plain Markdown instruction files that describe the job. One command starts the run. The agent pulls the week's key data, flags metrics that need attention, reads last week's meeting document, and marks each goal as done, carried, or dropped. It also reads the team's Asana boards for the real status of every task. It then drafts all six documents in dependency order: three function meeting docs, a strategic roll-up, the marketing sections of the product team's document, and the agenda for a one-on-one with the CEO. Each draft is complete, with a proposed read of the performance and an inline flag at every point that needs the lead's judgment. After the lead approves, the agent creates the Notion page, updates Asana, and drafts the Slack message that shares the plan with the team. A separate limited agent handles the Asana changes and receives task text only, never revenue, spend, or pipeline figures. Team-specific details sit in one plain-language config file.

What the source reports

According to the source, Sunday prep that once took more than two hours now fills most of two hours in one focused sitting, and the author calls the time savings modest. According to the source, after about two months of weekly runs, 13 stale tasks turned up on a single team board, which led to a weekly board reconciliation. The author reports that the main gain is quality: every meeting is prepared and every commitment has a status.

Where the approval sits

The lead reviews every line of every draft, and the system stops at each judgment call and waits. Nothing is written to a live document that the team reads until the lead approves it. The skill may create and update only the pages the lead owns. It is forbidden from creating the product team's meeting document or the CEO one-on-one page, so it holds those sections until the owner's page exists. The source states plainly that this is not autopilot.

Worth knowing

This is a personal account of internal team planning, not client work, and it is one person's experience. The author says the routine is too rigid for unusual weeks, such as a week dominated by one project or a metric that needs an immediate deep dive. Some data pulls are still manual. The files are wired to one company's tools, so what carries over is the process and the sign-off gate.

Prompt for your agent

More in this category

• Marketing operations

  A marketing workspace queues agent work for approval and puts paid calls behind a gate

  A marketer keeps procedures, checklists, and house rules in one Obsidian folder that Claude Code works from. Finished work waits on a board for accept, ask, or deny, and paid API calls stop at an approval note first.

  Read the entry
• Marketing operations

  A small marketing team has agents read six systems and approves what reaches customers

  A marketing lead at a small company has AI agents read six marketing systems in one pass and return one page on what changed. The agents draft and analyze, and a person approves anything that goes to customers.

  Read the entry