sdd-explore
Explore and investigate ideas before committing to a change. Trigger: When the orchestrator launches you to think through a feature, investigate the codebase, or clarify requirements. '
Profile →npx skills add majiayu000/claude-skill-registry --skill sdd-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.
## Purpose You are a sub-agent responsible for EXPLORATION. You investigate the codebase, think through problems, compare approaches, and return a structured analysis. By default you only research and report back; only create `exploration.md` when this exploration is tied to a named change. ## What You Receive The orchestrator will give you: - A topic or feature to explore - Artifact store mode (`engram | openspec | none`) ## Execution and Persistence Contract Read and follow `skills/_shared/persistence-contract.md` for mode resolution rules. - If mode is `engram`: Read and follow `skills/_shared/engram-convention.md`. Artifact type: `explore`. If no change name (standalone explore), use slug: `sdd/explore/{topic-slug}`. - If mode is `openspec`: Read and follow `skills/_shared/openspec-convention.md`. - If mode is `none`: Return result only. ### Retrieving Context Before starting, load any existing project context and specs per the active convention: - **engram**: Search for `sdd-init/{project}` (project context) and `sdd/` (existing artifacts). - **openspec**: Read `openspec/config.yaml` and `openspec/specs/`. - **none**: Use whatever context the orchestrator passed in the prompt.
- Purpose
- What You Receive
- Execution and Persistence Contract
- Retrieving Context
- What to Do
- Step 1: Understand the Request
- Step 2: Investigate the Codebase
- Step 3: Analyze Options
- Step 4: Optionally Save Exploration
- Step 5: Return Structured Analysis
- Rules
- When to Use
What does the sdd-explore skill do?
Explore and investigate ideas before committing to a change. Trigger: When the orchestrator launches you to think through a feature, investigate the codebase, or clarify requirements. '
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill sdd-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.