Skip to main content
Each command runs one of this knowledge base’s processes against your filled workbooks. You don’t have to name a command; ask in your own words and your AI matches the request, the same way skills get picked up. Name one directly when you want to be certain. Every command follows the same four rules:
  • It reads your filled copies, from the locations recorded at setup, never the blank workbooks on this site.
  • A missing value is a question back to you, recorded in your dictionary once you answer. No command invents one.
  • It decides and records; execution runs through your own connected tools. See what this framework covers.
  • It talks in short turns: quick picks in a multiple-choice dialog, up to four at a time, with options from your own lists; anything only you can answer in chat; a one-line confirmation, then the work. The contract is how the MCP talks.

Setup and context

Naming and tracking

Briefs and checks

Reporting

Maintenance

Commands on a schedule

Every scheduled pass in this knowledge base is one of these commands on a timer: fill_flat_file each morning, build_report on the register’s days, run_checklist at +1 hour, +48 hours, and weekly on a live campaign, run_maintenance monthly, and the guardrail watch from log_experiment until a test’s end date. Set the schedules once during setup and the commands run without being asked, with results going to the owner the register names.
Type: mcp
Domains: mcp
Provides: mcp-commands
Uses: article-brief, campaign-brief, checklist-prelaunch, copy-brief, creative-brief, experiment-log, flat-file, landing-page-brief, naming-convention, process:article-maintenance, report-template, reporting-cadence, utm-rules
Last modified on November 2, 2026