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.

daily-update - Prompt - OpenSmartRoute

Name: daily-update
Author: cameza

Prompt file imported from cameza/ai-missions-system (.windsurf/workflows/daily-update.md). Copyright stays with the author.

Daily Update Workflow

Server Required: Official Linear MCP Server (linear-mcp-server) - mcp2_* tools Purpose: Read issues and data from Linear (READ operations)

This workflow automates the process of generating daily project progress updates by fetching completed issues from Linear and formatting them into a structured update.

Prerequisites

Access to Linear workspace with MCP integration
Linear project with proper issue tracking and phases
Understanding of project phases and ticket structure
TPM role or project management responsibilities

Step 1: Fetch Today's Completed Issues (5 minutes)

Use Linear MCP to get completed issues:

# Get issues completed today (last 24 hours)
mcp2_list_issues --project "Mission 1: Resolution Tracker" --state "Done" --updatedAt "-P1D"

Filter results:

Only include issues with updatedAt timestamp from today
Exclude issues completed on previous days
Group by phase/feature area

Step 2: Analyze Progress Data (5 minutes)

Count completed issues by phase:

Phase 0: Setup
Phase 1: Foundation
Phase 2: Shared Components
Phase 3: Core Features
Phase 4: Polish & Enhancement
Phase 5: Quality & Deployment

Calculate progress metrics:

Total issues completed today
Overall project completion percentage
Phase completion percentages
Velocity assessment

Step 3: Generate Update Template (10 minutes)

Use the following template structure:

# [Project Name] - Daily Progress Update

## ✅ COMPLETED Issues Today ([X] tickets)

**[Phase Name]**
- MCS-[XX]: [Issue Title] ✅ DONE
- MCS-[XX]: [Issue Title] ✅ DONE

## 📈 Progress Summary

**Completed Today: [X]/[Total] tickets ([X]%)**
**Overall Progress: [Completed]/[Total] tickets ([X]%)**

- [Phase 1]: [X]/[Y] complete ✅
- [Phase 2]: [X]/[Y] complete ✅
- Remaining work: [X] tickets pending

## 🚀 Achievement Highlights

- **[Key Achievement 1]**: [Description]
- **[Key Achievement 2]**: [Description]
- **[Key Achievement 3]**: [Description]
- **[Key Achievement 4]**: [Description]

## 🎯 Next Steps

- MCS-[XX]: [Next Priority Issue]
- MCS-[XX]: [Second Priority Issue]
- MCS-[XX]: [Third Priority Issue]

## 📊 TPM Assessment

**Velocity**: [Assessment of today's progress]
**Critical Path**: [Current critical path items]
**Risk**: [Any identified risks or blockers]
**Timeline**: [Timeline assessment and schedule status]

**Recommendation**: [Actionable recommendation for next steps]

Step 4: Customize Content (10 minutes)

Fill in template sections:

Achievement Highlights:

Focus on major milestones reached
Highlight integration achievements
Note completion of significant features
Mention foundation work that enables future progress

Next Steps:

Prioritize critical path items
Focus on blocking dependencies
Consider upcoming phase transitions
Address any identified risks

TPM Assessment:

Evaluate velocity against expectations
Identify any schedule impacts
Note resource allocation needs
Provide strategic recommendations

Step 5: Review and Finalize (5 minutes)

Quality checks:

All completed issues from today are included
Progress calculations are accurate
Phase groupings are correct
Achievement highlights are meaningful
Next steps are prioritized correctly
TPM assessment is actionable

Final review:

Check for consistent formatting
Verify ticket numbers and titles
Ensure percentage calculations are correct
Validate phase completion status

Automation Script Example

For automated execution, use this script structure:

// Script to fetch daily completed issues and generate update
async function generateDailyUpdate() {
  // 1. Fetch today's completed issues
  const completedIssues = await mcp2_list_issues({
    project: "Mission 1: Resolution Tracker",
    state: "Done",
    updatedAt: "-P1D"
  });
  
  // 2. Group by phase
  const issuesByPhase = groupByPhase(completedIssues);
  
  // 3. Calculate metrics
  const metrics = calculateProgressMetrics(completedIssues);
  
  // 4. Generate update
  const update = generateUpdateTemplate(issuesByPhase, metrics);
  
  // 5. Return formatted update
  return update;
}

Best Practices

Content Guidelines:

Keep updates concise and focused on progress
Use consistent formatting and terminology
Highlight achievements that move the project forward
Provide actionable next steps and recommendations

Timing:

Run workflow at end of each workday
Include all issues completed during business hours
Consider timezone differences for distributed teams

Quality Assurance:

Double-check issue completion dates
Verify phase classifications are correct
Ensure progress metrics are accurate
Review for clarity and professionalism

Template Customization

Project-specific adjustments:

Update project name in title
Adjust phase names to match your project structure
Modify achievement highlight categories
Customize TPM assessment criteria

Styling options:

Add project-specific branding elements
Include team mentions or acknowledgments
Add links to relevant documentation
Include stakeholder-specific information

Integration Options

Linear Integration:

Use Linear webhooks for real-time updates
Schedule automated runs at specific times
Integrate with Linear cycle tracking
Connect to Linear team milestones

Communication Channels:

Post updates to Slack/Discord
Send email summaries to stakeholders
Update project dashboards
Archive in project documentation

Troubleshooting

Common Issues:

Missing issues: Check date range filters
Incorrect metrics: Verify total ticket count
Phase errors: Ensure proper labeling in Linear
Format issues: Check markdown syntax

Data Validation:

Cross-check with Linear UI
Verify issue completion timestamps
Confirm project phase definitions
Test with sample data

Usage Examples

Daily Standup Update:

Completed 4 core feature tickets today, achieving 57% overall project completion. 
Major achievement: Full mission management flow is now functional. 
Next priority: Complete final core feature (Mission Detail View).

Stakeholder Summary:

Excellent progress today with 4 major features completed. 
The project is significantly ahead of schedule with strong foundation and nearly complete feature set. 
No blockers identified - ready to complete final MVP features.

Team Retrospective:

Outstanding velocity completing 4 feature tickets. 
Successful integration of all UI components into working features. 
Recommend focusing on Mission Detail View to achieve full MVP functionality.

Workflow Duration: 25-35 minutes Frequency: Daily (end of business day) Owner: TPM or Project Manager Required Tools: Linear MCP, Markdown editor

Install daily-update 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.

# Daily Update Workflow **Server Required**: Official Linear MCP Server (linear-mcp-server) - `mcp2_*` tools **Purpose**: Read issues and data from Linear (READ operations) This workflow automates the process of generating daily project progress updates by fetching completed issues from Linear and formatting them into a structured update. ## Prerequisites - Access to Linear workspace with MCP integration - Linear project with proper issue tracking and phases - Understanding of project phases and ticket structure - TPM role or project management responsibilities ## Step 1: Fetch Today's Completed Issues (5 minutes) **Use Linear MCP to get completed issues:** ```bash # Get issues completed today (last 24 hours) mcp2_list_issues --project "Mission 1: Resolution Tracker" --state "Done" --updatedAt "-P1D" ``` **Filter results:** - Only include issues with `updatedAt` timestamp from today - Exclude issues completed on previous days - Group by phase/feature area ## Step 2: Analyze Progress Data (5 minutes) **Count completed issues by phase:** - Phase 0: Setup - Phase 1: Foundation - Phase 2: Shared Components - Phase 3: Core Features - Phase 4: Polish & Enhancement - Phase 5: Quality & Deployment **Calculate progress metrics:** - Total issues completed today - Overall project completion percentage - Phase completion percentages - Velocity assessment ## Step 3: Generate Update Template (10 minutes) **Use the following template structure:** ```markdown # [Project Name] - Daily Progress Update ## ✅ COMPLETED Issues Today ([X] tickets) **[Phase Name]** - MCS-[XX]: [Issue Title] ✅ DONE - MCS-[XX]: [Issue Title] ✅ DONE ## 📈 Progress Summary **Completed Today: [X]/[Total] tickets ([X]%)** **Overall Progress: [Completed]/[Total] tickets ([X]%)** - [Phase 1]: [X]/[Y] complete ✅ - [Phase 2]: [X]/[Y] complete ✅ - Remaining work: [X] tickets pending ## 🚀 Achievement Highlights - **[Key Achievement 1]**: [Description] - **[Key Achievement 2]**: [Description] - **[Key Achievement 3]**: [Description] - **[Key Achievement 4]**: [Description] ## 🎯 Next Steps - MCS-[XX]: [Next Priority Issue] - MCS-[XX]: [Second Priority Issue] - MCS-[XX]: [Third Priority Issue] ## 📊 TPM Assessment **Velocity**: [Assessment of today's progress] **Critical Path**: [Current critical path items] **Risk**: [Any identified risks or blockers] **Timeline**: [Timeline assessment and schedule status] **Recommendation**: [Actionable recommendation for next steps] ``` ## Step 4: Customize Content (10 minutes) **Fill in template sections:** **Achievement Highlights:** - Focus on major milestones reached - Highlight integration achievements - Note completion of significant features - Mention foundation work that enables future progress **Next Steps:** - Prioritize critical path items - Focus on blocking dependencies - Consider upcoming phase transitions - Address any identified risks **TPM Assessment:** - Evaluate velocity against expectations - Identify any schedule impacts - Note resource allocation needs - Provide strategic recommendations ## Step 5: Review and Finalize (5 minutes) **Quality checks:** - [ ] All completed issues from today are included - [ ] Progress calculations are accurate - [ ] Phase groupings are correct - [ ] Achievement highlights are meaningful - [ ] Next steps are prioritized correctly - [ ] TPM assessment is actionable **Final review:** - Check for consistent formatting - Verify ticket numbers and titles - Ensure percentage calculations are correct - Validate phase completion status ## Automation Script Example **For automated execution, use this script structure:** ```typescript // Script to fetch daily completed issues and generate update async function generateDailyUpdate() { // 1. Fetch today's completed issues const completedIssues = await mcp2_list_issues({ project: "Mission 1: Resolution Tracker", state: "Done", updatedAt: "-P1D" }); // 2. Group by phase const issuesByPhase = groupByPhase(completedIssues); // 3. Calculate metrics const metrics = calculateProgressMetrics(completedIssues); // 4. Generate update const update = generateUpdateTemplate(issuesByPhase, metrics); // 5. Return formatted update return update; } ``` ## Best Practices **Content Guidelines:** - Keep updates concise and focused on progress - Use consistent formatting and terminology - Highlight achievements that move the project forward - Provide actionable next steps and recommendations **Timing:** - Run workflow at end of each workday - Include all issues completed during business hours - Consider timezone differences for distributed teams **Quality Assurance:** - Double-check issue completion dates - Verify phase classifications are correct - Ensure progress metrics are accurate - Review for clarity and professionalism ## Template Customization **Project-specific adjustments:** - Update project name in title - Adjust phase names to match your project structure - Modify achievement highlight categories - Customize TPM assessment criteria **Styling options:** - Add project-specific branding elements - Include team mentions or acknowledgments - Add links to relevant documentation - Include stakeholder-specific information ## Integration Options **Linear Integration:** - Use Linear webhooks for real-time updates - Schedule automated runs at specific times - Integrate with Linear cycle tracking - Connect to Linear team milestones **Communication Channels:** - Post updates to Slack/Discord - Send email summaries to stakeholders - Update project dashboards - Archive in project documentation ## Troubleshooting **Common Issues:** - Missing issues: Check date range filters - Incorrect metrics: Verify total ticket count - Phase errors: Ensure proper labeling in Linear - Format issues: Check markdown syntax **Data Validation:** - Cross-check with Linear UI - Verify issue completion timestamps - Confirm project phase definitions - Test with sample data ## Usage Examples **Daily Standup Update:** ``` Completed 4 core feature tickets today, achieving 57% overall project completion. Major achievement: Full mission management flow is now functional. Next priority: Complete final core feature (Mission Detail View). ``` **Stakeholder Summary:** ``` Excellent progress today with 4 major features completed. The project is significantly ahead of schedule with strong foundation and nearly complete feature set. No blockers identified - ready to complete final MVP features. ``` **Team Retrospective:** ``` Outstanding velocity completing 4 feature tickets. Successful integration of all UI components into working features. Recommend focusing on Mission Detail View to achieve full MVP functionality. ``` --- **Workflow Duration:** 25-35 minutes **Frequency:** Daily (end of business day) **Owner:** TPM or Project Manager **Required Tools:** Linear MCP, Markdown editor

{ "prompt": "# Daily Update Workflow\n\n**Server Required**: Official Linear MCP Server (linear-mcp-server) - `mcp2_*` tools\n**Purpose**: Read issues and data from Linear (READ operations)\n\nThis workflow automates the process of generating daily project progress updates by fetching completed issues from Linear and formatting them into a structured update.\n\n## Prerequisites\n- Access to Linear workspace with MCP integration\n- Linear project with proper issue tracking and phases\n- Understanding of project phases and ticket structure\n- TPM role or project management responsibilities\n\n## Step 1: Fetch Today's Completed Issues (5 minutes)\n\n**Use Linear MCP to get completed issues:**\n```bash\n# Get issues completed today (last 24 hours)\nmcp2_list_issues --project \"Mission 1: Resolution Tracker\" --state \"Done\" --updatedAt \"-P1D\"\n```\n\n**Filter results:**\n- Only include issues with `updatedAt` timestamp from today\n- Exclude issues completed on previous days\n- Group by phase/feature area\n\n## Step 2: Analyze Progress Data (5 minutes)\n\n**Count completed issues by phase:**\n- Phase 0: Setup\n- Phase 1: Foundation \n- Phase 2: Shared Components\n- Phase 3: Core Features\n- Phase 4: Polish & Enhancement\n- Phase 5: Quality & Deployment\n\n**Calculate progress metrics:**\n- Total issues completed today\n- Overall project completion percentage\n- Phase completion percentages\n- Velocity assessment\n\n## Step 3: Generate Update Template (10 minutes)\n\n**Use the following template structure:**\n\n```markdown\n# [Project Name] - Daily Progress Update\n\n## ✅ COMPLETED Issues Today ([X] tickets)\n\n**[Phase Name]**\n- MCS-[XX]: [Issue Title] ✅ DONE\n- MCS-[XX]: [Issue Title] ✅ DONE\n\n## 📈 Progress Summary\n\n**Completed Today: [X]/[Total] tickets ([X]%)**\n**Overall Progress: [Completed]/[Total] tickets ([X]%)**\n\n- [Phase 1]: [X]/[Y] complete ✅\n- [Phase 2]: [X]/[Y] complete ✅\n- Remaining work: [X] tickets pending\n\n## 🚀 Achievement Highlights\n\n- **[Key Achievement 1]**: [Description]\n- **[Key Achievement 2]**: [Description]\n- **[Key Achievement 3]**: [Description]\n- **[Key Achievement 4]**: [Description]\n\n## 🎯 Next Steps\n\n- MCS-[XX]: [Next Priority Issue]\n- MCS-[XX]: [Second Priority Issue]\n- MCS-[XX]: [Third Priority Issue]\n\n## 📊 TPM Assessment\n\n**Velocity**: [Assessment of today's progress]\n**Critical Path**: [Current critical path items]\n**Risk**: [Any identified risks or blockers]\n**Timeline**: [Timeline assessment and schedule status]\n\n**Recommendation**: [Actionable recommendation for next steps]\n```\n\n## Step 4: Customize Content (10 minutes)\n\n**Fill in template sections:**\n\n**Achievement Highlights:**\n- Focus on major milestones reached\n- Highlight integration achievements\n- Note completion of significant features\n- Mention foundation work that enables future progress\n\n**Next Steps:**\n- Prioritize critical path items\n- Focus on blocking dependencies\n- Consider upcoming phase transitions\n- Address any identified risks\n\n**TPM Assessment:**\n- Evaluate velocity against expectations\n- Identify any schedule impacts\n- Note resource allocation needs\n- Provide strategic recommendations\n\n## Step 5: Review and Finalize (5 minutes)\n\n**Quality checks:**\n- [ ] All completed issues from today are included\n- [ ] Progress calculations are accurate\n- [ ] Phase groupings are correct\n- [ ] Achievement highlights are meaningful\n- [ ] Next steps are prioritized correctly\n- [ ] TPM assessment is actionable\n\n**Final review:**\n- Check for consistent formatting\n- Verify ticket numbers and titles\n- Ensure percentage calculations are correct\n- Validate phase completion status\n\n## Automation Script Example\n\n**For automated execution, use this script structure:**\n\n```typescript\n// Script to fetch daily completed issues and generate update\nasync function generateDailyUpdate() {\n // 1. Fetch today's completed issues\n const completedIssues = await mcp2_list_issues({\n project: \"Mission 1: Resolution Tracker\",\n state: \"Done\",\n updatedAt: \"-P1D\"\n });\n \n // 2. Group by phase\n const issuesByPhase = groupByPhase(completedIssues);\n \n // 3. Calculate metrics\n const metrics = calculateProgressMetrics(completedIssues);\n \n // 4. Generate update\n const update = generateUpdateTemplate(issuesByPhase, metrics);\n \n // 5. Return formatted update\n return update;\n}\n```\n\n## Best Practices\n\n**Content Guidelines:**\n- Keep updates concise and focused on progress\n- Use consistent formatting and terminology\n- Highlight achievements that move the project forward\n- Provide actionable next steps and recommendations\n\n**Timing:**\n- Run workflow at end of each workday\n- Include all issues completed during business hours\n- Consider timezone differences for distributed teams\n\n**Quality Assurance:**\n- Double-check issue completion dates\n- Verify phase classifications are correct\n- Ensure progress metrics are accurate\n- Review for clarity and professionalism\n\n## Template Customization\n\n**Project-specific adjustments:**\n- Update project name in title\n- Adjust phase names to match your project structure\n- Modify achievement highlight categories\n- Customize TPM assessment criteria\n\n**Styling options:**\n- Add project-specific branding elements\n- Include team mentions or acknowledgments\n- Add links to relevant documentation\n- Include stakeholder-specific information\n\n## Integration Options\n\n**Linear Integration:**\n- Use Linear webhooks for real-time updates\n- Schedule automated runs at specific times\n- Integrate with Linear cycle tracking\n- Connect to Linear team milestones\n\n**Communication Channels:**\n- Post updates to Slack/Discord\n- Send email summaries to stakeholders\n- Update project dashboards\n- Archive in project documentation\n\n## Troubleshooting\n\n**Common Issues:**\n- Missing issues: Check date range filters\n- Incorrect metrics: Verify total ticket count\n- Phase errors: Ensure proper labeling in Linear\n- Format issues: Check markdown syntax\n\n**Data Validation:**\n- Cross-check with Linear UI\n- Verify issue completion timestamps\n- Confirm project phase definitions\n- Test with sample data\n\n## Usage Examples\n\n**Daily Standup Update:**\n```\nCompleted 4 core feature tickets today, achieving 57% overall project completion. \nMajor achievement: Full mission management flow is now functional. \nNext priority: Complete final core feature (Mission Detail View).\n```\n\n**Stakeholder Summary:**\n```\nExcellent progress today with 4 major features completed. \nThe project is significantly ahead of schedule with strong foundation and nearly complete feature set. \nNo blockers identified - ready to complete final MVP features.\n```\n\n**Team Retrospective:**\n```\nOutstanding velocity completing 4 feature tickets. \nSuccessful integration of all UI components into working features. \nRecommend focusing on Mission Detail View to achieve full MVP functionality.\n```\n\n---\n\n**Workflow Duration:** 25-35 minutes\n**Frequency:** Daily (end of business day)\n**Owner:** TPM or Project Manager\n**Required Tools:** Linear MCP, Markdown editor", "variables": [], "notes": "This workflow automates the process of generating daily project progress updates by fetching completed issues from Linear and formatting them into a structured update.", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/cameza/ai-missions-system", "path": ".windsurf/workflows/daily-update.md", "ref": "d5dc6456e455378d1118a4f54d3d617edbfebce4", "url": "https://github.com/cameza/ai-missions-system/blob/d5dc6456e455378d1118a4f54d3d617edbfebce4/.windsurf/workflows/daily-update.md", "key": "cameza/ai-missions-system/.windsurf/workflows/daily-update.md" } } }

daily-update

About

Daily Update Workflow

Prerequisites

Step 1: Fetch Today's Completed Issues (5 minutes)

Step 2: Analyze Progress Data (5 minutes)

Step 3: Generate Update Template (10 minutes)

Step 4: Customize Content (10 minutes)

Step 5: Review and Finalize (5 minutes)

Automation Script Example

Best Practices

Template Customization

Integration Options

Troubleshooting

Usage Examples

Install daily-update 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