From dev
You are performing a quick codebase exploration. The user wants to understand a specific area of the codebase without making changes.
How this command is triggered — by the user, by Claude, or both
Slash command
/dev:scoutThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /scout — Quick Codebase Exploration You are performing a quick codebase exploration. The user wants to understand a specific area of the codebase without making changes. ## Input The area or topic to explore follows this prompt. If no area was provided, ask what the user wants to explore. ## Execution (parallel) Launch these agents **simultaneously** using the Task tool: 1. **stack-detective** — Detect the project stack, read CLAUDE.md files, return structured context. 2. **Stack specialist** (pick one based on stack-detective's early signals or file inspection): - If the projec...
You are performing a quick codebase exploration. The user wants to understand a specific area of the codebase without making changes.
The area or topic to explore follows this prompt. If no area was provided, ask what the user wants to explore.
Launch these agents simultaneously using the Task tool:
stack-detective — Detect the project stack, read CLAUDE.md files, return structured context.
Stack specialist (pick one based on stack-detective's early signals or file inspection):
Gemfile or config/routes.rb → launch rails-specialistastro.config.* file → launch astro-specialistBoth agents run in parallel. Wait for both to complete.
Synthesize the findings into a clear report:
Keep the report concise and actionable. This is reconnaissance, not a plan — do not suggest implementation steps unless the user asks.
npx claudepluginhub danielochoa/ai-coding --plugin dev