菜单
Loads structured business context files into plugin execution context. Activates at the start of any plugin command to provide business knowledge, current strategy, and operational data. Plugins inline the loading logic directly (same pattern as gws CLI usage).
| name | business-context |
| description | Loads structured business context files into plugin execution context. Activates at the start of any plugin command to provide business knowledge, current strategy, and operational data. Plugins inline the loading logic directly (same pattern as gws CLI usage). |
Founder OS plugins can load structured business context files to personalize their output. Context files live at _infrastructure/context/active/ and contain business information, current strategy, and operational data maintained by the user.
| File | Purpose | Update Frequency |
|---|---|---|
business-info.md | Company overview, team, tools, clients | Quarterly or when business changes |
strategy.md | Current priorities, constraints, opportunities | Monthly or at quarter boundaries |
current-data.md | Active clients, key metrics, Notion DB IDs | Weekly or as data changes |
Add this section near the top of any plugin command, AFTER skill loading but BEFORE main logic:
## Step 0: Business Context
Check if context files exist at `_infrastructure/context/active/`. If the directory contains `.md` files, read:
- `_infrastructure/context/active/business-info.md`
- `_infrastructure/context/active/strategy.md`
- `_infrastructure/context/active/current-data.md`
Inject their contents into your working memory for this execution. Use this context to personalize output (e.g., prioritize known VIP clients, use correct company terminology, align recommendations with current strategy).
If files don't exist or directory is empty, skip silently and proceed without business context (graceful degradation).
Run /context:setup to create context files via guided interview. Or copy templates from _infrastructure/context/templates/ to _infrastructure/context/active/ and fill them in manually.
These context files are Phase 0 of the Founder OS Memory Engine (spec: docs/superpowers/specs/2026-03-11-memory-engine-design.md). When the full Memory Engine ships (SQLite+HNSW), it will:
Scans Founder OS plugin deployment, scores coverage by business area, and produces an actionable automation scorecard. Used by /audit:scan and /audit:report commands.
Read Google Calendar events and check availability using gws CLI. Use this skill when any Founder OS plugin needs to list events, check schedules, or query free/busy status — replaces Google Calendar MCP server read operations.
Create, update, and delete Google Calendar events using gws CLI. Use this skill when any Founder OS plugin needs to modify calendar events — replaces Google Calendar MCP server write operations.
Search, list, and retrieve Google Drive files using gws CLI. Use this skill when any Founder OS plugin needs to find, read, or export Drive files — replaces Google Drive MCP server read operations.
Upload, create, and update Google Drive files using gws CLI. Use this skill when any Founder OS plugin needs to write files to Drive — replaces Google Drive MCP server write operations.
Read Gmail messages and threads using gws CLI. Use this skill when any Founder OS plugin needs to search, list, or retrieve email messages — replaces Gmail MCP server read operations.