Name: assign-tasks
Author: ninjasitm

Prompt file imported from ninjasitm/ai-assisted-landing-demo (.github/prompts/assign-tasks.prompt.md). Fill in {{ISSUE_TRACKER}}, {{QUARTER}}, {{PROJECT_KEY}}, {{DEFAULT_ASSIGNEE}} before use. Copyright stays with the author.

Create Tickets from Requirements

Parse requirement documents or task breakdown files and create structured tickets in {{ISSUE_TRACKER}}.

Usage

/assign-tasks docs/features/requirements.md
/assign-tasks docs/tasks/feature-breakdown.md

Task Consolidation Rules (CRITICAL)

Before creating tickets, consolidate tasks to reduce noise and improve focus.

Maximum Ticket Counts

Feature Size	Max Stories	Max Tasks/Story	Max Subtasks/Task
Small (< 8 SP)	1-2	2-3	0
Medium (8-21 SP)	2-4	3-4	2-4
Large (21-55 SP)	4-8	4-6	4-8
XL (55+ SP)	6-12	5-8	8-15

Consolidation Checklist

Before creating each ticket, ask:

Can these 2+ items be combined? Group related work together
Is this subtask necessary? Or is it just an obvious step?
Would a developer do these together? If yes, combine them
Does this represent meaningful progress? If not, merge it

Grouping Guidelines

Merge related work: Same component or feature area = 1 ticket
Bundle by deliverable: Group by what ships together
Collapse small items: < 2 SP should be subtasks or merged
Limit hierarchy: Prefer Epic → Story → Task (minimize Subtasks)

Epic Discovery (Parent Task Assignment)

All stories and tasks MUST belong to an Epic. Before creating tickets:

1. Check for Explicit Parent

If the requirement doc specifies an Epic, use it
If linked from an existing Epic, use that Epic

2. Search for Matching Epic

If no parent is specified, use MCP/{{ISSUE_TRACKER}} tools to find a suitable Epic:

# Search for open Epics in the project
- List all Epics with status: Open, In Progress
- Filter by labels/components matching the feature domain
- Check Epic descriptions for related keywords

Matching Criteria (in priority order):

Domain match: Epic covers same feature area (e.g., "Authentication", "Payments")
Component match: Epic targets same system component
Sprint/Release match: Epic is in current or upcoming sprint
Keyword match: Epic title/description contains related terms

3. Fallback to Maintenance Epic

If no appropriate Epic exists:

Search for existing "Maintenance" or "Tech Debt" Epic

If none exists, create one:

Epic: Maintenance & Improvements - {{QUARTER}}
Description: Technical improvements, bug fixes, and maintenance work
Labels: maintenance, tech-debt

4. Report Parent Assignment

In the ticket creation report, always include:

Parent Epic: [EPIC-123] Epic Title
Assignment Reason: Domain match (Authentication) | Maintenance fallback

Process

Parse Document:
- Load the specified document (.md, .txt, .json)
- Detect document structure (headers, lists, task categories)
- Extract task hierarchy: Epic → Story → Task → Subtask
Consolidate First (BEFORE creating tickets):
- Group related items by component, feature area, or deliverable
- Merge small tasks (< 2 SP) into related larger tasks
- Eliminate redundant subtasks that are obvious steps
- Validate counts against maximum limits above
Classify Consolidated Tasks:
- Epic: Large features, 13+ story points
- Story: User-focused deliverable, 3-13 story points (prefer larger)
- Task: Implementation work, 2-8 story points (avoid < 2 SP)
- Subtask: Only for complex tasks, 1-3 story points (use sparingly)
Estimate Effort:
- 0.5-1 hours → Merge with related task (too small alone)
- 2-3 hours → 2 story points
- 4-6 hours → 3-5 story points
- 7-12 hours → 8 story points
- 13+ hours → 13 story points (consider splitting into stories)
Create Tickets:
- Create in proper hierarchy order (Epics first, then Stories, then Tasks)
- Link child issues to parents
- Set assignees, labels, and story points
- Create dependency links where noted
Generate Report:
- List all created tickets with IDs
- Show hierarchy and relationships
- Report total story points
- Consolidation summary: "Merged X raw items into Y tickets"

API Rate Limiting & Throttling

CRITICAL: {{ISSUE_TRACKER}} APIs have rate limits. When creating multiple tickets:

Batch Strategy

Small batches (< 5 tickets): Create all tickets immediately
Medium batches (5-15 tickets): Create in groups of 5 with 2-second delays
Large batches (15+ tickets): Create in groups of 5 with 3-5 second delays

Implementation Pattern

1. Create Epic(s) first → Wait 2 seconds
2. Create Stories (batch of 5) → Wait 2 seconds
3. Create next Stories (batch of 5) → Wait 2 seconds
4. Create Tasks (batch of 5) → Wait 3 seconds
5. Continue batching with delays

Error Handling

429 (Rate Limit): Wait 10 seconds, then retry
503 (Service Unavailable): Wait 5 seconds, then retry
Max retries: 3 attempts per ticket
Failed tickets: Report at end with error details

Progress Reporting

Creating tickets...
✓ Epic created: PROJ-123
  [Waiting 2s to avoid rate limiting...]
✓ Stories created: PROJ-124, PROJ-125, PROJ-126 (batch 1/3)
  [Waiting 2s...]
✓ Stories created: PROJ-127, PROJ-128, PROJ-129 (batch 2/3)

Best Practices

⚠️ Never create more than 5 tickets without a delay
⚠️ Always wait at least 2 seconds between batches
⚠️ Increase delays if rate limit errors occur
✓ Show progress updates between batches
✓ Report any failed tickets with retry instructions

Anti-Patterns to Avoid

❌ Don't create separate tickets for:

"Create file X" and "Configure file X" (combine them)
"Write tests" and "Run tests" (one ticket)
Each individual file change
Steps that take < 1 hour
Each CRUD operation separately

✅ Do combine into single tickets:

All database work for an entity (model + migration + seeder)
Related API endpoints (CRUD for one resource)
All configuration and setup for a feature
Testing for a component (unit + integration)
Documentation updates across files

Document Format Support

Markdown Headers:

# Epic: Feature Name

## Story: User Story (combines related implementation)

### Task: Implementation Task (only if story needs breakdown)

Dependency Keywords:

"depends on", "after", "requires", "blocks"

Configuration

Project Key: {{PROJECT_KEY}}
Default Assignee: {{DEFAULT_ASSIGNEE}}
Labels: Based on content categories

Install assign-tasks 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.

# Create Tickets from Requirements Parse requirement documents or task breakdown files and create structured tickets in {{ISSUE_TRACKER}}. ## Usage ``` /assign-tasks docs/features/requirements.md /assign-tasks docs/tasks/feature-breakdown.md ``` ## Task Consolidation Rules (CRITICAL) Before creating tickets, consolidate tasks to reduce noise and improve focus. ### Maximum Ticket Counts | Feature Size | Max Stories | Max Tasks/Story | Max Subtasks/Task | | ---------------- | ----------- | --------------- | ----------------- | | Small (< 8 SP) | 1-2 | 2-3 | 0 | | Medium (8-21 SP) | 2-4 | 3-4 | 2-4 | | Large (21-55 SP) | 4-8 | 4-6 | 4-8 | | XL (55+ SP) | 6-12 | 5-8 | 8-15 | ### Consolidation Checklist Before creating each ticket, ask: 1. **Can these 2+ items be combined?** Group related work together 2. **Is this subtask necessary?** Or is it just an obvious step? 3. **Would a developer do these together?** If yes, combine them 4. **Does this represent meaningful progress?** If not, merge it ### Grouping Guidelines - **Merge related work**: Same component or feature area = 1 ticket - **Bundle by deliverable**: Group by what ships together - **Collapse small items**: < 2 SP should be subtasks or merged - **Limit hierarchy**: Prefer Epic → Story → Task (minimize Subtasks) ## Epic Discovery (Parent Task Assignment) All stories and tasks MUST belong to an Epic. Before creating tickets: ### 1. Check for Explicit Parent - If the requirement doc specifies an Epic, use it - If linked from an existing Epic, use that Epic ### 2. Search for Matching Epic If no parent is specified, use MCP/{{ISSUE_TRACKER}} tools to find a suitable Epic: ``` # Search for open Epics in the project - List all Epics with status: Open, In Progress - Filter by labels/components matching the feature domain - Check Epic descriptions for related keywords ``` **Matching Criteria** (in priority order): 1. **Domain match**: Epic covers same feature area (e.g., "Authentication", "Payments") 2. **Component match**: Epic targets same system component 3. **Sprint/Release match**: Epic is in current or upcoming sprint 4. **Keyword match**: Epic title/description contains related terms ### 3. Fallback to Maintenance Epic If no appropriate Epic exists: - Search for existing "Maintenance" or "Tech Debt" Epic - If none exists, create one: ``` Epic: Maintenance & Improvements - {{QUARTER}} Description: Technical improvements, bug fixes, and maintenance work Labels: maintenance, tech-debt ``` ### 4. Report Parent Assignment In the ticket creation report, always include: ``` Parent Epic: [EPIC-123] Epic Title Assignment Reason: Domain match (Authentication) | Maintenance fallback ``` ## Process 1. **Parse Document**: - Load the specified document (.md, .txt, .json) - Detect document structure (headers, lists, task categories) - Extract task hierarchy: Epic → Story → Task → Subtask 2. **Consolidate First** (BEFORE creating tickets): - **Group related items** by component, feature area, or deliverable - **Merge small tasks** (< 2 SP) into related larger tasks - **Eliminate redundant subtasks** that are obvious steps - **Validate counts** against maximum limits above 3. **Classify Consolidated Tasks**: - **Epic**: Large features, 13+ story points - **Story**: User-focused deliverable, 3-13 story points (prefer larger) - **Task**: Implementation work, 2-8 story points (avoid < 2 SP) - **Subtask**: Only for complex tasks, 1-3 story points (use sparingly) 4. **Estimate Effort**: - 0.5-1 hours → **Merge with related task** (too small alone) - 2-3 hours → 2 story points - 4-6 hours → 3-5 story points - 7-12 hours → 8 story points - 13+ hours → 13 story points (consider splitting into stories) 5. **Create Tickets**: - Create in proper hierarchy order (Epics first, then Stories, then Tasks) - Link child issues to parents - Set assignees, labels, and story points - Create dependency links where noted 6. **Generate Report**: - List all created tickets with IDs - Show hierarchy and relationships - Report total story points - **Consolidation summary**: "Merged X raw items into Y tickets" ## API Rate Limiting & Throttling **CRITICAL**: {{ISSUE_TRACKER}} APIs have rate limits. When creating multiple tickets: ### Batch Strategy - **Small batches** (< 5 tickets): Create all tickets immediately - **Medium batches** (5-15 tickets): Create in groups of 5 with 2-second delays - **Large batches** (15+ tickets): Create in groups of 5 with 3-5 second delays ### Implementation Pattern ``` 1. Create Epic(s) first → Wait 2 seconds 2. Create Stories (batch of 5) → Wait 2 seconds 3. Create next Stories (batch of 5) → Wait 2 seconds 4. Create Tasks (batch of 5) → Wait 3 seconds 5. Continue batching with delays ``` ### Error Handling - **429 (Rate Limit)**: Wait 10 seconds, then retry - **503 (Service Unavailable)**: Wait 5 seconds, then retry - **Max retries**: 3 attempts per ticket - **Failed tickets**: Report at end with error details ### Progress Reporting ``` Creating tickets... ✓ Epic created: PROJ-123 [Waiting 2s to avoid rate limiting...] ✓ Stories created: PROJ-124, PROJ-125, PROJ-126 (batch 1/3) [Waiting 2s...] ✓ Stories created: PROJ-127, PROJ-128, PROJ-129 (batch 2/3) ``` ### Best Practices - ⚠️ **Never create more than 5 tickets without a delay** - ⚠️ **Always wait at least 2 seconds between batches** - ⚠️ **Increase delays if rate limit errors occur** - ✓ **Show progress updates between batches** - ✓ **Report any failed tickets with retry instructions** ## Anti-Patterns to Avoid ❌ **Don't create separate tickets for**: - "Create file X" and "Configure file X" (combine them) - "Write tests" and "Run tests" (one ticket) - Each individual file change - Steps that take < 1 hour - Each CRUD operation separately ✅ **Do combine into single tickets**: - All database work for an entity (model + migration + seeder) - Related API endpoints (CRUD for one resource) - All configuration and setup for a feature - Testing for a component (unit + integration) - Documentation updates across files ## Document Format Support **Markdown Headers**: ```markdown # Epic: Feature Name ## Story: User Story (combines related implementation) ### Task: Implementation Task (only if story needs breakdown) ``` **Dependency Keywords**: - "depends on", "after", "requires", "blocks" ## Configuration - **Project Key**: `{{PROJECT_KEY}}` - **Default Assignee**: `{{DEFAULT_ASSIGNEE}}` - **Labels**: Based on content categories

{ "prompt": "# Create Tickets from Requirements\n\nParse requirement documents or task breakdown files and create structured tickets in {{ISSUE_TRACKER}}.\n\n## Usage\n\n```\n/assign-tasks docs/features/requirements.md\n/assign-tasks docs/tasks/feature-breakdown.md\n```\n\n## Task Consolidation Rules (CRITICAL)\n\nBefore creating tickets, consolidate tasks to reduce noise and improve focus.\n\n### Maximum Ticket Counts\n\n| Feature Size | Max Stories | Max Tasks/Story | Max Subtasks/Task |\n| ---------------- | ----------- | --------------- | ----------------- |\n| Small (< 8 SP) | 1-2 | 2-3 | 0 |\n| Medium (8-21 SP) | 2-4 | 3-4 | 2-4 |\n| Large (21-55 SP) | 4-8 | 4-6 | 4-8 |\n| XL (55+ SP) | 6-12 | 5-8 | 8-15 |\n\n### Consolidation Checklist\n\nBefore creating each ticket, ask:\n\n1. **Can these 2+ items be combined?** Group related work together\n2. **Is this subtask necessary?** Or is it just an obvious step?\n3. **Would a developer do these together?** If yes, combine them\n4. **Does this represent meaningful progress?** If not, merge it\n\n### Grouping Guidelines\n\n- **Merge related work**: Same component or feature area = 1 ticket\n- **Bundle by deliverable**: Group by what ships together\n- **Collapse small items**: < 2 SP should be subtasks or merged\n- **Limit hierarchy**: Prefer Epic → Story → Task (minimize Subtasks)\n\n## Epic Discovery (Parent Task Assignment)\n\nAll stories and tasks MUST belong to an Epic. Before creating tickets:\n\n### 1. Check for Explicit Parent\n\n- If the requirement doc specifies an Epic, use it\n- If linked from an existing Epic, use that Epic\n\n### 2. Search for Matching Epic\n\nIf no parent is specified, use MCP/{{ISSUE_TRACKER}} tools to find a suitable Epic:\n\n```\n# Search for open Epics in the project\n- List all Epics with status: Open, In Progress\n- Filter by labels/components matching the feature domain\n- Check Epic descriptions for related keywords\n```\n\n**Matching Criteria** (in priority order):\n\n1. **Domain match**: Epic covers same feature area (e.g., \"Authentication\", \"Payments\")\n2. **Component match**: Epic targets same system component\n3. **Sprint/Release match**: Epic is in current or upcoming sprint\n4. **Keyword match**: Epic title/description contains related terms\n\n### 3. Fallback to Maintenance Epic\n\nIf no appropriate Epic exists:\n\n- Search for existing \"Maintenance\" or \"Tech Debt\" Epic\n- If none exists, create one:\n ```\n Epic: Maintenance & Improvements - {{QUARTER}}\n Description: Technical improvements, bug fixes, and maintenance work\n Labels: maintenance, tech-debt\n ```\n\n### 4. Report Parent Assignment\n\nIn the ticket creation report, always include:\n\n```\nParent Epic: [EPIC-123] Epic Title\nAssignment Reason: Domain match (Authentication) | Maintenance fallback\n```\n\n## Process\n\n1. **Parse Document**:\n - Load the specified document (.md, .txt, .json)\n - Detect document structure (headers, lists, task categories)\n - Extract task hierarchy: Epic → Story → Task → Subtask\n\n2. **Consolidate First** (BEFORE creating tickets):\n - **Group related items** by component, feature area, or deliverable\n - **Merge small tasks** (< 2 SP) into related larger tasks\n - **Eliminate redundant subtasks** that are obvious steps\n - **Validate counts** against maximum limits above\n\n3. **Classify Consolidated Tasks**:\n - **Epic**: Large features, 13+ story points\n - **Story**: User-focused deliverable, 3-13 story points (prefer larger)\n - **Task**: Implementation work, 2-8 story points (avoid < 2 SP)\n - **Subtask**: Only for complex tasks, 1-3 story points (use sparingly)\n\n4. **Estimate Effort**:\n - 0.5-1 hours → **Merge with related task** (too small alone)\n - 2-3 hours → 2 story points\n - 4-6 hours → 3-5 story points\n - 7-12 hours → 8 story points\n - 13+ hours → 13 story points (consider splitting into stories)\n\n5. **Create Tickets**:\n - Create in proper hierarchy order (Epics first, then Stories, then Tasks)\n - Link child issues to parents\n - Set assignees, labels, and story points\n - Create dependency links where noted\n\n6. **Generate Report**:\n - List all created tickets with IDs\n - Show hierarchy and relationships\n - Report total story points\n - **Consolidation summary**: \"Merged X raw items into Y tickets\"\n\n## API Rate Limiting & Throttling\n\n**CRITICAL**: {{ISSUE_TRACKER}} APIs have rate limits. When creating multiple tickets:\n\n### Batch Strategy\n\n- **Small batches** (< 5 tickets): Create all tickets immediately\n- **Medium batches** (5-15 tickets): Create in groups of 5 with 2-second delays\n- **Large batches** (15+ tickets): Create in groups of 5 with 3-5 second delays\n\n### Implementation Pattern\n\n```\n1. Create Epic(s) first → Wait 2 seconds\n2. Create Stories (batch of 5) → Wait 2 seconds\n3. Create next Stories (batch of 5) → Wait 2 seconds\n4. Create Tasks (batch of 5) → Wait 3 seconds\n5. Continue batching with delays\n```\n\n### Error Handling\n\n- **429 (Rate Limit)**: Wait 10 seconds, then retry\n- **503 (Service Unavailable)**: Wait 5 seconds, then retry\n- **Max retries**: 3 attempts per ticket\n- **Failed tickets**: Report at end with error details\n\n### Progress Reporting\n\n```\nCreating tickets...\n✓ Epic created: PROJ-123\n [Waiting 2s to avoid rate limiting...]\n✓ Stories created: PROJ-124, PROJ-125, PROJ-126 (batch 1/3)\n [Waiting 2s...]\n✓ Stories created: PROJ-127, PROJ-128, PROJ-129 (batch 2/3)\n```\n\n### Best Practices\n\n- ⚠️ **Never create more than 5 tickets without a delay**\n- ⚠️ **Always wait at least 2 seconds between batches**\n- ⚠️ **Increase delays if rate limit errors occur**\n- ✓ **Show progress updates between batches**\n- ✓ **Report any failed tickets with retry instructions**\n\n## Anti-Patterns to Avoid\n\n❌ **Don't create separate tickets for**:\n\n- \"Create file X\" and \"Configure file X\" (combine them)\n- \"Write tests\" and \"Run tests\" (one ticket)\n- Each individual file change\n- Steps that take < 1 hour\n- Each CRUD operation separately\n\n✅ **Do combine into single tickets**:\n\n- All database work for an entity (model + migration + seeder)\n- Related API endpoints (CRUD for one resource)\n- All configuration and setup for a feature\n- Testing for a component (unit + integration)\n- Documentation updates across files\n\n## Document Format Support\n\n**Markdown Headers**:\n\n```markdown\n# Epic: Feature Name\n\n## Story: User Story (combines related implementation)\n\n### Task: Implementation Task (only if story needs breakdown)\n```\n\n**Dependency Keywords**:\n\n- \"depends on\", \"after\", \"requires\", \"blocks\"\n\n## Configuration\n\n- **Project Key**: `{{PROJECT_KEY}}`\n- **Default Assignee**: `{{DEFAULT_ASSIGNEE}}`\n- **Labels**: Based on content categories", "variables": [ "ISSUE_TRACKER", "QUARTER", "PROJECT_KEY", "DEFAULT_ASSIGNEE" ], "notes": "Create {{ISSUE_TRACKER}} tickets from requirements or task files", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/ninjasitm/ai-assisted-landing-demo", "path": ".github/prompts/assign-tasks.prompt.md", "ref": "b9f37b8be69bbd62ae5dac32dc5790784a4c384c", "url": "https://github.com/ninjasitm/ai-assisted-landing-demo/blob/b9f37b8be69bbd62ae5dac32dc5790784a4c384c/.github/prompts/assign-tasks.prompt.md", "key": "ninjasitm/ai-assisted-landing-demo/.github/prompts/assign-tasks.prompt.md" } } }

assign-tasks

About