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.

task-transition - Prompt - OpenSmartRoute

Name: task-transition
Author: yuberalberto

Prompt file imported from yuberalberto/vjobs-landing (.windsurf/workflows/task-transition.md). Copyright stays with the author.

/task-transition

Goal

Archive completed task documentation, create new task documentation with structured template, and update features tracker atomically.

Steps

1. Validate Completion

Confirm the current task is actually complete
Verify task detail file exists in docs-project/
Check that all checklist items are marked [x]
Ask user for confirmation before proceeding

2. Archive Completed Task

Locate current task detail file: docs-project/[task-name].md
Create archive directory if needed: docs-project/archive/archived-tasks/
Move file to archive with timestamp: archived-[task-name]-YYYY-MM-DD.md
Verify file was moved successfully

3. Create New Task Documentation

Generate new task detail file: docs-project/[new-task-name].md
Use structured template with sections:
- Progress checklist
- Technical Specifications
- Implementation Steps
- Testing Checklist
- Risk Assessment
- Current Status
Include placeholders for user-specific configurations
Ensure all content is in English (code, comments, docs)

4. Update Features Tracker

Open docs-project/features_tracker.md
Move completed task from Progress to Done section
Add new task to Progress section with file reference
Reorganize Next section if needed
Fix numbering inconsistencies (N1, N2, N3, etc.)
Update metadata: Last updated date and current branch
Preserve all existing Done items

5. Verification

Confirm archived file exists in correct location
Verify new task file has complete structure
Check features_tracker.md has correct updates
Ensure no duplicate IDs or broken references

6. Summary Report

Provide clear summary:

Archived: File path and new location
Created: New task file with template structure
Updated: Features tracker changes
Next Steps: What user needs to provide (URLs, configs, etc.)

Usage

/task-transition [completed-task-name] [new-task-name] [new-task-title]

Examples:
/task-transition refactor-services-section calendly-integration "Calendly Integration - Replace Contact Form"
/task-transition mobile-optimization seo-implementation "Basic SEO Setup"

Template Structure for New Tasks

The workflow generates task documentation with this structure:

# [Task Title]

This document provides detailed specifications for [task description].

## Progress
- [ ] Step 1
- [ ] Step 2
- [ ] Step 3
- [ ] Documentation update

---

## Technical Specifications

### 1. [Component/Area] Changes 🛠️
**Current State:**
- [Description]

**Required Changes:**
- [List of changes]

### 2. [Another Component] Changes 🏗️
**Keep Existing:**
- [What to preserve]

**Replace/Update:**
- [What to change]

---

## Implementation Steps

### Phase 1: [Phase Name]
1. [Step 1]
2. [Step 2]

### Phase 2: [Phase Name]
1. [Step 1]
2. [Step 2]

---

## Files to Modify

### Primary Changes:
- `path/to/file.ext` - [Description]

### No Changes Needed:
- `path/to/file.ext` - [Reason]

---

## Testing Checklist

### Functionality:
- [ ] Test case 1
- [ ] Test case 2

### Responsive:
- [ ] Desktop (>992px)
- [ ] Tablet (768-992px)
- [ ] Mobile (<=768px)
- [ ] Small mobile (<=576px)

### Performance:
- [ ] Load time
- [ ] No console errors
- [ ] Memory usage

---

## Configuration Requirements
[Placeholders for user-specific settings]

---

## Risk Assessment & Mitigation

### Potential Issues:
1. **Issue 1**: Description
2. **Issue 2**: Description

### Mitigation Strategies:
- Strategy 1
- Strategy 2

---

## Current Status

**State:** Planning phase
**Priority:** [P1/N1/B1]
**Dependencies:** [List dependencies]
**Estimated Effort:** [Time estimate]

---

**Next Steps:**
1. [Action 1]
2. [Action 2]

Integration with Rules

This workflow applies:

Git discipline: No auto-commits, semantic commit style
Permission protocol: Ask before modifying files
Project tracking: Single source of truth in features_tracker.md
Documentation scope: Preserve archive as historical reference
Quality standards: English for all code/docs, Spanish for chat

Project-Specific Behavior

This workflow is specific to VJobs Landing because:

Uses docs-project/features_tracker.md as main tracker
Archives to docs-project/archive/archived-tasks/
Follows project's task ID system ([P1], [N1], [B1], [D1])
Respects project's documentation structure
Maintains responsive breakpoints in testing checklists

Safety Checks

Before execution:

✓ Verify completed task file exists
✓ Confirm task is actually complete
✓ Check archive directory exists
✓ Validate new task name is unique
✓ Ensure no filename conflicts

During execution:

✓ Backup before moving files
✓ Verify file operations succeed
✓ Check tracker updates are correct
✓ Preserve existing Done items

After execution:

✓ Confirm archived file in correct location
✓ Verify new task file is complete
✓ Check tracker has no broken references
✓ Ensure no duplicate IDs

Example Execution

Input: /task-transition refactor-services-section calendly-integration "Calendly Integration"

1. ✓ Validating completion of refactor-services-section
2. ✓ Moving docs-project/refactor-services-section.md
   → docs-project/archive/archived-tasks/archived-refactor-services-section-2026-01-20.md
3. ✓ Creating docs-project/calendly-integration.md with template
4. ✓ Updating features_tracker.md:
   - Moved [P2] to Done
   - Added [P1] Calendly integration to Progress
   - Fixed Next section numbering
   - Updated timestamp
5. ✓ Verification complete

Summary:
- Archived: refactor-services-section.md → archive/archived-tasks/
- Created: calendly-integration.md (206 lines, complete template)
- Updated: features_tracker.md (Progress, Next, Done sections)
- Next: User needs to provide Calendly event URL

Error Handling

If completed task file not found:

List available task files in docs-project/
Ask user to specify correct filename

If new task file already exists:

Warn about overwrite
Ask for confirmation or new name

If archive directory missing:

Create directory structure automatically
Confirm creation with user

If tracker update fails:

Rollback file operations
Report specific error
Ask for manual intervention

Workflow Chaining

This workflow integrates with:

/complete-feature - Use before task-transition to finalize work
/git-commit-workflow - Use after to commit changes
/code-integrity-check - Run before archiving task
/review-changes - Validate tracker updates

Notes

Always use absolute paths for file operations
Preserve exact formatting in features_tracker.md
Generate comprehensive task documentation
Include all responsive breakpoints in testing
Add placeholders for user-specific configurations
Maintain English for all generated content
Use Spanish only for user communication

Install task-transition 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.

# /task-transition ## Goal Archive completed task documentation, create new task documentation with structured template, and update features tracker atomically. ## Steps ### 1. Validate Completion - Confirm the current task is actually complete - Verify task detail file exists in `docs-project/` - Check that all checklist items are marked [x] - Ask user for confirmation before proceeding ### 2. Archive Completed Task - Locate current task detail file: `docs-project/[task-name].md` - Create archive directory if needed: `docs-project/archive/archived-tasks/` - Move file to archive with timestamp: `archived-[task-name]-YYYY-MM-DD.md` - Verify file was moved successfully ### 3. Create New Task Documentation - Generate new task detail file: `docs-project/[new-task-name].md` - Use structured template with sections: - Progress checklist - Technical Specifications - Implementation Steps - Testing Checklist - Risk Assessment - Current Status - Include placeholders for user-specific configurations - Ensure all content is in English (code, comments, docs) ### 4. Update Features Tracker - Open `docs-project/features_tracker.md` - Move completed task from Progress to Done section - Add new task to Progress section with file reference - Reorganize Next section if needed - Fix numbering inconsistencies (N1, N2, N3, etc.) - Update metadata: Last updated date and current branch - Preserve all existing Done items ### 5. Verification - Confirm archived file exists in correct location - Verify new task file has complete structure - Check features_tracker.md has correct updates - Ensure no duplicate IDs or broken references ### 6. Summary Report Provide clear summary: - **Archived**: File path and new location - **Created**: New task file with template structure - **Updated**: Features tracker changes - **Next Steps**: What user needs to provide (URLs, configs, etc.) ## Usage ```bash /task-transition [completed-task-name] [new-task-name] [new-task-title] Examples: /task-transition refactor-services-section calendly-integration "Calendly Integration - Replace Contact Form" /task-transition mobile-optimization seo-implementation "Basic SEO Setup" ``` ## Template Structure for New Tasks The workflow generates task documentation with this structure: ```markdown # [Task Title] This document provides detailed specifications for [task description]. ## Progress - [ ] Step 1 - [ ] Step 2 - [ ] Step 3 - [ ] Documentation update --- ## Technical Specifications ### 1. [Component/Area] Changes 🛠️ **Current State:** - [Description] **Required Changes:** - [List of changes] ### 2. [Another Component] Changes 🏗️ **Keep Existing:** - [What to preserve] **Replace/Update:** - [What to change] --- ## Implementation Steps ### Phase 1: [Phase Name] 1. [Step 1] 2. [Step 2] ### Phase 2: [Phase Name] 1. [Step 1] 2. [Step 2] --- ## Files to Modify ### Primary Changes: - `path/to/file.ext` - [Description] ### No Changes Needed: - `path/to/file.ext` - [Reason] --- ## Testing Checklist ### Functionality: - [ ] Test case 1 - [ ] Test case 2 ### Responsive: - [ ] Desktop (>992px) - [ ] Tablet (768-992px) - [ ] Mobile (<=768px) - [ ] Small mobile (<=576px) ### Performance: - [ ] Load time - [ ] No console errors - [ ] Memory usage --- ## Configuration Requirements [Placeholders for user-specific settings] --- ## Risk Assessment & Mitigation ### Potential Issues: 1. **Issue 1**: Description 2. **Issue 2**: Description ### Mitigation Strategies: - Strategy 1 - Strategy 2 --- ## Current Status **State:** Planning phase **Priority:** [P1/N1/B1] **Dependencies:** [List dependencies] **Estimated Effort:** [Time estimate] --- **Next Steps:** 1. [Action 1] 2. [Action 2] ``` ## Integration with Rules This workflow applies: - **Git discipline**: No auto-commits, semantic commit style - **Permission protocol**: Ask before modifying files - **Project tracking**: Single source of truth in features_tracker.md - **Documentation scope**: Preserve archive as historical reference - **Quality standards**: English for all code/docs, Spanish for chat ## Project-Specific Behavior This workflow is specific to VJobs Landing because: - Uses `docs-project/features_tracker.md` as main tracker - Archives to `docs-project/archive/archived-tasks/` - Follows project's task ID system ([P1], [N1], [B1], [D1]) - Respects project's documentation structure - Maintains responsive breakpoints in testing checklists ## Safety Checks Before execution: - ✓ Verify completed task file exists - ✓ Confirm task is actually complete - ✓ Check archive directory exists - ✓ Validate new task name is unique - ✓ Ensure no filename conflicts During execution: - ✓ Backup before moving files - ✓ Verify file operations succeed - ✓ Check tracker updates are correct - ✓ Preserve existing Done items After execution: - ✓ Confirm archived file in correct location - ✓ Verify new task file is complete - ✓ Check tracker has no broken references - ✓ Ensure no duplicate IDs ## Example Execution ``` Input: /task-transition refactor-services-section calendly-integration "Calendly Integration" 1. ✓ Validating completion of refactor-services-section 2. ✓ Moving docs-project/refactor-services-section.md → docs-project/archive/archived-tasks/archived-refactor-services-section-2026-01-20.md 3. ✓ Creating docs-project/calendly-integration.md with template 4. ✓ Updating features_tracker.md: - Moved [P2] to Done - Added [P1] Calendly integration to Progress - Fixed Next section numbering - Updated timestamp 5. ✓ Verification complete Summary: - Archived: refactor-services-section.md → archive/archived-tasks/ - Created: calendly-integration.md (206 lines, complete template) - Updated: features_tracker.md (Progress, Next, Done sections) - Next: User needs to provide Calendly event URL ``` ## Error Handling **If completed task file not found:** - List available task files in docs-project/ - Ask user to specify correct filename **If new task file already exists:** - Warn about overwrite - Ask for confirmation or new name **If archive directory missing:** - Create directory structure automatically - Confirm creation with user **If tracker update fails:** - Rollback file operations - Report specific error - Ask for manual intervention ## Workflow Chaining This workflow integrates with: - `/complete-feature` - Use before task-transition to finalize work - `/git-commit-workflow` - Use after to commit changes - `/code-integrity-check` - Run before archiving task - `/review-changes` - Validate tracker updates ## Notes - Always use absolute paths for file operations - Preserve exact formatting in features_tracker.md - Generate comprehensive task documentation - Include all responsive breakpoints in testing - Add placeholders for user-specific configurations - Maintain English for all generated content - Use Spanish only for user communication

{ "prompt": "# /task-transition\n\n## Goal\nArchive completed task documentation, create new task documentation with structured template, and update features tracker atomically.\n\n## Steps\n\n### 1. Validate Completion\n- Confirm the current task is actually complete\n- Verify task detail file exists in `docs-project/`\n- Check that all checklist items are marked [x]\n- Ask user for confirmation before proceeding\n\n### 2. Archive Completed Task\n- Locate current task detail file: `docs-project/[task-name].md`\n- Create archive directory if needed: `docs-project/archive/archived-tasks/`\n- Move file to archive with timestamp: `archived-[task-name]-YYYY-MM-DD.md`\n- Verify file was moved successfully\n\n### 3. Create New Task Documentation\n- Generate new task detail file: `docs-project/[new-task-name].md`\n- Use structured template with sections:\n - Progress checklist\n - Technical Specifications\n - Implementation Steps\n - Testing Checklist\n - Risk Assessment\n - Current Status\n- Include placeholders for user-specific configurations\n- Ensure all content is in English (code, comments, docs)\n\n### 4. Update Features Tracker\n- Open `docs-project/features_tracker.md`\n- Move completed task from Progress to Done section\n- Add new task to Progress section with file reference\n- Reorganize Next section if needed\n- Fix numbering inconsistencies (N1, N2, N3, etc.)\n- Update metadata: Last updated date and current branch\n- Preserve all existing Done items\n\n### 5. Verification\n- Confirm archived file exists in correct location\n- Verify new task file has complete structure\n- Check features_tracker.md has correct updates\n- Ensure no duplicate IDs or broken references\n\n### 6. Summary Report\nProvide clear summary:\n- **Archived**: File path and new location\n- **Created**: New task file with template structure\n- **Updated**: Features tracker changes\n- **Next Steps**: What user needs to provide (URLs, configs, etc.)\n\n## Usage\n```bash\n/task-transition [completed-task-name] [new-task-name] [new-task-title]\n\nExamples:\n/task-transition refactor-services-section calendly-integration \"Calendly Integration - Replace Contact Form\"\n/task-transition mobile-optimization seo-implementation \"Basic SEO Setup\"\n```\n\n## Template Structure for New Tasks\n\nThe workflow generates task documentation with this structure:\n\n```markdown\n# [Task Title]\n\nThis document provides detailed specifications for [task description].\n\n## Progress\n- [ ] Step 1\n- [ ] Step 2\n- [ ] Step 3\n- [ ] Documentation update\n\n---\n\n## Technical Specifications\n\n### 1. [Component/Area] Changes 🛠️\n**Current State:**\n- [Description]\n\n**Required Changes:**\n- [List of changes]\n\n### 2. [Another Component] Changes 🏗️\n**Keep Existing:**\n- [What to preserve]\n\n**Replace/Update:**\n- [What to change]\n\n---\n\n## Implementation Steps\n\n### Phase 1: [Phase Name]\n1. [Step 1]\n2. [Step 2]\n\n### Phase 2: [Phase Name]\n1. [Step 1]\n2. [Step 2]\n\n---\n\n## Files to Modify\n\n### Primary Changes:\n- `path/to/file.ext` - [Description]\n\n### No Changes Needed:\n- `path/to/file.ext` - [Reason]\n\n---\n\n## Testing Checklist\n\n### Functionality:\n- [ ] Test case 1\n- [ ] Test case 2\n\n### Responsive:\n- [ ] Desktop (>992px)\n- [ ] Tablet (768-992px)\n- [ ] Mobile (<=768px)\n- [ ] Small mobile (<=576px)\n\n### Performance:\n- [ ] Load time\n- [ ] No console errors\n- [ ] Memory usage\n\n---\n\n## Configuration Requirements\n[Placeholders for user-specific settings]\n\n---\n\n## Risk Assessment & Mitigation\n\n### Potential Issues:\n1. **Issue 1**: Description\n2. **Issue 2**: Description\n\n### Mitigation Strategies:\n- Strategy 1\n- Strategy 2\n\n---\n\n## Current Status\n\n**State:** Planning phase\n**Priority:** [P1/N1/B1]\n**Dependencies:** [List dependencies]\n**Estimated Effort:** [Time estimate]\n\n---\n\n**Next Steps:**\n1. [Action 1]\n2. [Action 2]\n```\n\n## Integration with Rules\n\nThis workflow applies:\n- **Git discipline**: No auto-commits, semantic commit style\n- **Permission protocol**: Ask before modifying files\n- **Project tracking**: Single source of truth in features_tracker.md\n- **Documentation scope**: Preserve archive as historical reference\n- **Quality standards**: English for all code/docs, Spanish for chat\n\n## Project-Specific Behavior\n\nThis workflow is specific to VJobs Landing because:\n- Uses `docs-project/features_tracker.md` as main tracker\n- Archives to `docs-project/archive/archived-tasks/`\n- Follows project's task ID system ([P1], [N1], [B1], [D1])\n- Respects project's documentation structure\n- Maintains responsive breakpoints in testing checklists\n\n## Safety Checks\n\nBefore execution:\n- ✓ Verify completed task file exists\n- ✓ Confirm task is actually complete\n- ✓ Check archive directory exists\n- ✓ Validate new task name is unique\n- ✓ Ensure no filename conflicts\n\nDuring execution:\n- ✓ Backup before moving files\n- ✓ Verify file operations succeed\n- ✓ Check tracker updates are correct\n- ✓ Preserve existing Done items\n\nAfter execution:\n- ✓ Confirm archived file in correct location\n- ✓ Verify new task file is complete\n- ✓ Check tracker has no broken references\n- ✓ Ensure no duplicate IDs\n\n## Example Execution\n\n```\nInput: /task-transition refactor-services-section calendly-integration \"Calendly Integration\"\n\n1. ✓ Validating completion of refactor-services-section\n2. ✓ Moving docs-project/refactor-services-section.md\n → docs-project/archive/archived-tasks/archived-refactor-services-section-2026-01-20.md\n3. ✓ Creating docs-project/calendly-integration.md with template\n4. ✓ Updating features_tracker.md:\n - Moved [P2] to Done\n - Added [P1] Calendly integration to Progress\n - Fixed Next section numbering\n - Updated timestamp\n5. ✓ Verification complete\n\nSummary:\n- Archived: refactor-services-section.md → archive/archived-tasks/\n- Created: calendly-integration.md (206 lines, complete template)\n- Updated: features_tracker.md (Progress, Next, Done sections)\n- Next: User needs to provide Calendly event URL\n```\n\n## Error Handling\n\n**If completed task file not found:**\n- List available task files in docs-project/\n- Ask user to specify correct filename\n\n**If new task file already exists:**\n- Warn about overwrite\n- Ask for confirmation or new name\n\n**If archive directory missing:**\n- Create directory structure automatically\n- Confirm creation with user\n\n**If tracker update fails:**\n- Rollback file operations\n- Report specific error\n- Ask for manual intervention\n\n## Workflow Chaining\n\nThis workflow integrates with:\n- `/complete-feature` - Use before task-transition to finalize work\n- `/git-commit-workflow` - Use after to commit changes\n- `/code-integrity-check` - Run before archiving task\n- `/review-changes` - Validate tracker updates\n\n## Notes\n\n- Always use absolute paths for file operations\n- Preserve exact formatting in features_tracker.md\n- Generate comprehensive task documentation\n- Include all responsive breakpoints in testing\n- Add placeholders for user-specific configurations\n- Maintain English for all generated content\n- Use Spanish only for user communication", "variables": [], "notes": "Transition from completed task to new task with full documentation", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/yuberalberto/vjobs-landing", "path": ".windsurf/workflows/task-transition.md", "ref": "e790886dd8e3a36864a354fc194b3f34c9fb279e", "url": "https://github.com/yuberalberto/vjobs-landing/blob/e790886dd8e3a36864a354fc194b3f34c9fb279e/.windsurf/workflows/task-transition.md", "key": "yuberalberto/vjobs-landing/.windsurf/workflows/task-transition.md" } } }

task-transition

About