How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

help - Prompt - OpenSmartRoute

Name: help
Author: mkolb22

Prompt file imported from mkolb22/dockercd (.claude/commands/help.md). Copyright stays with the author.

Display context-aware help for Dragonfly WYSIWID workflows and commands.

When the user runs this command, you should:

Determine Help Context
- If no argument: Show overview of all commands
- If topic provided: Show detailed help for that topic
- If in workflow: Show current state and available actions
Available Topics
- commands - List all slash commands
- concepts - Explain the 10 concepts
- workflow - How workflows work
- sync - Synchronization rules
- state - Current workflow state
- troubleshooting - Common issues and fixes

Usage

/help              # Overview and quick start
/help commands     # List all commands
/help concepts     # Explain concepts
/help workflow     # How workflows work
/help state        # Current workflow state
/help troubleshooting  # Common issues

Overview Response (no arguments)

When user runs /help with no arguments:

Dragonfly WYSIWID Architecture - Quick Reference

WHAT YOU SEE IS WHAT IT DOES

Core Workflow:
  Story -> Architecture -> Implementation -> Quality -> Version

Getting Started:
  /feature "description"   Create a new feature
  /workflow "description"  Run complete workflow automatically
  /sync                    Check current sync state

Key Commands:
  /costs                   Show session costs
  /trace <id>              Trace workflow history
  /health                  Check session health
  /checkpoint              Save current state

Need More Help?
  /help commands           All available commands
  /help concepts           How concepts work
  /help workflow           Workflow details
  /help troubleshooting    Common issues

Commands List Response

When user runs /help commands:

Dragonfly Commands Reference

WORKFLOW COMMANDS
  /feature <description>   Create feature story, evaluate syncs
  /workflow <description>  Run complete workflow automatically
  /sync                    Evaluate synchronization rules

STATE & CONTEXT
  /checkpoint              Save session state
  /restore                 Restore from checkpoint
  /health                  Check context usage
  /trace <id>              Trace provenance chain

COST & PERFORMANCE
  /costs                   Show session costs
  /predict-cost <desc>     Estimate feature cost
  /slo                     View SLO metrics

MEMORY
  /remember <fact>         Store in semantic memory
  /recall <query>          Retrieve from memory
  /global-remember         Store across projects
  /global-recall           Recall cross-project

ANALYSIS
  /replay <id>             Replay failed workflow
  /explore <question>      Explore codebase
  /profile                 Profile project
  /retrospective           Review workflow quality

UTILITIES
  /cache                   Manage concept cache
  /classify <desc>         Classify task type
  /estimate <desc>         Estimate effort
  /pr-review               Review pull request

Concepts Help Response

When user runs /help concepts:

Dragonfly Concepts (10 Total)

CORE WORKFLOW CONCEPTS
  story          Captures user requirements (Opus)
                 Actions: create, update, clarify, cancel

  architecture   Designs technical approach (Opus)
                 Actions: design, revise, validate

  implementation Generates code from specs (Opus)
                 Actions: generate, refactor, fix

  quality        Reviews code and runs tests (Opus)
                 Actions: review, test, benchmark

  version        Manages git operations (Opus)
                 Actions: commit, tag, release

  context        Manages context window (Opus)
                 Actions: compress, snapshot, restore

INTEGRATION CONCEPTS
  code-analysis  Gathers codebase context via MCP (Opus)
                 Actions: context, impact, profile

  security       Validates security at each phase (Opus)
                 Actions: threat_model, validate, scan

  verification   Multi-pass independent review (Opus)
                 Actions: verify_architecture, verify_implementation

  documentation  Generates docs at each phase (Opus)
                 Actions: generate, update, validate

KEY PRINCIPLE:
  Concepts NEVER call other concepts directly.
  Synchronization rules orchestrate the workflow.

State Help Response

When user runs /help state:

First, check current state by reading data/ files:

Current Workflow State

ACTIVE FLOWS
  flow-001: "Add user authentication"
    Status: in_progress
    Phase: implementation
    Story: story-001 (ready)
    Architecture: arch-001 (completed)
    Implementation: impl-001 (in_progress)

RECENT ACTIONS
  1. story.create -> completed (2 min ago)
  2. architecture.design -> completed (1 min ago)
  3. implementation.generate -> in_progress

NEXT STEPS
  - Implementation completes
  - Sync triggers: impl-to-quality-review
  - Parallel: impl-to-quality-test

CONTEXT USAGE
  Current: 35%
  Status: healthy
  Checkpoints: 1

ACTIONS YOU CAN TAKE
  /sync --execute          Continue workflow
  /trace flow-001          See full history
  /checkpoint              Save current state

Troubleshooting Response

When user runs /help troubleshooting:

Dragonfly Troubleshooting Guide

COMMON ISSUES

1. "Sync rule not firing"
   Cause: Prerequisites not met
   Fix: Check data/ state files
   - /trace <id> to see what's missing
   - Ensure previous concept completed successfully

2. "Context too high (>90%)"
   Cause: Long workflow without compression
   Fix: Create checkpoint and restore
   - /checkpoint "before continuing"
   - /restore if needed

3. "MCP server unavailable"
   Cause: MCP servers not running
   Fix: Workflow continues without code analysis
   - Check: mcp-servers/ for server status
   - MCP is optional - workflow gracefully degrades

4. "Architecture has high risk"
   Cause: Design detected risky patterns
   Fix: Review and approve or revise
   - Read data/architecture/arch-{id}.yaml
   - User decision required

5. "Quality review failed"
   Cause: Code issues found
   Fix: Check review findings
   - Read data/reviews/review-{id}.yaml
   - Fix issues and re-run quality

6. "Missing state file"
   Cause: Concept didn't complete
   Fix: Re-run previous step
   - Check data/ for existing state
   - /replay <id> to restart from failure

DIAGNOSTIC COMMANDS
  /health                  Check overall health
  /trace <id>              Trace specific flow
  /costs                   Check spending
  /sync --dry-run          Preview sync evaluation

GETTING HELP
  - Read .claude/synchronizations/*.yaml for workflow logic
  - Check data/provenance/ for action history
  - Review CLAUDE.md for project context

Context-Aware Behavior

When providing help, check:

Active Workflow: If there's an in-progress flow, offer relevant next steps
Recent Errors: If data/ shows issues, suggest fixes
Context Usage: If high (>75%), suggest checkpoint
MCP Status: If unavailable, note graceful degradation

Related Commands

/health - More detailed health status
/trace - Detailed provenance tracking
/sync - Manual sync evaluation

Install help and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Display context-aware help for Dragonfly WYSIWID workflows and commands. When the user runs this command, you should: 1. **Determine Help Context** - If no argument: Show overview of all commands - If topic provided: Show detailed help for that topic - If in workflow: Show current state and available actions 2. **Available Topics** - `commands` - List all slash commands - `concepts` - Explain the 10 concepts - `workflow` - How workflows work - `sync` - Synchronization rules - `state` - Current workflow state - `troubleshooting` - Common issues and fixes ## Usage ``` /help # Overview and quick start /help commands # List all commands /help concepts # Explain concepts /help workflow # How workflows work /help state # Current workflow state /help troubleshooting # Common issues ``` ## Overview Response (no arguments) When user runs `/help` with no arguments: ``` Dragonfly WYSIWID Architecture - Quick Reference WHAT YOU SEE IS WHAT IT DOES Core Workflow: Story -> Architecture -> Implementation -> Quality -> Version Getting Started: /feature "description" Create a new feature /workflow "description" Run complete workflow automatically /sync Check current sync state Key Commands: /costs Show session costs /trace <id> Trace workflow history /health Check session health /checkpoint Save current state Need More Help? /help commands All available commands /help concepts How concepts work /help workflow Workflow details /help troubleshooting Common issues ``` ## Commands List Response When user runs `/help commands`: ``` Dragonfly Commands Reference WORKFLOW COMMANDS /feature <description> Create feature story, evaluate syncs /workflow <description> Run complete workflow automatically /sync Evaluate synchronization rules STATE & CONTEXT /checkpoint Save session state /restore Restore from checkpoint /health Check context usage /trace <id> Trace provenance chain COST & PERFORMANCE /costs Show session costs /predict-cost <desc> Estimate feature cost /slo View SLO metrics MEMORY /remember <fact> Store in semantic memory /recall <query> Retrieve from memory /global-remember Store across projects /global-recall Recall cross-project ANALYSIS /replay <id> Replay failed workflow /explore <question> Explore codebase /profile Profile project /retrospective Review workflow quality UTILITIES /cache Manage concept cache /classify <desc> Classify task type /estimate <desc> Estimate effort /pr-review Review pull request ``` ## Concepts Help Response When user runs `/help concepts`: ``` Dragonfly Concepts (10 Total) CORE WORKFLOW CONCEPTS story Captures user requirements (Opus) Actions: create, update, clarify, cancel architecture Designs technical approach (Opus) Actions: design, revise, validate implementation Generates code from specs (Opus) Actions: generate, refactor, fix quality Reviews code and runs tests (Opus) Actions: review, test, benchmark version Manages git operations (Opus) Actions: commit, tag, release context Manages context window (Opus) Actions: compress, snapshot, restore INTEGRATION CONCEPTS code-analysis Gathers codebase context via MCP (Opus) Actions: context, impact, profile security Validates security at each phase (Opus) Actions: threat_model, validate, scan verification Multi-pass independent review (Opus) Actions: verify_architecture, verify_implementation documentation Generates docs at each phase (Opus) Actions: generate, update, validate KEY PRINCIPLE: Concepts NEVER call other concepts directly. Synchronization rules orchestrate the workflow. ``` ## State Help Response When user runs `/help state`: First, check current state by reading data/ files: ``` Current Workflow State ACTIVE FLOWS flow-001: "Add user authentication" Status: in_progress Phase: implementation Story: story-001 (ready) Architecture: arch-001 (completed) Implementation: impl-001 (in_progress) RECENT ACTIONS 1. story.create -> completed (2 min ago) 2. architecture.design -> completed (1 min ago) 3. implementation.generate -> in_progress NEXT STEPS - Implementation completes - Sync triggers: impl-to-quality-review - Parallel: impl-to-quality-test CONTEXT USAGE Current: 35% Status: healthy Checkpoints: 1 ACTIONS YOU CAN TAKE /sync --execute Continue workflow /trace flow-001 See full history /checkpoint Save current state ``` ## Troubleshooting Response When user runs `/help troubleshooting`: ``` Dragonfly Troubleshooting Guide COMMON ISSUES 1. "Sync rule not firing" Cause: Prerequisites not met Fix: Check data/ state files - /trace <id> to see what's missing - Ensure previous concept completed successfully 2. "Context too high (>90%)" Cause: Long workflow without compression Fix: Create checkpoint and restore - /checkpoint "before continuing" - /restore if needed 3. "MCP server unavailable" Cause: MCP servers not running Fix: Workflow continues without code analysis - Check: mcp-servers/ for server status - MCP is optional - workflow gracefully degrades 4. "Architecture has high risk" Cause: Design detected risky patterns Fix: Review and approve or revise - Read data/architecture/arch-{id}.yaml - User decision required 5. "Quality review failed" Cause: Code issues found Fix: Check review findings - Read data/reviews/review-{id}.yaml - Fix issues and re-run quality 6. "Missing state file" Cause: Concept didn't complete Fix: Re-run previous step - Check data/ for existing state - /replay <id> to restart from failure DIAGNOSTIC COMMANDS /health Check overall health /trace <id> Trace specific flow /costs Check spending /sync --dry-run Preview sync evaluation GETTING HELP - Read .claude/synchronizations/*.yaml for workflow logic - Check data/provenance/ for action history - Review CLAUDE.md for project context ``` ## Context-Aware Behavior When providing help, check: 1. **Active Workflow**: If there's an in-progress flow, offer relevant next steps 2. **Recent Errors**: If data/ shows issues, suggest fixes 3. **Context Usage**: If high (>75%), suggest checkpoint 4. **MCP Status**: If unavailable, note graceful degradation ## Related Commands - `/health` - More detailed health status - `/trace` - Detailed provenance tracking - `/sync` - Manual sync evaluation

{ "prompt": "Display context-aware help for Dragonfly WYSIWID workflows and commands.\n\nWhen the user runs this command, you should:\n\n1. **Determine Help Context**\n - If no argument: Show overview of all commands\n - If topic provided: Show detailed help for that topic\n - If in workflow: Show current state and available actions\n\n2. **Available Topics**\n - `commands` - List all slash commands\n - `concepts` - Explain the 10 concepts\n - `workflow` - How workflows work\n - `sync` - Synchronization rules\n - `state` - Current workflow state\n - `troubleshooting` - Common issues and fixes\n\n## Usage\n\n```\n/help # Overview and quick start\n/help commands # List all commands\n/help concepts # Explain concepts\n/help workflow # How workflows work\n/help state # Current workflow state\n/help troubleshooting # Common issues\n```\n\n## Overview Response (no arguments)\n\nWhen user runs `/help` with no arguments:\n\n```\nDragonfly WYSIWID Architecture - Quick Reference\n\nWHAT YOU SEE IS WHAT IT DOES\n\nCore Workflow:\n Story -> Architecture -> Implementation -> Quality -> Version\n\nGetting Started:\n /feature \"description\" Create a new feature\n /workflow \"description\" Run complete workflow automatically\n /sync Check current sync state\n\nKey Commands:\n /costs Show session costs\n /trace <id> Trace workflow history\n /health Check session health\n /checkpoint Save current state\n\nNeed More Help?\n /help commands All available commands\n /help concepts How concepts work\n /help workflow Workflow details\n /help troubleshooting Common issues\n```\n\n## Commands List Response\n\nWhen user runs `/help commands`:\n\n```\nDragonfly Commands Reference\n\nWORKFLOW COMMANDS\n /feature <description> Create feature story, evaluate syncs\n /workflow <description> Run complete workflow automatically\n /sync Evaluate synchronization rules\n\nSTATE & CONTEXT\n /checkpoint Save session state\n /restore Restore from checkpoint\n /health Check context usage\n /trace <id> Trace provenance chain\n\nCOST & PERFORMANCE\n /costs Show session costs\n /predict-cost <desc> Estimate feature cost\n /slo View SLO metrics\n\nMEMORY\n /remember <fact> Store in semantic memory\n /recall <query> Retrieve from memory\n /global-remember Store across projects\n /global-recall Recall cross-project\n\nANALYSIS\n /replay <id> Replay failed workflow\n /explore <question> Explore codebase\n /profile Profile project\n /retrospective Review workflow quality\n\nUTILITIES\n /cache Manage concept cache\n /classify <desc> Classify task type\n /estimate <desc> Estimate effort\n /pr-review Review pull request\n```\n\n## Concepts Help Response\n\nWhen user runs `/help concepts`:\n\n```\nDragonfly Concepts (10 Total)\n\nCORE WORKFLOW CONCEPTS\n story Captures user requirements (Opus)\n Actions: create, update, clarify, cancel\n\n architecture Designs technical approach (Opus)\n Actions: design, revise, validate\n\n implementation Generates code from specs (Opus)\n Actions: generate, refactor, fix\n\n quality Reviews code and runs tests (Opus)\n Actions: review, test, benchmark\n\n version Manages git operations (Opus)\n Actions: commit, tag, release\n\n context Manages context window (Opus)\n Actions: compress, snapshot, restore\n\nINTEGRATION CONCEPTS\n code-analysis Gathers codebase context via MCP (Opus)\n Actions: context, impact, profile\n\n security Validates security at each phase (Opus)\n Actions: threat_model, validate, scan\n\n verification Multi-pass independent review (Opus)\n Actions: verify_architecture, verify_implementation\n\n documentation Generates docs at each phase (Opus)\n Actions: generate, update, validate\n\nKEY PRINCIPLE:\n Concepts NEVER call other concepts directly.\n Synchronization rules orchestrate the workflow.\n```\n\n## State Help Response\n\nWhen user runs `/help state`:\n\nFirst, check current state by reading data/ files:\n\n```\nCurrent Workflow State\n\nACTIVE FLOWS\n flow-001: \"Add user authentication\"\n Status: in_progress\n Phase: implementation\n Story: story-001 (ready)\n Architecture: arch-001 (completed)\n Implementation: impl-001 (in_progress)\n\nRECENT ACTIONS\n 1. story.create -> completed (2 min ago)\n 2. architecture.design -> completed (1 min ago)\n 3. implementation.generate -> in_progress\n\nNEXT STEPS\n - Implementation completes\n - Sync triggers: impl-to-quality-review\n - Parallel: impl-to-quality-test\n\nCONTEXT USAGE\n Current: 35%\n Status: healthy\n Checkpoints: 1\n\nACTIONS YOU CAN TAKE\n /sync --execute Continue workflow\n /trace flow-001 See full history\n /checkpoint Save current state\n```\n\n## Troubleshooting Response\n\nWhen user runs `/help troubleshooting`:\n\n```\nDragonfly Troubleshooting Guide\n\nCOMMON ISSUES\n\n1. \"Sync rule not firing\"\n Cause: Prerequisites not met\n Fix: Check data/ state files\n - /trace <id> to see what's missing\n - Ensure previous concept completed successfully\n\n2. \"Context too high (>90%)\"\n Cause: Long workflow without compression\n Fix: Create checkpoint and restore\n - /checkpoint \"before continuing\"\n - /restore if needed\n\n3. \"MCP server unavailable\"\n Cause: MCP servers not running\n Fix: Workflow continues without code analysis\n - Check: mcp-servers/ for server status\n - MCP is optional - workflow gracefully degrades\n\n4. \"Architecture has high risk\"\n Cause: Design detected risky patterns\n Fix: Review and approve or revise\n - Read data/architecture/arch-{id}.yaml\n - User decision required\n\n5. \"Quality review failed\"\n Cause: Code issues found\n Fix: Check review findings\n - Read data/reviews/review-{id}.yaml\n - Fix issues and re-run quality\n\n6. \"Missing state file\"\n Cause: Concept didn't complete\n Fix: Re-run previous step\n - Check data/ for existing state\n - /replay <id> to restart from failure\n\nDIAGNOSTIC COMMANDS\n /health Check overall health\n /trace <id> Trace specific flow\n /costs Check spending\n /sync --dry-run Preview sync evaluation\n\nGETTING HELP\n - Read .claude/synchronizations/*.yaml for workflow logic\n - Check data/provenance/ for action history\n - Review CLAUDE.md for project context\n```\n\n## Context-Aware Behavior\n\nWhen providing help, check:\n\n1. **Active Workflow**: If there's an in-progress flow, offer relevant next steps\n2. **Recent Errors**: If data/ shows issues, suggest fixes\n3. **Context Usage**: If high (>75%), suggest checkpoint\n4. **MCP Status**: If unavailable, note graceful degradation\n\n## Related Commands\n\n- `/health` - More detailed health status\n- `/trace` - Detailed provenance tracking\n- `/sync` - Manual sync evaluation", "variables": [], "notes": "Display context-aware help for Dragonfly WYSIWID workflows and commands.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/mkolb22/dockercd", "path": ".claude/commands/help.md", "ref": "4a344880aafd12349a7ad956378aaab982cc5e94", "url": "https://github.com/mkolb22/dockercd/blob/4a344880aafd12349a7ad956378aaab982cc5e94/.claude/commands/help.md", "key": "mkolb22/dockercd/.claude/commands/help.md" } } }

help

About

Usage

Overview Response (no arguments)

Commands List Response

Concepts Help Response

State Help Response

Troubleshooting Response

Context-Aware Behavior

Related Commands

Install help and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews