Adds --schedule flag support to any Founder OS plugin command. Generates P27 Workflow Automator YAML files behind the scenes so users can schedule recurring plugin execution without knowing P27 exists.
From founder-osnpx claudepluginhub thecloudtips/founder-os --plugin founder-osThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
The scheduling bridge enables any plugin command to accept a --schedule flag that configures recurring execution. Behind the scenes, it generates a P27 Workflow Automator workflow YAML and registers it with P27's scheduling system.
Any plugin command that supports scheduling adds this flag to its argument parsing:
| Flag | Value | Behavior |
|---|---|---|
--schedule "expression" | Natural language or 5-field cron | Generate workflow + register schedule |
--schedule disable | literal "disable" | Remove schedule for this command |
--schedule status | literal "status" | Show current schedule status |
--persistent | (no value, used with --schedule) | Generate OS-level cron instead of session-level |
See references/schedule-flag-spec.md for full parsing rules.
When a user runs e.g. /founder-os:briefing:daily --schedule "weekdays 7:30am":
templates/workflow-template.yamlworkflows/auto-[command-name].yamlskills/workflow/workflow-scheduling/SKILL.md--persistent)Add this section to any plugin command file that should support scheduling:
## Scheduling Support
If `$ARGUMENTS` contains `--schedule`:
1. Extract the schedule value and any `--persistent` flag
2. Read `_infrastructure/scheduling/SKILL.md` for scheduling bridge logic
3. Read `_infrastructure/scheduling/references/schedule-flag-spec.md` for argument parsing
4. Handle the schedule operation (create/disable/status) per the spec
5. Exit after scheduling — do NOT continue to main command logic
Use P27's existing NL-to-cron conversion table (from skills/workflow/workflow-scheduling/SKILL.md):
| Natural Language | Cron |
|---|---|
| "weekdays 8am" | 0 8 * * 1-5 |
| "every morning" | 0 9 * * * |
| "every Monday" | 0 9 * * 1 |
| "Fridays 5pm" | 0 17 * * 5 |
| "daily 6am" | 0 6 * * * |
| "twice daily" | 0 9,17 * * * |
Always confirm the converted expression with the user before applying.
When a plugin supports scheduling, suggest a sensible default if user hasn't specified one:
| Command | Suggested Default |
|---|---|
/founder-os:briefing:daily | Weekdays 7:30am |
/founder-os:morning:sync | Weekdays 8:00am |
/founder-os:review:weekly (review) | Fridays 5:00pm |
/founder-os:crm:sync-email | Weekdays 9:00am, 2:00pm |
/founder-os:client:health-scan (health-scan) | Weekdays 9:30am |
/founder-os:followup:check | Weekdays 10:00am |
/founder-os:drive:search (drive-search) | Daily 6:00am |
/founder-os:slack:digest | Weekdays 6:00pm |
/founder-os:learn:weekly | Fridays 4:00pm |