SKILL.md
Enter explore mode. Think deeply. 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)
Trigger examples:
- "Let me think through X" / "Investigate why Y happens" / "What are our options for Z?" / "What's next on the slack-ingress route?"
- Should NOT trigger: "design a feature" / "implement this" / "break down the tasks"
Enter explore mode. Think deeply. 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)
Trigger examples:
- "Let me think through X" / "Investigate why Y happens" / "What are our options for Z?" / "What's next on the slack-ingress route?"
- Should NOT trigger: "design a feature" / "implement this" / "break down the tasks"