explorelisted

@.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 specific artifact types: /prd owns requirements, /design owns technical architecture, /plan owns issue decomposition. Explore owns the question of WHICH artifact type to produce. It investigates before committing. **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Artifact Type Routing Guide When a user isn't sure what to build, use this table to recommend a starting point. | Situation | Route To | Why | |-----------|----------|-----| | "I want to build X but don't know where to start" | `/explore <topic>` | Open-ended; the right artifact type isn't clear yet | | "Should I write a PRD or design doc?" | Read the decision table below | Match signals to the situation | | "I know what to build, not how" | `/design <topic>` | What-to-build is settled, how-to-build is the question | | "I have a feature named but haven't framed its problem and scope yet" | `/brief <topic>` | Frames a feature's problem, outcome, journeys, and scope before requirements; the step between roadmap and PRD | | "I know what we need but haven't written it down" | `/prd <topic>` | Requirements need to be captured and agreed on | |