Menú
Instantly capture user ideas to work queue with intelligent grouping
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Route complex requests to the right specialist agent or chain of agents. This skill acts as the central brain of an agent swarm — it analyses what the user needs, determines which specialist domain(s) are required, and coordinates parallel or sequential agent execution. Use this skill when a request spans multiple domains (e.g., "research competitors and create a pitch deck"), when you need to decide which specialist should handle an ambiguous request, or when a task requires a multi-step pipeline across different skills. Triggers on: multi-step requests, cross-domain tasks, "coordinate", "plan this out", "I need help with multiple things", or any complex request that touches more than one specialist area. Also triggers when the user seems unsure which tool or approach to use.
>-
>-
>-
>-
Compare entity financial ratios against ATO small business benchmarks to assess audit probability
| name | idea-queue-capture |
| description | Instantly capture user ideas to work queue with intelligent grouping |
| version | 1.0.0 |
This skill provides fast, interruption-free idea capture for the autonomous work queue system. It follows Matt Maher's "do-work" pattern where one Claude instance (Capture) collects ideas while another instance (Work) executes them.
Key Principle: Capture is FAST. No planning, no validation, no execution - just preserve the full context and queue it.
Extract all distinct ideas from the user's message:
Analyze if ideas should be grouped or separated:
Group together (create single queue item) if:
Separate (create multiple queue items) if:
Example Grouping:
Input: "Fix the copy icon overlap in description panel AND adjust the panel spacing"
Output: 1 queue item (both affect description panel)
Input: "Fix copy icon overlap. Also analyze R&D transactions for FY2023-24"
Output: 2 queue items (UI vs tax analysis - completely different domains)
Based on keywords and context:
| Keywords | Type |
|---|---|
| "bug", "fix", "broken", "error", "issue" | bug |
| "feature", "add", "new", "create", "build" | feature |
| "improve", "enhance", "optimize", "refactor", "better" | improvement |
| "client", "customer", "stakeholder", "requested" | client_request |
| Everything else | task |
Create concise title (max 80 chars):
import { addToQueue } from '@/lib/queue/work-queue-manager';
const queueItem = await addToQueue({
title: generatedTitle,
description: userInputVerbatim, // Full user message preserved
queue_item_type: detectedType,
payload: {
original_message: userInput,
context: currentContext,
timestamp: new Date().toISOString(),
source: 'capture-skill',
},
});
Return clear confirmation with:
# Required (already configured in ATO)
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
Uses the work_queue table created by migration 20260129_create_work_queue.sql.
/capture-ideaCapture the current user message as an idea.
Usage:
User: Fix the navigation header padding in mobile view
User: /capture-idea
/capture-request <text>Capture specific text as a request.
Usage:
/capture-request Add dark mode toggle to settings page
/capture-multipleExplicitly capture multiple separate ideas from the message.
Usage:
User: Fix button color. Also update the form validation. And review tax calculations.
User: /capture-multiple
Creates 3 separate queue items.
/list-queueShow pending queue items and their positions.
Usage:
/list-queue
Output:
📋 Work Queue Status
Pending (3 items):
1. Fix copy icon overlap - P2 - Bug - 2 mins ago
2. Add R&D analysis for FY2023-24 - P1 - Feature - 15 mins ago
3. Update navigation spacing - P3 - Improvement - 1 hour ago
Validated (1 item):
1. Fix description panel spacing - P2 - Bug - Ready for execution
Currently processing: Analyzing deduction opportunities (12% complete)
Total in queue: 4 items
/queue-statsShow detailed queue statistics.
Usage:
/queue-stats
Output:
📊 Queue Statistics
Total items processed: 127
Average execution time: 8.3 minutes
Total token usage: 45,230 PTS
Status breakdown:
- Pending: 3
- Validated: 1
- Processing: 1
- Completed: 119
- Failed: 2
- Archived: 115
Success rate: 98.4%
{
"status": "success",
"captured": [
{
"id": "uuid-123",
"title": "Fix copy icon overlap in description panel",
"type": "bug",
"status": "pending",
"queue_position": 3,
"created_at": "2026-01-29T10:30:00Z"
}
],
"message": "1 idea captured successfully",
"next_steps": "The Senior PM agent will validate this idea and create a Linear issue if approved."
}
{
"status": "success",
"captured": [
{
"id": "uuid-123",
"title": "Fix navigation header padding",
"type": "bug",
"status": "pending",
"queue_position": 3
},
{
"id": "uuid-456",
"title": "Analyze R&D transactions for FY2023-24",
"type": "feature",
"status": "pending",
"queue_position": 4
}
],
"message": "2 ideas captured successfully",
"next_steps": "The Senior PM agent will validate these ideas and create Linear issues if approved."
}
{
"status": "error",
"error": "Failed to add item to queue: Database connection failed",
"suggestions": [
"Check SUPABASE_SERVICE_ROLE_KEY is configured",
"Verify Supabase project is running",
"Run migration: supabase migration up"
]
}
When capturing ideas, use clear, friendly language:
✅ Idea captured successfully!
**Title**: Fix copy icon overlap in description panel
**Type**: Bug
**Queue position**: #3
The Senior PM agent will validate this and create a Linear issue shortly.
You can continue working - this won't interrupt your current task.
✅ 2 ideas captured successfully!
1. **Fix navigation header padding** (Bug) - Position #3
2. **Analyze R&D transactions** (Feature) - Position #4
Both ideas will be validated by the Senior PM agent.
⚙️ Idea captured! The work queue is currently processing other items.
**Your idea**: Add dark mode toggle
**Position**: #5 in queue
**Estimated wait**: ~15 minutes
You'll be notified when your idea reaches validation.
If queue write fails:
If title/description too long:
truncated: trueNOT performed at capture stage (deferred to PM validation):
| Metric | Target |
|---|---|
| Capture time | < 2 seconds |
| User wait time | Immediate response |
| Database write | < 500ms |
| Message parsing | < 100ms |
SUPABASE_SERVICE_ROLE_KEY for database accessImportant: If user provides sensitive information (passwords, API keys), capture includes it. Warn user:
⚠️ Warning: Your idea contains what looks like sensitive information.
Please review the queue item before the Senior PM validates it.
/list-queue shows correct status/queue-stats calculates correctlyUser: The navigation header has too much padding on mobile devices. It's covering content.
User: /capture-idea
Claude: ✅ Idea captured successfully!
**Title**: Fix navigation header padding on mobile
**Type**: Bug
**Queue position**: #1
The Senior PM agent will validate this and create a Linear issue shortly.
User: The description panel on the right has two issues:
1. The copy icon overlaps with text
2. There's not enough spacing between sections
User: /capture-idea
Claude: ✅ Idea captured successfully!
**Title**: Fix description panel UI issues
**Type**: Bug
**Queue position**: #2
Grouped 2 related issues into 1 queue item since they affect the same component.
The Senior PM will validate and route to the appropriate agent.
User: Fix the copy icon overlap. Also, I need an analysis of all R&D eligible transactions for FY2023-24.
User: /capture-idea
Claude: ✅ 2 ideas captured successfully!
1. **Fix copy icon overlap** (Bug) - Position #3
2. **Analyze R&D eligible transactions for FY2023-24** (Feature) - Position #4
Created separate queue items since these are different domains (UI vs tax analysis).
Both will be validated by the Senior PM agent.
/process-queue