← ClaudeAtlas

offline-questionslisted

Use when the user wants to park a question for later — fires a background subagent that researches with full session context and appends a structured answer to ~/Desktop/Offline_Questions_and_Answers.md. Trigger phrases include "park this question", "research this offline", "I care about this but not now", or invocation via /offline-question.
amitkot/claude-code-tools · ★ 0 · AI & Automation · score 73
Install: claude install-skill amitkot/claude-code-tools
# Offline Questions The user is in the middle of something and has thought of a question they care about but don't want to derail the current session for. Your job is to capture the question with rich context, hand it to a background subagent for research, and let the user keep working. The subagent appends a structured Q&A entry to `~/Desktop/Offline_Questions_and_Answers.md` and fires a desktop notification when done. ## Your job (the main agent) You do **four** things, in order: ### 1. Echo the parked question (one line) Before spawning anything, surface what you're about to send off so the user can catch a wrong-question disaster: > Parking: *"<question>"* — researching in background (mode: standard | deep). That's it. No further prose, no summary of what you're about to do. ### 2. Build the curated briefing This is the most important step. The subagent has zero session context — what makes this skill better than the user opening a new Claude tab is **you** filtering the conversation down to the relevant signal. Write the briefing as if you were handing a smart colleague who just walked into the room a focused note. Structure (these section headers go in the briefing prompt verbatim): ``` # Offline question ## The question <verbatim what the user asked, no rewording> ## Session context <3-6 sentences. What were we working on? What had we already established? What had the user already ruled out? What made this question come up *now*? Be specific — name the fil