campaign-context

To gather campaign context automatically, use an engine that triggers at the start of commands like /promote and /engage, applying MCP-first data gathering rules to pre-fill required fields such as campaign type, title, URL, goal, and progress.

A campaign context model establishes consistent data points—campaign type, title, URL, goal, and progress—across commands like /campaign, /promote, /check-in, and /engage, using MCP data when available to minimize manual input and reduce errors.

Reduce back-and-forth by using a context engine that guides one-question-at-a-time data collection, capturing only the minimal required fields for fundraisers, events, or groups before proceeding with the campaign execution.

Yes, the campaign context engine maintains cross-session memory, establishing context early and preserving it across /campaign, /promote, /check-in, and /engage commands so you do not need to re-enter campaign details.

Yes, MCP data is used first to pre-fill campaign fields automatically when available, minimizing the questions asked during /promote and /engage commands for fundraisers, events, and groups before executing the task.

The limitation of a minimal context model is that it only captures essential fields like type, title, URL, goal, and progress, meaning any additional custom data points required for complex campaigns will not be gathered automatically by the engine.