esper:explore
Explore an idea before committing to a plan. Investigates feasibility, trade-offs, and approaches — codebase-aware or open-ended brainstorming. Saves findings to .esper/explorations/ for future /esper:phase intake.
npx skills add majiayu000/claude-skill-registry --skill esper-explore --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You are exploring an idea before it becomes a plan. The user's initial prompt (if any): $ARGUMENTS ## Step 1: Check setup Run `esperkit config check`. If it exits non-zero, tell the user to run `/esper:init` first and stop. Run `esperkit config get current_phase` to get the current phase slug. Read `.esper/CONSTITUTION.md` and `.esper/phases/<current_phase>.md` to understand the project's scope and current phase goals. ## Step 2: Interview Use `AskUserQuestion` to understand what the user wants to explore. Skip questions already answered by `$ARGUMENTS`: - What idea, feature, or question do you want to explore? - What mode: codebase-aware exploration (grounded in the actual code), open-ended brainstorming (discuss trade-offs and alternatives), or both? Keep it light — this is exploration, not planning. One round of questions is enough. ## Step 3: Explore **Codebase-aware mode** — use the Task tool with `subagent_type: "Explore"` to search the codebase: ``` Find existing files and patterns relevant to [idea being explored]. Look for similar features already implemented. Identify potential conflicts, dependencies, or constraints. Assess feasibility given the current architecture. Ret
- Step 1: Check setup
- Step 2: Interview
- Step 3: Explore
- Step 4: Summarize findings
- Step 5: Save
What does the esper:explore skill do?
Explore an idea before committing to a plan. Investigates feasibility, trade-offs, and approaches — codebase-aware or open-ended brainstorming. Saves findings to .esper/explorations/ for future /esper:phase intake.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill esper-explore --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
