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.

feature-request - Prompt - OpenSmartRoute

Name: feature-request
Author: danilonovaisv

Prompt file imported from danilonovaisv/SCENES-GENERATOR (.windsurf/workflows/core/feature/feature-request.md). Copyright stays with the author.

Feature Request Workflow

The Feature Request system provides comprehensive tracking and annotation capabilities for feature requests with granular command aliases and automatic code/shell script annotation.

Usage

Granular Command Aliases

The system supports multiple levels of command granularity:

# Full form
max:feature-request create "Add new feature" "Description here" --priority high

# Short form
max:fr list --status open

# Minimal form
m:fr show FR-20250220-001

# Legacy forms
feature-request update FR-20250220-001 --status in_progress
fr create "Quick feature" "Simple description"

Basic Operations

Create Feature Request

# Basic creation
max:feature-request create "Add dark mode" "Implement dark theme for UI" --priority high

# With tags
max:fr create "API endpoints" "Add REST API for user management" --tags api,backend --priority medium

# From file
m:fr create "Complex feature" --file feature_description.md --priority critical

List and Filter

# List all requests
max:feature-request list

# Filter by status
max:fr list --status open

# Filter by priority
feature-request list --priority high

# Combined filters
m:fr list --status open --priority high

View Details

# Show specific request
max:feature-request show FR-20250220-001

# Short form
m:fr show FR-20250220-001

Update Requests

# Update status
max:fr update FR-20250220-001 --status in_progress

# Update priority
feature-request update FR-20250220-001 --priority critical

# Both status and priority
m:fr update FR-20250220-001 --status completed --priority low

Delete Requests

# Delete a request
max:feature-request delete FR-20250220-001

Annotation Features

Automatic Code Block Annotation

The system automatically detects and annotates code blocks in feature request descriptions:

Python Code Annotation

def process_data(data):
    # 📝 Function: process_data - defines reusable logic
    for item in data:
        # 📝 Loop - iterates over sequence
        if item.is_valid():
            # 📝 Conditional logic - controls program flow
            yield transform(item)

Shell Command Annotation

cd /Users/ethandellaposta/Documents/git/MAx
# 📋 Navigate to directory: /Users/ethandellaposta/Documents/git/MAx
git log --oneline --since="2 weeks ago"
# 📋 Git operation: log
&& git show --name-only HEAD
# 📋 Chain command - execute if previous succeeds

Mixed Content Annotation

The system handles mixed content with multiple annotation types:

Based on my analysis, I can see that the workflow needs updates.

Command cd, git
cd /Users/ethandellaposta/Documents/git/MAx && git log --oneline
# 📋 Navigate to directory: /Users/ethandellaposta/Documents/git/MAx
# 📋 Chain command - execute if previous succeeds
# 📋 Git operation: log

```python
# 📝 Import: specific module import - targeted functionality
from feature_request import FeatureRequestSystem

def main():
    # 📝 Function: main - defines reusable logic
    system = FeatureRequestSystem()
    # 📝 Import: FeatureRequestSystem - brings in external functionality

Command Reference

Actions

Action	Description	Example
`create`	Create new feature request	`max:fr create "Title" "Description"`
`list`	List feature requests	`max:fr list --status open`
`show`	Show specific request	`max:fr show FR-20250220-001`
`update`	Update request status/priority	`max:fr update FR-001 --status in_progress`
`delete`	Delete a request	`max:fr delete FR-20250220-001`

Options

Option	Description	Values
`--title`	Request title	String
`--description`	Request description	String
`--priority`	Priority level	low, medium, high, critical
`--status`	Status filter	open, in_progress, completed, rejected
`--tags`	Categorization tags	List of strings
`--file`	Read description from file	File path

Alias Hierarchy

max:feature-request  (Full form - most explicit)
     ↓
max:fr              (Short form - balanced)
     ↓
m:fr                (Minimal form - quickest)
     ↓
feature-request     (Legacy form - compatible)
     ↓
fr                  (Shortest form - minimal)

Annotation Patterns

Code Block Detection

The system detects:

Markdown code blocks with language specification
Shell command blocks with command prefixes
Mixed content with multiple annotation types

Annotation Types

Type	Trigger	Example
Function definition	`def` or `class`	`# 📝 Function: name - defines reusable logic`
Import statements	`import` or `from`	`# 📝 Import: module - brings in external functionality`
Control structures	`if` , `for` , `while`	`# 📝 Conditional logic - controls program flow`
Shell commands	`cd` , `git` , `ls`	`# 📋 Navigate to directory: path`
Command chaining	`&&`, `

Annotation Logic

The annotation system:

Detects blocks using regex patterns
Analyzes content for specific patterns
Adds contextual annotations after relevant lines
Preserves original code while adding insights
Handles multiple languages (Python, Bash, JavaScript, etc.)

Integration

With Git Hooks

Add to pre-commit hooks for feature request validation:

# .pre-commit-config.yaml
repos:
  - repo: local
    hooks:
      - id: feature-request-check
        name: Feature Request Validation
        entry: python3 .max/feature_request.py list
        language: system

With IDE

The command aliases work directly in IDE command palette:

max:feature-request - Full feature request operations
max:fr - Quick feature request actions
m:fr - Rapid feature request management

With CI/CD

Integrate with GitHub Actions:

# .github/workflows/feature-requests.yml
name: Feature Request Check
on: [pull_request]
jobs:
  check-requests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: List open feature requests
        run: python3 .max/feature_request.py list --status open

Data Storage

Feature requests are stored in .max/feature_requests.json with the following structure:

[
  {
    "id": "FR-20250220-001",
    "title": "Feature title",
    "description": "Detailed description with code blocks",
    "priority": "high",
    "status": "open",
    "created_at": "2025-02-20T12:00:00",
    "updated_at": "2025-02-20T12:00:00",
    "annotations": ["Found code_block at lines 5-10"],
    "code_blocks": [
      {
        "type": "code_block",
        "language": "python",
        "original": "def example():\n    pass",
        "annotated": "def example():\n    # 📝 Function: example - defines reusable logic\n    pass",
        "line_start": 5,
        "line_end": 6
      }
    ],
    "tags": ["enhancement", "ui"]
  }
]

Best Practices

1. Use Granular Aliases

Full form for documentation and scripts: max:feature-request
Short form for daily use: max:fr
Minimal form for quick operations: m:fr

2. Write Annotatable Descriptions

Include code blocks and commands in descriptions:

Need to implement the following:

```python
def new_feature():
    # Implementation here
    pass

Shell commands for testing:

cd project && python test_new_feature.py

3. Use Tags Effectively

Categorize requests for better organization:

max:fr create "API feature" "Description" --tags api,backend,high-priority

4. Regular Status Updates

Keep requests current:

m:fr update FR-001 --status in_progress
# Work on feature...
m:fr update FR-001 --status completed

Examples

Complete Workflow

# Create feature request with detailed description
max:feature-request create "Add user authentication" """
Implement OAuth2 authentication with the following:

```python
# 📝 Import: specific module import - targeted functionality
from authlib.integrations.flask_client import OAuth

def setup_oauth(app):
    # 📝 Function: setup_oauth - defines reusable logic
    oauth = OAuth(app)
    # Configure OAuth providers...

Shell commands for setup:

# 📋 Navigate to directory: /project
cd /project
# 📋 Git operation: checkout
git checkout -b feature/auth
# 📋 Chain command - execute if previous succeeds
&& pip install authlib

""" --priority high --tags security,authentication

List high priority open requests

max:fr list --status open --priority high

Update status when starting work

m:fr update FR-20250220-001 --status in_progress

Mark as completed when done

feature-request update FR-20250220-001 --status completed


### Quick Operations

```bash
# Quick status check
m:fr list

# Fast feature creation
fr create "Quick fix" "Minor bug fix" --priority low

# Rapid status update
m:fr update FR-001 --status completed

🚀 The Feature Request system provides comprehensive tracking with intelligent annotation and granular command control!

Install feature-request 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.

# Feature Request Workflow The Feature Request system provides comprehensive tracking and annotation capabilities for feature requests with granular command aliases and automatic code/shell script annotation. ## Usage ### Granular Command Aliases The system supports multiple levels of command granularity: ```bash # Full form max:feature-request create "Add new feature" "Description here" --priority high # Short form max:fr list --status open # Minimal form m:fr show FR-20250220-001 # Legacy forms feature-request update FR-20250220-001 --status in_progress fr create "Quick feature" "Simple description" ``` ### Basic Operations #### Create Feature Request ```bash # Basic creation max:feature-request create "Add dark mode" "Implement dark theme for UI" --priority high # With tags max:fr create "API endpoints" "Add REST API for user management" --tags api,backend --priority medium # From file m:fr create "Complex feature" --file feature_description.md --priority critical ``` #### List and Filter ```bash # List all requests max:feature-request list # Filter by status max:fr list --status open # Filter by priority feature-request list --priority high # Combined filters m:fr list --status open --priority high ``` #### View Details ```bash # Show specific request max:feature-request show FR-20250220-001 # Short form m:fr show FR-20250220-001 ``` #### Update Requests ```bash # Update status max:fr update FR-20250220-001 --status in_progress # Update priority feature-request update FR-20250220-001 --priority critical # Both status and priority m:fr update FR-20250220-001 --status completed --priority low ``` #### Delete Requests ```bash # Delete a request max:feature-request delete FR-20250220-001 ``` ## Annotation Features ### Automatic Code Block Annotation The system automatically detects and annotates code blocks in feature request descriptions: #### Python Code Annotation ```python def process_data(data): # 📝 Function: process_data - defines reusable logic for item in data: # 📝 Loop - iterates over sequence if item.is_valid(): # 📝 Conditional logic - controls program flow yield transform(item) ``` #### Shell Command Annotation ```bash cd /Users/ethandellaposta/Documents/git/MAx # 📋 Navigate to directory: /Users/ethandellaposta/Documents/git/MAx git log --oneline --since="2 weeks ago" # 📋 Git operation: log && git show --name-only HEAD # 📋 Chain command - execute if previous succeeds ``` #### Mixed Content Annotation The system handles mixed content with multiple annotation types: ``` Based on my analysis, I can see that the workflow needs updates. Command cd, git cd /Users/ethandellaposta/Documents/git/MAx && git log --oneline # 📋 Navigate to directory: /Users/ethandellaposta/Documents/git/MAx # 📋 Chain command - execute if previous succeeds # 📋 Git operation: log ```python # 📝 Import: specific module import - targeted functionality from feature_request import FeatureRequestSystem def main(): # 📝 Function: main - defines reusable logic system = FeatureRequestSystem() # 📝 Import: FeatureRequestSystem - brings in external functionality ``` ## Command Reference ### Actions | Action | Description | Example | |--------|-------------|---------| | `create` | Create new feature request | `max:fr create "Title" "Description"` | | `list` | List feature requests | `max:fr list --status open` | | `show` | Show specific request | `max:fr show FR-20250220-001` | | `update` | Update request status/priority | `max:fr update FR-001 --status in_progress` | | `delete` | Delete a request | `max:fr delete FR-20250220-001` | ### Options | Option | Description | Values | |--------|-------------|--------| | `--title` | Request title | String | | `--description` | Request description | String | | `--priority` | Priority level | low, medium, high, critical | | `--status` | Status filter | open, in_progress, completed, rejected | | `--tags` | Categorization tags | List of strings | | `--file` | Read description from file | File path | ### Alias Hierarchy ``` max:feature-request (Full form - most explicit) ↓ max:fr (Short form - balanced) ↓ m:fr (Minimal form - quickest) ↓ feature-request (Legacy form - compatible) ↓ fr (Shortest form - minimal) ``` ## Annotation Patterns ### Code Block Detection The system detects: 1. **Markdown code blocks** with language specification 2. **Shell command blocks** with command prefixes 3. **Mixed content** with multiple annotation types ### Annotation Types | Type | Trigger | Example | |------|---------|---------| | Function definition | `def ` or `class ` | `# 📝 Function: name - defines reusable logic` | | Import statements | `import ` or `from ` | `# 📝 Import: module - brings in external functionality` | | Control structures | `if `, `for `, `while ` | `# 📝 Conditional logic - controls program flow` | | Shell commands | `cd `, `git `, `ls ` | `# 📋 Navigate to directory: path` | | Command chaining | `&&`, `||`, `|` | `# 📋 Chain command - execute if previous succeeds` | ### Annotation Logic The annotation system: 1. **Detects blocks** using regex patterns 2. **Analyzes content** for specific patterns 3. **Adds contextual annotations** after relevant lines 4. **Preserves original code** while adding insights 5. **Handles multiple languages** (Python, Bash, JavaScript, etc.) ## Integration ### With Git Hooks Add to pre-commit hooks for feature request validation: ```yaml # .pre-commit-config.yaml repos: - repo: local hooks: - id: feature-request-check name: Feature Request Validation entry: python3 .max/feature_request.py list language: system ``` ### With IDE The command aliases work directly in IDE command palette: - `max:feature-request` - Full feature request operations - `max:fr` - Quick feature request actions - `m:fr` - Rapid feature request management ### With CI/CD Integrate with GitHub Actions: ```yaml # .github/workflows/feature-requests.yml name: Feature Request Check on: [pull_request] jobs: check-requests: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: List open feature requests run: python3 .max/feature_request.py list --status open ``` ## Data Storage Feature requests are stored in `.max/feature_requests.json` with the following structure: ```json [ { "id": "FR-20250220-001", "title": "Feature title", "description": "Detailed description with code blocks", "priority": "high", "status": "open", "created_at": "2025-02-20T12:00:00", "updated_at": "2025-02-20T12:00:00", "annotations": ["Found code_block at lines 5-10"], "code_blocks": [ { "type": "code_block", "language": "python", "original": "def example():\n pass", "annotated": "def example():\n # 📝 Function: example - defines reusable logic\n pass", "line_start": 5, "line_end": 6 } ], "tags": ["enhancement", "ui"] } ] ``` ## Best Practices ### 1. Use Granular Aliases - **Full form** for documentation and scripts: `max:feature-request` - **Short form** for daily use: `max:fr` - **Minimal form** for quick operations: `m:fr` ### 2. Write Annotatable Descriptions Include code blocks and commands in descriptions: ```markdown Need to implement the following: ```python def new_feature(): # Implementation here pass ``` Shell commands for testing: ```bash cd project && python test_new_feature.py ``` ### 3. Use Tags Effectively Categorize requests for better organization: ```bash max:fr create "API feature" "Description" --tags api,backend,high-priority ``` ### 4. Regular Status Updates Keep requests current: ```bash m:fr update FR-001 --status in_progress # Work on feature... m:fr update FR-001 --status completed ``` ## Examples ### Complete Workflow ```bash # Create feature request with detailed description max:feature-request create "Add user authentication" """ Implement OAuth2 authentication with the following: ```python # 📝 Import: specific module import - targeted functionality from authlib.integrations.flask_client import OAuth def setup_oauth(app): # 📝 Function: setup_oauth - defines reusable logic oauth = OAuth(app) # Configure OAuth providers... ``` Shell commands for setup: ```bash # 📋 Navigate to directory: /project cd /project # 📋 Git operation: checkout git checkout -b feature/auth # 📋 Chain command - execute if previous succeeds && pip install authlib ``` """ --priority high --tags security,authentication # List high priority open requests max:fr list --status open --priority high # Update status when starting work m:fr update FR-20250220-001 --status in_progress # Mark as completed when done feature-request update FR-20250220-001 --status completed ``` ### Quick Operations ```bash # Quick status check m:fr list # Fast feature creation fr create "Quick fix" "Minor bug fix" --priority low # Rapid status update m:fr update FR-001 --status completed ``` --- **🚀 The Feature Request system provides comprehensive tracking with intelligent annotation and granular command control!**

{ "prompt": "# Feature Request Workflow\n\nThe Feature Request system provides comprehensive tracking and annotation capabilities for feature requests with granular command aliases and automatic code/shell script annotation.\n\n## Usage\n\n### Granular Command Aliases\n\nThe system supports multiple levels of command granularity:\n\n```bash\n# Full form\nmax:feature-request create \"Add new feature\" \"Description here\" --priority high\n\n# Short form\nmax:fr list --status open\n\n# Minimal form\nm:fr show FR-20250220-001\n\n# Legacy forms\nfeature-request update FR-20250220-001 --status in_progress\nfr create \"Quick feature\" \"Simple description\"\n```\n\n### Basic Operations\n\n#### Create Feature Request\n```bash\n# Basic creation\nmax:feature-request create \"Add dark mode\" \"Implement dark theme for UI\" --priority high\n\n# With tags\nmax:fr create \"API endpoints\" \"Add REST API for user management\" --tags api,backend --priority medium\n\n# From file\nm:fr create \"Complex feature\" --file feature_description.md --priority critical\n```\n\n#### List and Filter\n```bash\n# List all requests\nmax:feature-request list\n\n# Filter by status\nmax:fr list --status open\n\n# Filter by priority\nfeature-request list --priority high\n\n# Combined filters\nm:fr list --status open --priority high\n```\n\n#### View Details\n```bash\n# Show specific request\nmax:feature-request show FR-20250220-001\n\n# Short form\nm:fr show FR-20250220-001\n```\n\n#### Update Requests\n```bash\n# Update status\nmax:fr update FR-20250220-001 --status in_progress\n\n# Update priority\nfeature-request update FR-20250220-001 --priority critical\n\n# Both status and priority\nm:fr update FR-20250220-001 --status completed --priority low\n```\n\n#### Delete Requests\n```bash\n# Delete a request\nmax:feature-request delete FR-20250220-001\n```\n\n## Annotation Features\n\n### Automatic Code Block Annotation\n\nThe system automatically detects and annotates code blocks in feature request descriptions:\n\n#### Python Code Annotation\n```python\ndef process_data(data):\n # 📝 Function: process_data - defines reusable logic\n for item in data:\n # 📝 Loop - iterates over sequence\n if item.is_valid():\n # 📝 Conditional logic - controls program flow\n yield transform(item)\n```\n\n#### Shell Command Annotation\n```bash\ncd /Users/ethandellaposta/Documents/git/MAx\n# 📋 Navigate to directory: /Users/ethandellaposta/Documents/git/MAx\ngit log --oneline --since=\"2 weeks ago\"\n# 📋 Git operation: log\n&& git show --name-only HEAD\n# 📋 Chain command - execute if previous succeeds\n```\n\n#### Mixed Content Annotation\nThe system handles mixed content with multiple annotation types:\n\n```\nBased on my analysis, I can see that the workflow needs updates.\n\nCommand cd, git\ncd /Users/ethandellaposta/Documents/git/MAx && git log --oneline\n# 📋 Navigate to directory: /Users/ethandellaposta/Documents/git/MAx\n# 📋 Chain command - execute if previous succeeds\n# 📋 Git operation: log\n\n```python\n# 📝 Import: specific module import - targeted functionality\nfrom feature_request import FeatureRequestSystem\n\ndef main():\n # 📝 Function: main - defines reusable logic\n system = FeatureRequestSystem()\n # 📝 Import: FeatureRequestSystem - brings in external functionality\n```\n\n## Command Reference\n\n### Actions\n\n| Action | Description | Example |\n|--------|-------------|---------|\n| `create` | Create new feature request | `max:fr create \"Title\" \"Description\"` |\n| `list` | List feature requests | `max:fr list --status open` |\n| `show` | Show specific request | `max:fr show FR-20250220-001` |\n| `update` | Update request status/priority | `max:fr update FR-001 --status in_progress` |\n| `delete` | Delete a request | `max:fr delete FR-20250220-001` |\n\n### Options\n\n| Option | Description | Values |\n|--------|-------------|--------|\n| `--title` | Request title | String |\n| `--description` | Request description | String |\n| `--priority` | Priority level | low, medium, high, critical |\n| `--status` | Status filter | open, in_progress, completed, rejected |\n| `--tags` | Categorization tags | List of strings |\n| `--file` | Read description from file | File path |\n\n### Alias Hierarchy\n\n```\nmax:feature-request (Full form - most explicit)\n ↓\nmax:fr (Short form - balanced)\n ↓\nm:fr (Minimal form - quickest)\n ↓\nfeature-request (Legacy form - compatible)\n ↓\nfr (Shortest form - minimal)\n```\n\n## Annotation Patterns\n\n### Code Block Detection\n\nThe system detects:\n\n1. **Markdown code blocks** with language specification\n2. **Shell command blocks** with command prefixes\n3. **Mixed content** with multiple annotation types\n\n### Annotation Types\n\n| Type | Trigger | Example |\n|------|---------|---------|\n| Function definition | `def ` or `class ` | `# 📝 Function: name - defines reusable logic` |\n| Import statements | `import ` or `from ` | `# 📝 Import: module - brings in external functionality` |\n| Control structures | `if `, `for `, `while ` | `# 📝 Conditional logic - controls program flow` |\n| Shell commands | `cd `, `git `, `ls ` | `# 📋 Navigate to directory: path` |\n| Command chaining | `&&`, `||`, `|` | `# 📋 Chain command - execute if previous succeeds` |\n\n### Annotation Logic\n\nThe annotation system:\n\n1. **Detects blocks** using regex patterns\n2. **Analyzes content** for specific patterns\n3. **Adds contextual annotations** after relevant lines\n4. **Preserves original code** while adding insights\n5. **Handles multiple languages** (Python, Bash, JavaScript, etc.)\n\n## Integration\n\n### With Git Hooks\n\nAdd to pre-commit hooks for feature request validation:\n\n```yaml\n# .pre-commit-config.yaml\nrepos:\n - repo: local\n hooks:\n - id: feature-request-check\n name: Feature Request Validation\n entry: python3 .max/feature_request.py list\n language: system\n```\n\n### With IDE\n\nThe command aliases work directly in IDE command palette:\n\n- `max:feature-request` - Full feature request operations\n- `max:fr` - Quick feature request actions\n- `m:fr` - Rapid feature request management\n\n### With CI/CD\n\nIntegrate with GitHub Actions:\n\n```yaml\n# .github/workflows/feature-requests.yml\nname: Feature Request Check\non: [pull_request]\njobs:\n check-requests:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v2\n - name: List open feature requests\n run: python3 .max/feature_request.py list --status open\n```\n\n## Data Storage\n\nFeature requests are stored in `.max/feature_requests.json` with the following structure:\n\n```json\n[\n {\n \"id\": \"FR-20250220-001\",\n \"title\": \"Feature title\",\n \"description\": \"Detailed description with code blocks\",\n \"priority\": \"high\",\n \"status\": \"open\",\n \"created_at\": \"2025-02-20T12:00:00\",\n \"updated_at\": \"2025-02-20T12:00:00\",\n \"annotations\": [\"Found code_block at lines 5-10\"],\n \"code_blocks\": [\n {\n \"type\": \"code_block\",\n \"language\": \"python\",\n \"original\": \"def example():\\n pass\",\n \"annotated\": \"def example():\\n # 📝 Function: example - defines reusable logic\\n pass\",\n \"line_start\": 5,\n \"line_end\": 6\n }\n ],\n \"tags\": [\"enhancement\", \"ui\"]\n }\n]\n```\n\n## Best Practices\n\n### 1. Use Granular Aliases\n\n- **Full form** for documentation and scripts: `max:feature-request`\n- **Short form** for daily use: `max:fr`\n- **Minimal form** for quick operations: `m:fr`\n\n### 2. Write Annotatable Descriptions\n\nInclude code blocks and commands in descriptions:\n\n```markdown\nNeed to implement the following:\n\n```python\ndef new_feature():\n # Implementation here\n pass\n```\n\nShell commands for testing:\n```bash\ncd project && python test_new_feature.py\n```\n\n### 3. Use Tags Effectively\n\nCategorize requests for better organization:\n\n```bash\nmax:fr create \"API feature\" \"Description\" --tags api,backend,high-priority\n```\n\n### 4. Regular Status Updates\n\nKeep requests current:\n\n```bash\nm:fr update FR-001 --status in_progress\n# Work on feature...\nm:fr update FR-001 --status completed\n```\n\n## Examples\n\n### Complete Workflow\n\n```bash\n# Create feature request with detailed description\nmax:feature-request create \"Add user authentication\" \"\"\"\nImplement OAuth2 authentication with the following:\n\n```python\n# 📝 Import: specific module import - targeted functionality\nfrom authlib.integrations.flask_client import OAuth\n\ndef setup_oauth(app):\n # 📝 Function: setup_oauth - defines reusable logic\n oauth = OAuth(app)\n # Configure OAuth providers...\n```\n\nShell commands for setup:\n```bash\n# 📋 Navigate to directory: /project\ncd /project\n# 📋 Git operation: checkout\ngit checkout -b feature/auth\n# 📋 Chain command - execute if previous succeeds\n&& pip install authlib\n```\n\"\"\" --priority high --tags security,authentication\n\n# List high priority open requests\nmax:fr list --status open --priority high\n\n# Update status when starting work\nm:fr update FR-20250220-001 --status in_progress\n\n# Mark as completed when done\nfeature-request update FR-20250220-001 --status completed\n```\n\n### Quick Operations\n\n```bash\n# Quick status check\nm:fr list\n\n# Fast feature creation\nfr create \"Quick fix\" \"Minor bug fix\" --priority low\n\n# Rapid status update\nm:fr update FR-001 --status completed\n```\n\n---\n\n**🚀 The Feature Request system provides comprehensive tracking with intelligent annotation and granular command control!**", "variables": [], "notes": "Feature Request System - Track and annotate feature requests with granular command aliases", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/danilonovaisv/SCENES-GENERATOR", "path": ".windsurf/workflows/core/feature/feature-request.md", "ref": "568dcd7257722992a39408538087f87c69c7f2e2", "url": "https://github.com/danilonovaisv/SCENES-GENERATOR/blob/568dcd7257722992a39408538087f87c69c7f2e2/.windsurf/workflows/core/feature/feature-request.md", "key": "danilonovaisv/SCENES-GENERATOR/.windsurf/workflows/core/feature/feature-request.md" } } }