/sc-explore

name: sc-explore
description: Research, analyze, and explore to build understanding
argument-hint: Research query or topic to explore

sc-explore: Research and Understanding Command

**Purpose**: I need to understand something - conducts research, analysis, codebase exploration, and knowledge synthesis to build understanding

Agent Orchestration and Deployment Strategy

**Efficiency First:** Handle tasks directly when possible. Use agents only when genuinely needed for:

• Multi-step coordination requiring handoffs
• Specialized domain expertise beyond general capability
• Parallel work streams with interdependencies
• Complex analysis requiring multiple perspectives
• Operations that produce verbose intermediate output

**Direct Agent Rules (ALWAYS delegate these):**

• **Deep codebase analysis** → Use `sc-code-explorer`
• **Architecture design** → Use `sc-code-architect`
• **Code quality review** → Use `sc-code-reviewer`

**Available Agents:**

• `sc-code-explorer` - Deeply analyzes existing codebase features by tracing execution paths and mapping architecture
• `sc-code-architect` - Designs feature architectures by analyzing existing patterns and providing implementation blueprints
• `sc-code-reviewer` - Reviews code for bugs, security vulnerabilities, and adherence to project conventions

**Context Preservation:**

• **Keep only**: user request, actionable recommendations, code changes, summary, next steps
• **Discard**: intermediate outputs, full docs, verbose logs, exploratory reads

**Processing Pipeline**: Parse → Classify → Validate → Route → Execute → Synthesize

Intent Recognition and Semantic Transformation

This command interprets natural language requests that express the intent: "I need to understand something" - research, analysis, exploration, learning, or investigation of codebases, technologies, concepts, or domain knowledge.

**Command Execution:**

**Empty $ARGUMENTS**: Display usage suggestions → stop **Has content**: Parse intent → apply strategy → route execution

**Intent Processing:** Extract intent → Apply strategy matrix → Validate → Execute

**Strategy Matrix:**

| Condition | Direct Handling | Agent Required | | --------- | ------------------- | ------------------------------ | | Task Type | Simple, single-step | See "Direct Agent Rules" above | | Domain | Single, familiar | Multi-tech, unknown | | Context | Available locally | External research needed | | Output | Concise, focused | Verbose, needs filtering |

Transforms: $ARGUMENTS into structured execution:

• Intent: [recognized-user-intent]
• Approach: [direct/agent with reasoning]
• Agents: [none OR minimal-viable-set]

Output Template

## Response

[Direct answer or action taken - 1-3 sentences addressing the core request]

## Details

[Main content based on command type:
- Plan: Strategy breakdown with phases
- Work: Code changes and implementation steps
- Explore: Research findings and analysis
- Review: Issues found and quality assessment]

## Next Actions

[What to do next:
- Plan: Implementation steps to begin
- Work: Testing and validation needed
- Explore: Areas for deeper investigation
- Review: Fixes and improvements to make]

## Notes

[Optional - context, warnings, alternatives, or additional considerations]

---

**User Request**: $ARGUMENTS