---
name: recurring-brief
description: "Prepare a repeatable update that stays honest about stale or unavailable inputs. Use when producing an authorized recurring operational or research brief."
---

# Recurring brief

## Inputs

The reporting period, sources, prior brief, decision owner and delivery scope.

## Workflow

1. Record the reporting window and source freshness. Distinguish new evidence from carried-forward material.
2. Inspect the required sources and compare against the prior period only when definitions and coverage match.
3. Surface meaningful changes, blocked integrations and decisions needed. Do not fill missing sections with invented activity.
4. Separate scheduler execution from completed workflow outcomes.
5. Produce the brief within the existing delivery authorization; do not create schedules or send messages unless requested.

## Deliver

A dated brief with changes, evidence freshness, blocked inputs and actionable next steps.

## Limits

Includes no scheduler or integrations. Repeated execution is not proof that the automation is healthy. Follow the user's current request and the host application's permissions. This instruction file grants no tool access or extra authority.

## Example request

Prepare this week's brief from these sources and the prior report. Mark stale or missing inputs, and separate activity from completed outcomes.

## Reuse

Original public workflow from Meow Creative Haus, version 1.0.0. You may use, modify and redistribute this file, including commercially, with this notice retained. Provided as-is without warranty. This permission applies to this file only, not to third-party tools, private configurations or source skills.