npx claudepluginhub thecloudtips/founder-os --plugin founder-os[--scheduled] [--verbose]workflow//listLists installed and generated CLI-Anything tools, scanning packages and directories. Supports --path for directory, --depth for recursion, --json for output format.
/listLists beads issues with filters for status, priority, type, assignee, labels, title, dates, and more. Outputs table, JSON, digraph, or DOT formats.
/listLists all configured Hookify rules from .claude/hookify.*.local.md files in a summary table with name, enabled status, event, pattern, file path, plus message previews and management footer.
/listLists all learnings from pro-workflow database, sorted by recent (default) or applied count, or filtered by category/project. Shows ID, category, description, applications, and dates.
/listLists all Hookify rules in the project with status (enabled/blocking/warning/disabled), location, patterns/conditions, and totals. Supports --enabled, --disabled, --all flags.
/listLists and searches sparkrun inference recipes by name, model, runtime, or description. Filters by registry and runtime; also inspects, validates VRAM, and exports recipes.
List all workflow YAML files in the workflows/ directory with their metadata.
Read: ${CLAUDE_PLUGIN_ROOT}/skills/workflow/workflow-design/SKILL.md
--scheduled (optional) — show only workflows with schedule.enabled=true--verbose (optional) — show full details including step count, dependencies, and schedule infoCheck if context files exist at _infrastructure/context/active/. If the directory contains .md files, read business-info.md, strategy.md, and current-data.md. Use this context to personalize output (e.g., prioritize known clients, use correct terminology, align with current strategy). If files don't exist, skip silently.
Read the context-injection skill at _infrastructure/memory/context-injection/SKILL.md.
Query for memories relevant to the current input (company, contacts, topics detected in arguments).
If memories are returned, incorporate them into your working context for this execution.
Scan Directory: List all .yaml files in the workflows/ directory (exclude workflows/examples/ and workflows/runners/).
Parse Metadata: For each file, parse YAML and extract: workflow.name, workflow.description, workflow.version, workflow.tags, step count, schedule.enabled, schedule.cron.
Filter: If --scheduled, include only workflows where schedule.enabled=true.
Display List:
Default format:
Available Workflows
━━━━━━━━━━━━━━━━━━
morning-routine "Weekday morning check-in pipeline" (4 steps)
weekly-review "End-of-week review and planning" (6 steps)
client-onboarding "New client setup with CRM sync" (5 steps, scheduled)
━━━━━━━━━━━━━━━━━━
Total: 3 workflows
Use /founder-os:workflow:run [name] to execute
Verbose format (--verbose): Add version, tags, schedule details, and step list for each workflow.
No workflows found in workflows/ directory.
Create one with /founder-os:workflow:create or copy the template from templates/workflow-template.yaml
Read the pattern-detection skill at _infrastructure/memory/pattern-detection/SKILL.md.
Log this execution as an observation with: plugin name, primary action performed, key entities (companies, contacts), and output summary.
Check for emerging patterns per the detection rules. If a memory reaches the adaptation threshold, append the notification to the output.
/founder-os:workflow:list
/founder-os:workflow:list --scheduled
/founder-os:workflow:list --verbose