acquire-skillslisted

# Acquire Skills Find and install skills for the current task — across both tech and thinking/reasoning dimensions. ## Usage ``` /brana:acquire-skills — scan current activity + project /brana:acquire-skills <task-id> — scan a specific task's needs /brana:acquire-skills <keyword> — direct search ("cloudflare", "decision matrix") ``` ## Never suggest these (brana workflow internals) The following skills are system workflow tools, not capability skills. Never surface them as recommendations: `build`, `backlog`, `close`, `sitrep`, `onboard`, `align`, `reconcile`, `ship`, `docs`, `retrospective`, `review`, `gemini`, `claudemd`, `plugin`, `scheduler`, `do`, `log`, `export-pdf`, `verify-docs`, `client-retire`, `cargo-machete`, `bash-defensive-patterns`, `rust-skills`, `gsheets`, `meta-templates`, `mcp-builder`, `memory`, `discover`. Thinking skills ARE valid to recommend: `decide`, `brainstorm`, `challenge`, `swot-analysis`, `decision-matrix`, `critical-thinking-logical-reasoning`, `pre-mortem`, `inversion`, `first-principles`, `second-order-thinking`, `six-thinking-hats`, `systems-thinking`, `jobs-to-be-done`. ## Process ### Step 0: Detect mode From `$ARGUMENTS`: - **No argument:** run Steps 1a + 1b (activity detection + tech scan) - **Task ID (t-NNN):** read task from `.claude/tasks.json`, extract subject + tags + description → use as context for both Steps 1a and 1b - **Keyword:** skip Steps 1a + 1b entirely, use keyword directly in S