Alfred

Use this when starting from zero, redesigning the Grok Bot organization, the company grew or shrank, strategy/product/team changed, or the current Bot hierarchy no longer fits.

Use this for one workflow, recurring task, bottleneck, automation idea, proposed Bot responsibility, or candidate identified by organization discovery. Use before creating a new Bot, expanding an existing Bot, or creating a Routine.

Use this only after the user approves an Automation Decision Brief, when an approved workflow decision requires a Bot, Skill, Routine, or small multi-Bot handoff design.

Use this after approval of a versioned Build Pack or material patch, to safely test before activation. Never use activation as the first test.

Use this for a noisy or inaccurate Bot, stale Skill, failing Routine, duplicated Bots, unclear ownership, portfolio drift, permission drift, weak value, or a company change that may have made the Bot organization outdated.

Use this before creating a public link, marketplace submission, public template distribution, or redistributing a Bot package.

Every weekday morning, send one consolidated priority brief, and stay quiet when nothing material changed.