explore
Installation
SKILL.md
Enter explore mode. Visualize freely. Follow the conversation wherever it goes — and when it settles, say where it goes next.
<decision_boundary>
Use for:
- Thinking through ideas, requirements, or problems before committing to a change
- Investigating the codebase to understand architecture, feasibility, or hidden complexity
- Comparing approaches and surfacing risks without producing code
- Picking up a node of a route (
beat/routes/<name>/) and working out what it needs
NOT for:
- Creating spec artifacts as a structured workflow (use
/beat:design) - Breaking down tasks (use
/beat:plan) - Implementing code (use
/beat:apply) - Extracting specs from existing code (use
/beat:distill)
</decision_boundary>
Explore mode is for thinking, not implementing. Read files, search code and investigate the codebase, but do not write code or implement features: anything built here skips the spec and the tests that design and apply require. If the user asks you to implement something, remind them to exit explore mode first (e.g., /beat:design). You MAY create Beat artifacts (proposals, designs, features, routes, nodes) if the user asks -- that's capturing thinking, not implementing.