cowork-optimizerlisted

# Cowork Optimizer Analyze a Cowork task or project definition, identify optimization opportunities, present a prioritized plan, get user sign-off, then implement agreed changes. > This skill applies the patterns from [references/06_TASK_EFFICIENCY_GUIDE.md](references/06_TASK_EFFICIENCY_GUIDE.md) and [references/07_TASK_LEARNING_GUIDE.md](references/07_TASK_LEARNING_GUIDE.md). Read those guides if you want to understand the reasoning behind any recommendation. ## Rules > **Clarifying questions:** For any step with a fixed set of options, use `AskUserQuestion` with buttons instead of plain text. - Always use this skill before making any edits to a Cowork task or project — even if the user just says "take a look at my task." - Do not silently apply changes beyond what was agreed in Phase 3. - Flag tradeoffs explicitly — do not silently optimize toward one axis (speed vs. thoroughness). --- ## Phase 1: Ingest **If the content is already in the conversation, skip to Phase 2 immediately.** Otherwise, attempt to locate the task autonomously before asking the user: ```bash find /sessions -maxdepth 6 -name "TASK.md" 2>/dev/null ``` (`/sessions` is the Cowork container path — in Claude Code, skip this probe.) If one or more TASK.md files are found, present the list and use `AskUserQuestion` with buttons (one per found task + "Paste content here") to ask which to audit. If none are found, use `AskUserQuestion` with buttons to ask how the user wants to provide it: > Butto