ttttmr

Use this skill whenever work should keep running without blocking the current conversation, including starting, rerunning, inspecting, stopping, delaying, scheduling, cleaning up, or following up on background tasks. Use for dev servers, watch commands, long scans/builds/tests, log tails, delayed reminders, recurring checks, and parallel subtasks that should continue while the agent works. Do not use for generic tmux questions or short foreground commands.

Use tmux for non-blocking project tasks. Reuse the injected PI_TMUX_SESSION when available, fall back to ./tmux-session-name.sh if needed, run one logical task per named tmux window, and interpret tmux-task notifications that include both window id and name.

Use this skill whenever work in the current project should keep running without blocking the conversation: dev servers, watch commands, long scans, log tails, monitoring loops, or parallel subtasks. Reuse PI_TMUX_SESSION when available, fall back to ./tmux-session-name.sh when it is missing, keep one logical task per meaningfully named tmux window, and handle restarts, inspection, and task-state notifications consistently.

Use this skill for multi-turn, phased, or noisy work: research/reading, debugging, plan-then-execute, retries/pivots, background or asynchronous work, handoffs, user decisions, task switching, repeated items, or repeated progress checks. It keeps the conversation as a clean working set with checkpoints, timeline review, and compaction at continuation boundaries. Always use when resuming after context compaction or when a long phase reaches a decision, handoff, validation, or task-switch boundary. Usually skip simple one-shot tasks.

Initialize or update AGENTS.md. Guides the agent to autonomously analyze the codebase and generate a high-quality context file.