From vibe-engineering
Manages persistent cross-session JSON task queue for non-blocking work like deferred fixes, TODOs, non-urgent reviews, and flaky tests. Tracks priority, status, acceptance criteria.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vibe-engineering:async-task-queueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Not everything needs to be done right now. But "I'll do it later" only works if "later" actually happens.
Not everything needs to be done right now. But "I'll do it later" only works if "later" actually happens.
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"
}
]
}
in_progresscompleted, commitpending, add notes about what went wrongList all tasks with status counts. Identify stale tasks (>7 days pending).
Pending: X | In Progress: Y | Completed: Z | Failed: W
| ID | Priority | Description | Age | Status |
|---|---|---|---|---|
| vibe-001 | high | Add auth token refresh | 2d | pending |
| vibe-002 | medium | Fix flaky test in utils | 5d | pending |
npx claudepluginhub ash1794/vibe-engineering --plugin vibe-engineeringManage a deferred task queue — add, list, process, remove, batch-execute, schedule, prioritize, and browse history of tasks stored in the vault.
Executes eligible tasks from session task list, syncs against codebase/PR state to surface stales, and generates handovers. Use /task-run [--all] [--sync [--dry-run]] [--handover [query]].