sdd-explore
Codebase analysis and context gathering for spec-driven development
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Codebase analysis and context gathering for spec-driven development
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Structured code review
Find and load available skills
PR description generation
Spec-faithful implementation for spec-driven development
Architecture and interface design for spec-driven development
Codebase analysis and context gathering for spec-driven development
| name | sdd-explore |
| description | Codebase analysis and context gathering for spec-driven development |
| methodology | sdd |
Analyze an existing codebase to gather context before proposing solutions. This is the first phase of the SDD pipeline — understand before proposing.
Identify entry points: Find where the relevant system behavior begins.
Trace data flow: Follow data through the system.
Map dependencies: Understand what depends on what.
Identify hotspots: Flag areas of concern.
Document constraints: Note existing commitments.
Summarize for the Proposer: Produce a context document.
## Exploration Report: <topic>
### Entry Points
- <file/function>: <description of role>
### Data Flow
<brief description or diagram>
### Key Data Structures
- <type>: <description and purpose>
### Constraints
- <constraint>: <why it exists>
### Hotspots
- <area>: <risk or complexity reason>
### Open Questions
1. <question needing clarification before proposing>