Name: delegate-to-cursor
Author: jackmaxwil

Prompt file imported from jackmaxwil/alfred (.cursor/commands/delegate-to-cursor.md). Copyright stays with the author.

Delegate Linear Tickets to Cursor Agents

Overview

Bulk assign Linear tickets to Cursor agents for automated execution. This command handles delegation, begin prompt creation, and validation of blocking relationships.

Prerequisites

Linear MCP tools configured
Cursor delegate ID: 5497cebb-b66c-4675-bd54-fc650cf94d27
Tickets must have clear descriptions and acceptance criteria

Workflow

Phase 1: Identify Tickets

Determine which tickets to delegate:

Option A: Specific Issue IDs

Tickets: ALF-308, ALF-309, ALF-310, ALF-311, ALF-312

Option B: Query by Label/Project

Use Linear MCP: list_issues
Arguments: {
  "team": "Alfred-ops",
  "label": "infrastructure",
  "state": "Backlog",
  "limit": 50
}

Option C: Query by Epic

// Get all issues blocked by an epic
Use Linear MCP: get_issue with includeRelations
Then filter for issues in the `blocks` array

Phase 2: Validate Tickets

Before delegating, verify each ticket has:

✅ Clear description with context
✅ Specific file paths or implementation guidance
✅ Acceptance criteria defined
✅ Proper labels (ui, api, database, infrastructure, etc.)
✅ Appropriate priority (1=Urgent, 2=High, 3=Medium, 4=Low)

Warn if tickets are missing critical information.

Phase 3: Assign Cursor Delegate

For each validated ticket:

Use Linear MCP: update_issue
Arguments: {
  "id": "<issue-id>",
  "delegate": "Cursor"
}

Phase 4: Add Begin Prompts (Optional)

Create detailed begin prompts as comments:

Use Linear MCP: create_comment
Arguments: {
  "issueId": "<issue-id>",
  "body": "@cursor\n\n## Begin Prompt\n\n<detailed-context-and-tasks>"
}

Begin Prompt Template:

@cursor

## Begin Prompt

<Brief description of the task>

**Context:**

- Current state: <what exists now>
- Target state: <what should exist>
- Reference files: <paths-to-similar-implementations>

**Tasks:**

1. <Specific task with code example if relevant>
2. <Next task>
3. <Final task>

**Pattern:**

```typescript
// Before
<current-code-snippet>

// After
<target-code-snippet>
```

Acceptance:

<Criterion 1>
<Criterion 2>
<Criterion 3>

Commands:

cd <relevant-directory>
bun test <test-path>


### Phase 5: Report Summary
Output:
- ✅ Total tickets delegated
- ✅ Tickets with begin prompts added
- ✅ Any validation warnings
- ✅ Recommended execution order (based on blocking relationships)

## Input Patterns

### Pattern 1: List of IDs

Delegate these tickets to Cursor: ALF-308, ALF-309, ALF-310


### Pattern 2: Epic Children

Delegate all sub-tasks of ALF-307 to Cursor


### Pattern 3: Filter Criteria

Delegate all "infrastructure" tickets in "Backlog" state to Cursor


### Pattern 4: Priority Range

Delegate all Urgent and High priority tickets to Cursor


## Begin Prompt Generation

When creating begin prompts, include:

1. **Context Section:**
   - What currently exists
   - What's missing or broken
   - Reference implementations

2. **Tasks Section:**
   - Numbered list of specific actions
   - Code examples where helpful
   - File paths to create/modify

3. **Pattern/Example Section:**
   - Before/after code snippets
   - Common anti-patterns to avoid
   - Testing patterns

4. **Acceptance Section:**
   - Measurable criteria
   - Coverage requirements
   - Performance budgets (if applicable)

5. **Commands Section:**
   - How to run tests
   - How to validate changes
   - How to check coverage

## Best Practices

1. **Validate before delegating** - Ensure tickets have enough context for autonomous execution
2. **Check dependencies** - Don't delegate blocked tickets without delegating blockers first
3. **Prioritize clearly** - Use Linear priority field (1=Urgent, 2=High, 3=Medium, 4=Low)
4. **Add begin prompts for complex tasks** - Simple tasks may not need detailed prompts
5. **Link related tickets** - Use `relatedTo` to connect similar work
6. **Set estimates** - Use story points (1, 2, 3, 5, 8) for capacity planning

## Example Output

```markdown
## Delegation Summary

✅ Delegated 5 tickets to Cursor:
- ALF-308: Create privacy router test suite (Priority: Urgent)
- ALF-309: Create deploy router test suite (Priority: Urgent)
- ALF-310: Create fs/terminal router security tests (Priority: Urgent)
- ALF-311: Create sanitization repository tests (Priority: Urgent)
- ALF-312: Build reusable testing infrastructure (Priority: High)

✅ Added begin prompts to all 5 tickets

⚠️  Dependency Chain:
1. Start with ALF-312 (unblocks others)
2. Then parallel: ALF-308, 309, 310, 311

## Next Steps
Cursor agents can now pick up these tickets. Monitor progress in Linear.

Common Issues

Issue: Ticket missing context

Solution: Add more detail to description before delegating, or add comprehensive begin prompt

Issue: Blocking relationships unclear

Solution: Use Linear blocks field to enforce execution order

Issue: Begin prompt too generic

Solution: Include specific file paths, code examples, and validation commands

Related Commands

/investigate-ticket - Deep dive into a single ticket before delegation
/update-linear - Update ticket status after completion
/implement-feature - Full implementation workflow (complements delegation)

Example Usage

Example 1: Delegate Epic Children

/delegate-to-cursor all sub-tasks of ALF-307

Example 2: Delegate Specific Tickets

/delegate-to-cursor ALF-308, ALF-309, ALF-310 with begin prompts

Example 3: Delegate by Filter

/delegate-to-cursor all "infrastructure" tickets in "Backlog"

Example 4: Validate Only (Dry Run)

/delegate-to-cursor --dry-run ALF-308, ALF-309, ALF-310

Install delegate-to-cursor 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.

# Delegate Linear Tickets to Cursor Agents ## Overview Bulk assign Linear tickets to Cursor agents for automated execution. This command handles delegation, begin prompt creation, and validation of blocking relationships. ## Prerequisites - Linear MCP tools configured - Cursor delegate ID: `5497cebb-b66c-4675-bd54-fc650cf94d27` - Tickets must have clear descriptions and acceptance criteria ## Workflow ### Phase 1: Identify Tickets Determine which tickets to delegate: **Option A: Specific Issue IDs** ``` Tickets: ALF-308, ALF-309, ALF-310, ALF-311, ALF-312 ``` **Option B: Query by Label/Project** ```typescript Use Linear MCP: list_issues Arguments: { "team": "Alfred-ops", "label": "infrastructure", "state": "Backlog", "limit": 50 } ``` **Option C: Query by Epic** ```typescript // Get all issues blocked by an epic Use Linear MCP: get_issue with includeRelations Then filter for issues in the `blocks` array ``` ### Phase 2: Validate Tickets Before delegating, verify each ticket has: - ✅ Clear description with context - ✅ Specific file paths or implementation guidance - ✅ Acceptance criteria defined - ✅ Proper labels (ui, api, database, infrastructure, etc.) - ✅ Appropriate priority (1=Urgent, 2=High, 3=Medium, 4=Low) Warn if tickets are missing critical information. ### Phase 3: Assign Cursor Delegate For each validated ticket: ```typescript Use Linear MCP: update_issue Arguments: { "id": "<issue-id>", "delegate": "Cursor" } ``` ### Phase 4: Add Begin Prompts (Optional) Create detailed begin prompts as comments: ```typescript Use Linear MCP: create_comment Arguments: { "issueId": "<issue-id>", "body": "@cursor\n\n## Begin Prompt\n\n<detailed-context-and-tasks>" } ``` **Begin Prompt Template:** ````markdown @cursor ## Begin Prompt <Brief description of the task> **Context:** - Current state: <what exists now> - Target state: <what should exist> - Reference files: <paths-to-similar-implementations> **Tasks:** 1. <Specific task with code example if relevant> 2. <Next task> 3. <Final task> **Pattern:** ```typescript // Before <current-code-snippet> // After <target-code-snippet> ``` ```` **Acceptance:** - <Criterion 1> - <Criterion 2> - <Criterion 3> **Commands:** ```bash cd <relevant-directory> bun test <test-path> ``` ``` ### Phase 5: Report Summary Output: - ✅ Total tickets delegated - ✅ Tickets with begin prompts added - ✅ Any validation warnings - ✅ Recommended execution order (based on blocking relationships) ## Input Patterns ### Pattern 1: List of IDs ``` Delegate these tickets to Cursor: ALF-308, ALF-309, ALF-310 ``` ### Pattern 2: Epic Children ``` Delegate all sub-tasks of ALF-307 to Cursor ``` ### Pattern 3: Filter Criteria ``` Delegate all "infrastructure" tickets in "Backlog" state to Cursor ``` ### Pattern 4: Priority Range ``` Delegate all Urgent and High priority tickets to Cursor ```` ## Begin Prompt Generation When creating begin prompts, include: 1. **Context Section:** - What currently exists - What's missing or broken - Reference implementations 2. **Tasks Section:** - Numbered list of specific actions - Code examples where helpful - File paths to create/modify 3. **Pattern/Example Section:** - Before/after code snippets - Common anti-patterns to avoid - Testing patterns 4. **Acceptance Section:** - Measurable criteria - Coverage requirements - Performance budgets (if applicable) 5. **Commands Section:** - How to run tests - How to validate changes - How to check coverage ## Best Practices 1. **Validate before delegating** - Ensure tickets have enough context for autonomous execution 2. **Check dependencies** - Don't delegate blocked tickets without delegating blockers first 3. **Prioritize clearly** - Use Linear priority field (1=Urgent, 2=High, 3=Medium, 4=Low) 4. **Add begin prompts for complex tasks** - Simple tasks may not need detailed prompts 5. **Link related tickets** - Use `relatedTo` to connect similar work 6. **Set estimates** - Use story points (1, 2, 3, 5, 8) for capacity planning ## Example Output ```markdown ## Delegation Summary ✅ Delegated 5 tickets to Cursor: - ALF-308: Create privacy router test suite (Priority: Urgent) - ALF-309: Create deploy router test suite (Priority: Urgent) - ALF-310: Create fs/terminal router security tests (Priority: Urgent) - ALF-311: Create sanitization repository tests (Priority: Urgent) - ALF-312: Build reusable testing infrastructure (Priority: High) ✅ Added begin prompts to all 5 tickets ⚠️ Dependency Chain: 1. Start with ALF-312 (unblocks others) 2. Then parallel: ALF-308, 309, 310, 311 ## Next Steps Cursor agents can now pick up these tickets. Monitor progress in Linear. ```` ## Common Issues ### Issue: Ticket missing context **Solution:** Add more detail to description before delegating, or add comprehensive begin prompt ### Issue: Blocking relationships unclear **Solution:** Use Linear `blocks` field to enforce execution order ### Issue: Begin prompt too generic **Solution:** Include specific file paths, code examples, and validation commands ## Related Commands - `/investigate-ticket` - Deep dive into a single ticket before delegation - `/update-linear` - Update ticket status after completion - `/implement-feature` - Full implementation workflow (complements delegation) ## Example Usage ### Example 1: Delegate Epic Children ``` /delegate-to-cursor all sub-tasks of ALF-307 ``` ### Example 2: Delegate Specific Tickets ``` /delegate-to-cursor ALF-308, ALF-309, ALF-310 with begin prompts ``` ### Example 3: Delegate by Filter ``` /delegate-to-cursor all "infrastructure" tickets in "Backlog" ``` ### Example 4: Validate Only (Dry Run) ``` /delegate-to-cursor --dry-run ALF-308, ALF-309, ALF-310 ```

{ "prompt": "# Delegate Linear Tickets to Cursor Agents\n\n## Overview\n\nBulk assign Linear tickets to Cursor agents for automated execution. This command handles delegation, begin prompt creation, and validation of blocking relationships.\n\n## Prerequisites\n\n- Linear MCP tools configured\n- Cursor delegate ID: `5497cebb-b66c-4675-bd54-fc650cf94d27`\n- Tickets must have clear descriptions and acceptance criteria\n\n## Workflow\n\n### Phase 1: Identify Tickets\n\nDetermine which tickets to delegate:\n\n**Option A: Specific Issue IDs**\n\n```\nTickets: ALF-308, ALF-309, ALF-310, ALF-311, ALF-312\n```\n\n**Option B: Query by Label/Project**\n\n```typescript\nUse Linear MCP: list_issues\nArguments: {\n \"team\": \"Alfred-ops\",\n \"label\": \"infrastructure\",\n \"state\": \"Backlog\",\n \"limit\": 50\n}\n```\n\n**Option C: Query by Epic**\n\n```typescript\n// Get all issues blocked by an epic\nUse Linear MCP: get_issue with includeRelations\nThen filter for issues in the `blocks` array\n```\n\n### Phase 2: Validate Tickets\n\nBefore delegating, verify each ticket has:\n\n- ✅ Clear description with context\n- ✅ Specific file paths or implementation guidance\n- ✅ Acceptance criteria defined\n- ✅ Proper labels (ui, api, database, infrastructure, etc.)\n- ✅ Appropriate priority (1=Urgent, 2=High, 3=Medium, 4=Low)\n\nWarn if tickets are missing critical information.\n\n### Phase 3: Assign Cursor Delegate\n\nFor each validated ticket:\n\n```typescript\nUse Linear MCP: update_issue\nArguments: {\n \"id\": \"<issue-id>\",\n \"delegate\": \"Cursor\"\n}\n```\n\n### Phase 4: Add Begin Prompts (Optional)\n\nCreate detailed begin prompts as comments:\n\n```typescript\nUse Linear MCP: create_comment\nArguments: {\n \"issueId\": \"<issue-id>\",\n \"body\": \"@cursor\\n\\n## Begin Prompt\\n\\n<detailed-context-and-tasks>\"\n}\n```\n\n**Begin Prompt Template:**\n\n````markdown\n@cursor\n\n## Begin Prompt\n\n<Brief description of the task>\n\n**Context:**\n\n- Current state: <what exists now>\n- Target state: <what should exist>\n- Reference files: <paths-to-similar-implementations>\n\n**Tasks:**\n\n1. <Specific task with code example if relevant>\n2. <Next task>\n3. <Final task>\n\n**Pattern:**\n\n```typescript\n// Before\n<current-code-snippet>\n\n// After\n<target-code-snippet>\n```\n````\n\n**Acceptance:**\n\n- <Criterion 1>\n- <Criterion 2>\n- <Criterion 3>\n\n**Commands:**\n\n```bash\ncd <relevant-directory>\nbun test <test-path>\n```\n\n```\n\n### Phase 5: Report Summary\nOutput:\n- ✅ Total tickets delegated\n- ✅ Tickets with begin prompts added\n- ✅ Any validation warnings\n- ✅ Recommended execution order (based on blocking relationships)\n\n## Input Patterns\n\n### Pattern 1: List of IDs\n```\n\nDelegate these tickets to Cursor: ALF-308, ALF-309, ALF-310\n\n```\n\n### Pattern 2: Epic Children\n```\n\nDelegate all sub-tasks of ALF-307 to Cursor\n\n```\n\n### Pattern 3: Filter Criteria\n```\n\nDelegate all \"infrastructure\" tickets in \"Backlog\" state to Cursor\n\n```\n\n### Pattern 4: Priority Range\n```\n\nDelegate all Urgent and High priority tickets to Cursor\n\n````\n\n## Begin Prompt Generation\n\nWhen creating begin prompts, include:\n\n1. **Context Section:**\n - What currently exists\n - What's missing or broken\n - Reference implementations\n\n2. **Tasks Section:**\n - Numbered list of specific actions\n - Code examples where helpful\n - File paths to create/modify\n\n3. **Pattern/Example Section:**\n - Before/after code snippets\n - Common anti-patterns to avoid\n - Testing patterns\n\n4. **Acceptance Section:**\n - Measurable criteria\n - Coverage requirements\n - Performance budgets (if applicable)\n\n5. **Commands Section:**\n - How to run tests\n - How to validate changes\n - How to check coverage\n\n## Best Practices\n\n1. **Validate before delegating** - Ensure tickets have enough context for autonomous execution\n2. **Check dependencies** - Don't delegate blocked tickets without delegating blockers first\n3. **Prioritize clearly** - Use Linear priority field (1=Urgent, 2=High, 3=Medium, 4=Low)\n4. **Add begin prompts for complex tasks** - Simple tasks may not need detailed prompts\n5. **Link related tickets** - Use `relatedTo` to connect similar work\n6. **Set estimates** - Use story points (1, 2, 3, 5, 8) for capacity planning\n\n## Example Output\n\n```markdown\n## Delegation Summary\n\n✅ Delegated 5 tickets to Cursor:\n- ALF-308: Create privacy router test suite (Priority: Urgent)\n- ALF-309: Create deploy router test suite (Priority: Urgent)\n- ALF-310: Create fs/terminal router security tests (Priority: Urgent)\n- ALF-311: Create sanitization repository tests (Priority: Urgent)\n- ALF-312: Build reusable testing infrastructure (Priority: High)\n\n✅ Added begin prompts to all 5 tickets\n\n⚠️ Dependency Chain:\n1. Start with ALF-312 (unblocks others)\n2. Then parallel: ALF-308, 309, 310, 311\n\n## Next Steps\nCursor agents can now pick up these tickets. Monitor progress in Linear.\n````\n\n## Common Issues\n\n### Issue: Ticket missing context\n\n**Solution:** Add more detail to description before delegating, or add comprehensive begin prompt\n\n### Issue: Blocking relationships unclear\n\n**Solution:** Use Linear `blocks` field to enforce execution order\n\n### Issue: Begin prompt too generic\n\n**Solution:** Include specific file paths, code examples, and validation commands\n\n## Related Commands\n\n- `/investigate-ticket` - Deep dive into a single ticket before delegation\n- `/update-linear` - Update ticket status after completion\n- `/implement-feature` - Full implementation workflow (complements delegation)\n\n## Example Usage\n\n### Example 1: Delegate Epic Children\n\n```\n/delegate-to-cursor all sub-tasks of ALF-307\n```\n\n### Example 2: Delegate Specific Tickets\n\n```\n/delegate-to-cursor ALF-308, ALF-309, ALF-310 with begin prompts\n```\n\n### Example 3: Delegate by Filter\n\n```\n/delegate-to-cursor all \"infrastructure\" tickets in \"Backlog\"\n```\n\n### Example 4: Validate Only (Dry Run)\n\n```\n/delegate-to-cursor --dry-run ALF-308, ALF-309, ALF-310\n```", "variables": [], "notes": "Bulk assign Linear tickets to Cursor agents for automated execution. This command handles delegation, begin prompt creation, and validation of blocking relationships.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/jackmaxwil/alfred", "path": ".cursor/commands/delegate-to-cursor.md", "ref": "226a597e8c9c64ce54d079da0f9b834eca369d6c", "url": "https://github.com/jackmaxwil/alfred/blob/226a597e8c9c64ce54d079da0f9b834eca369d6c/.cursor/commands/delegate-to-cursor.md", "key": "jackmaxwil/alfred/.cursor/commands/delegate-to-cursor.md" } } }

delegate-to-cursor

About