Skip to content
Back to skills

Sdd Explore

ASecurity

Codebase analysis and context gathering for spec-driven development

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
ai-agentsgogitapisecurityperformance

Works with

  • cli
  • api

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add PedroMosquera/squadai --skill sdd-explore --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sdd Explore?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sdd Explore
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pedromosquera-sdd-explore/badge)](https://www.skillsdirectory.com/skills/pedromosquera-sdd-explore)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sdd-explore
description: Codebase analysis and context gathering for spec-driven development
methodology: sdd
---

# SDD Explore Skill

Analyze an existing codebase to gather context before proposing solutions.
This is the first phase of the SDD pipeline: understand before proposing.

## Steps

1. **Identify entry points**: Find where the relevant system behavior begins.
   - Main functions, HTTP handlers, CLI commands, event listeners
   - Public API surfaces (exported functions, interfaces)
   - Configuration loading points

2. **Trace data flow**: Follow data through the system.
   - How does input enter the system?
   - What transformations does it undergo?
   - Where is data persisted or returned?
   - What are the side effects?

3. **Map dependencies**: Understand what depends on what.
   - Internal package dependencies
   - External library dependencies
   - Interface boundaries and their implementations
   - Circular dependency risks

4. **Identify hotspots**: Flag areas of concern.
   - Files changed frequently in git log
   - Code with high complexity or low test coverage
   - Undocumented magic behavior
   - Areas where the feature request will require changes

5. **Document constraints**: Note existing commitments.
   - Public API contracts that must not break
   - Performance SLAs or resource limits
   - Security requirements (auth, input validation)
   - Compatibility requirements (old data formats, deprecated paths)

6. **Summarize for the Proposer**: Produce a context document.
   - Overview of relevant system components
   - Key data structures and their relationships
   - Constraints the Proposer must respect
   - Open questions that need clarification

## Output Format

```
## 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>
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…