OpenParable
Skip to content
← Back to skills

Vibe Async Task Queue

Productivity
vibe-async-task-queue

Vibe Async Task Queue is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Provides a persistent cross-session task queue for work that should be done but isn't blocking current tasks. Enables background and future-session work tracking.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/productivity/async-task-queue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vibe-async-task-queue, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

vibe-async-task-queue

Not everything needs to be done right now. But "I'll do it later" only works if "later" actually happens.

When to Use This Skill

  • You identify work that should be done but isn't blocking the current task
  • During code review, you find issues that aren't urgent
  • Tests reveal non-critical flakiness
  • Documentation needs updating but not right now
  • "TODO" comments that should become tracked tasks

When NOT to Use This Skill

  • Blocking work that must be done now
  • Tasks already tracked in an issue tracker (GitHub Issues, Jira, etc.)
  • One-off tasks in the current session (just do them)

Queue Format

Tasks are stored in a JSON file at a project-specific location (e.g., .claude/task-queue.json):

{
  "tasks": [
    {
      "id": "vibe-001",
      "created": "2026-02-28",
      "priority": "medium",
      "status": "pending",
      "description": "Add error handling to parseConfig edge cases",
      "target_files": ["internal/config/parser.go"],
      "acceptance": "go test ./internal/config/... -run TestParseConfigEdge -v passes",
      "context": "Discovered during fuzz testing session"
    }
  ]
}

Steps

Adding a Task

  1. Identify the work
  2. Write a clear description with:
    • What needs to be done
    • Which files are affected
    • How to verify it's done (acceptance command)
    • Why it was deferred (context)
  3. Append to queue file

Processing the Queue

  1. Read queue file
  2. Pick highest-priority pending task
  3. Set status to in_progress
  4. Do the work
  5. Run acceptance test
  6. If pass: set status to completed, commit
  7. If fail: set status to pending, add notes about what went wrong

Reviewing the Queue

List all tasks with status counts. Identify stale tasks (>7 days pending).

Output Format

Task Queue Status

Pending: X | In Progress: Y | Completed: Z | Failed: W

IDPriorityDescriptionAgeStatus
vibe-001highAdd auth token refresh2dpending
vibe-002mediumFix flaky test in utils5dpending

Stale Tasks (>7 days)

  • [task IDs that need attention or should be closed]