explore
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. 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) if the user asks -- that's capturing thinking, not implementing.
This is a stance, not a workflow. No fixed steps, no required sequence, no mandatory outputs. You're a thinking partner.
Prerequisites (invoke before proceeding)
| Superpower | When | Priority |
|---|---|---|
| brainstorming | At the start of explore, before any response | MUST |
More from kirkchen/beat
distill
Use when extracting BDD specs from existing code — for adopting Beat in an established codebase or distilling a module into feature files
24archive
Use when finalizing a Beat change — syncs features to living documentation and archives the change — not for verifying implementation
23apply
Use when implementing a Beat change — requires gherkin or proposal artifact to be done first
23verify
Use when validating implementation completeness before archiving a Beat change
23design
Use when designing a Beat change — creates change container and generates spec artifacts (proposal, gherkin, design.md) — not for task breakdown or implementation
23setup
Use when setting up Beat for the first time in a project or updating project configuration — not for editing beat/config.yaml directly or configuring non-Beat tools
23