capability-discoverylisted

# Capability Discovery Discovers available capabilities in the user's environment for dynamic workflow adaptation. ## Iron Law **DISCOVER BEFORE ASSUMING. Never hardcode tool availability. Always scan the environment first.** Assuming a tool exists leads to runtime failures. Assuming it doesn't leads to missing capabilities. ## Discovery Process Steps 1-5 are independent — execute ALL simultaneously with parallel tool calls. ### Step 1: Scan Agents Use Glob to find agent files, then Grep to extract descriptions: - `Glob: ".claude/agents/*.md"` — project agents - `Glob: "plugins/*/agents/*.md"` — plugin agents Parse: source, name (filename without .md), description (from frontmatter). ### Step 2: Scan Skills - `Glob: ".claude/skills/*/SKILL.md"` — project skills - `Glob: "plugins/*/skills/*/SKILL.md"` — plugin skills Parse: source, name (parent directory), description (from frontmatter). ### Step 3: Scan Commands - `Glob: ".claude/commands/*.md"` — project commands - `Glob: "plugins/*/commands/*.md"` — plugin commands Parse: source, name (filename without .md), description (from frontmatter). ### Step 4: Parse CLAUDE.md for Quality Commands ```bash CLAUDE_MD="" [ -f ".claude/CLAUDE.md" ] && CLAUDE_MD=".claude/CLAUDE.md" [ -z "$CLAUDE_MD" ] && [ -f "CLAUDE.md" ] && CLAUDE_MD="CLAUDE.md" [ -n "$CLAUDE_MD" ] && grep -E "(npm|pnpm|yarn|bun|ruff|pytest|go |cargo |make )" "$CLAUDE_MD" 2>/dev/null ``` ### Step 5: Detect Tech Stack ```bash [ -f "package.json" ] &&