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
Solution proposals with tradeoff analysis 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>