← ClaudeAtlas

explorelisted

Investigate something open-ended before anyone commits to it, then say where the work actually starts. Use it for feasibility — "is this even possible?", "can we do X with our current stack?", "what would it take to support Y?", "spike this" — and for the stuck case: "I don't know where to start", "what should I do next?", "how do I start this?", "I'm stuck", "I want to understand how Z works before we commit", "research whether we should...". It fans out research and lands either a written spike report or a decision about which entry point the work belongs to. Guessing instead means committing to an approach nobody checked was possible. Do NOT use it once you already know what comes next: working out one feature is `/scope`, framing a whole initiative is `/charter`, running a finished plan is `/execute`, picking between options already named is `/decision`, and surveying named competitors is `/comp`.
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh explore 2>&1 || true` @.claude/shirabe-extensions/explore.md @.claude/shirabe-extensions/explore.local.md # Explore Explore is the entry point for "I don't know what I need." It serves two roles: as a passive routing advisor (when Claude is auto-loaded and users need help picking a command), and as an active exploration workflow (when invoked via /explore). Other skills own the work itself: `/scope` runs the tactical chain, `/charter` the strategic one, `/execute` drives a finished PLAN, and `/work-on` takes a single issue. Explore owns the question of which one receives the work, and it answers that question after the research rather than before it. **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Routing Guide When a user isn't sure where to start, use this table to recommend a command. Every destination is something the author runs. None of them is a step inside a chain that a parent skill already sequences: a BRIEF, a PRD, a DESIGN, and a PLAN are hops inside `/scope`, and picking one of them as an entry point is the choice this skill stopped making. Those hops stay directly invocable once their own upstream is settled -- `/design` on an accepted PRD, `/plan` on an accepted DESIGN -- but an author in that position is not asking where to start, so no row below points at them. | Situation | Route To | Why | |-----------|----------|-----| | "I want to build X but don't know where to start