tq-manager

name	tq-manager
description	Manage tq tasks and actions on behalf of the user via the tq CLI. Use when the user wants to create a task, add or dispatch an action, check queue status, run something now or interrupt, or schedule a recurring action. Lightweight interactive hub; hands off to tq:create-action / tq:done / tq:failed / tq:cancel / tq:triage for disciplined flows.
allowed-tools	Bash(tq *)

tq Manager

You manage tasks and actions on behalf of the user via tq CLI.

CLI reference (auto-loaded)

!tq task create --help !tq action create --help

Decision guide

• Which project? Ask if ambiguous. Check tq project list for IDs.
• Which instruction? Infer from context. If the user provides a direct instruction (e.g., a slash command), pass it as a positional argument to tq action create.
• Dispatch immediately? Only when the user explicitly asks to interrupt or run now. Otherwise create as pending.
• Default dispatch mode? It is configurable globally — inspect with tq config get default_mode, change with tq config set default_mode <mode>. New actions inherit it automatically; a per-action --meta '{"mode":...}' always overrides it. Do not rely on memory for the default — read it from tq config.
• Looking for past context? Use tq search "<keyword>" --project <id> to search within a specific project. Omit --project only when the target project is unknown.
• What did action #N find? Why did it stop? If tq action get <id> --jq '.result' is thin, resolve the Claude Code session log via the recipe below and Read its tail (~200 lines). When claude_session_id is empty, .result is the only signal.

SID=$(tq action get <id> --jq '.metadata | fromjson.claude_session_id // empty')
[ -n "$SID" ] && find ~/.claude/projects -name "$SID.jsonl" -print -quit

• Schedule/action mode? Default to interactive; pick noninteractive only when a long batch fleet would otherwise saturate the interactive slot pool. Both launch via claude --bg and consume the normal Claude Code allowance — the choice is purely a slot-pool concern, not a billing source. Set via --meta (merges — pass mode and claude_args together). Rationale and the full decision rule: docs/best-practices.md. Metadata keys: tq schedule create --help.
• Worktree? Optional. Add "--worktree" to claude_args for file-modifying actions that may run in parallel; skip for read-only or serialized work. When added, always pair with a scope-derived name ("--worktree","<scope-name>" — file, feature, or skill) so sessions are identifiable in the TUI and git worktree list.

Filtering output

IMPORTANT: Always use the built-in --jq flag for filtering. Never pipe to jq, python3, or other external commands — piped commands trigger user approval prompts and block execution.

# Good: single command, no approval needed
tq action list --jq '.[] | select(.task_id == 200) | .title'
tq task list --jq '.[] | select(.status == "open") | {id, title}'

# Bad: pipe triggers approval prompt
tq action list | jq '.[] | select(.task_id == 200)'
tq task list | python3 -c 'import json,sys; ...'

Related skills

This skill is the lightweight interactive hub. Hand off to the dedicated skills when the request is one of these — they encode discipline this skill does not:

• tq:create-action — authoring a self-contained delegation to a fresh worker session (goal-first instruction, effort/worktree selection). Use it whenever "creating the action is the deliverable" rather than doing the work now.
• tq:done / tq:failed / tq:cancel — recording an action's terminal state, with the merge-guard, remaining settlement, and task-level follow-up flow each enforces.
• tq:triage — inventory and cleanup across all open tasks.