sdd-explore
Explore SDD ideas before committing to a change. Trigger: orchestrator launches exploration or requirement clarification.
- License 许可
- MIT
- 最近更新
- 2026-07-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- sdd-explore
- license
- MIT
- metadata
- { "author": "gentleman-programming", "version": "2.0", "delegate_only": true }
- description
- Explore SDD ideas before committing to a change. Trigger: orchestrator launches exploration or requirement clarification.
- user-invocable
- false
- disable-model-invocation
- true
03 SKILL.md 正文
ORCHESTRATOR GATE: If you loaded this skill via the
skill()tool, you are the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to the dedicatedsdd-exploresub-agent using your platform's delegation primitive (e.g.,task(...), sub-agent invocation, etc.). This skill is for EXECUTORS only.
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 | hybrid | none)
Execution and Persistence Contract
Follow Section B (retrieval) and Section C (persistence) from
skills/_shared/sdd-phase-common.md.
- engram: Optionally read
sdd-init/{project}for project context. Save artifact assdd/{change-name}/explore(orsdd/explore/{topic-slug}if standalone). - openspec: Read and follow
skills/_shared/openspec-convention.md. - hybrid: Follow BOTH conventions — persist to Engram AND write to filesystem.
- none: Return result only.
Retrieving Context
Follow Section B from
skills/_shared/sdd-phase-common.mdfor retrieval.
- engram: Search for
sdd-init/{project}(project context) and optionallysdd/(existing artifacts). - openspec: Read
openspec/config.yamlandopenspec/specs/. - none: Use whatever context the orchestrator passed in the prompt.
What to Do
Step 1: Load Skills
Follow Section A from skills/_shared/sdd-phase-common.md.
Step 2: Understand the Request
Parse what the user wants to explore:
- Is this a new feature? A bug fix? A refactor?
- What domain does it touch?
Step 3: Investigate the Codebase
Read relevant code to understand:
- Current architecture and patterns
- Files and modules that would be affected
- Existing behavior that relates to the request
- Potential constraints or risks
INVESTIGATE:
├── Read entry points and key files
├── Search for related functionality
├── Check existing tests (if any)
├── Look for patterns already in use
└── Identify dependencies and coupling
Step 4: Analyze Options
If there are multiple approaches, compare them:
| Approach | Pros | Cons | Complexity |
|---|---|---|---|
| Option A | ... | ... | Low/Med/High |
| Option B | ... | ... | Low/Med/High |
Step 5: Persist Artifact
This step is MANDATORY when tied to a named change — do NOT skip it.
Follow Section C from skills/_shared/sdd-phase-common.md.
- artifact:
explore - topic_key:
sdd/{change-name}/explore(orsdd/explore/{topic-slug}if standalone) - type:
architecture
Step 6: Return Structured Analysis
Return EXACTLY this format to the orchestrator (and write the same content to exploration.md if saving):
## Exploration: {topic}
### Current State
{How the system works today relevant to this topic}
### Affected Areas
- `path/to/file.ext` — {why it's affected}
- `path/to/other.ext` — {why it's affected}
### Approaches
1. **{Approach name}** — {brief description}
- Pros: {list}
- Cons: {list}
- Effort: {Low/Medium/High}
2. **{Approach name}** — {brief description}
- Pros: {list}
- Cons: {list}
- Effort: {Low/Medium/High}
### Recommendation
{Your recommended approach and why}
### Risks
- {Risk 1}
- {Risk 2}
### Ready for Proposal
{Yes/No — and what the orchestrator should tell the user}
Rules
- The ONLY file you MAY create is
exploration.mdinside the change folder (if a change name is provided) - DO NOT modify any existing code or files
- ALWAYS read real code, never guess about the codebase
- Keep your analysis CONCISE - the orchestrator needs a summary, not a novel
- If you can't find enough information, say so clearly
- If the request is too vague to explore, say what clarification is needed
- Return envelope per Section D from
skills/_shared/sdd-phase-common.md.
04 同仓库更多 Skills
zustand-5
Zustand 5 state management patterns. Trigger: When managing React state with Zustand.
zod-4
Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.