skills.rest
juanmanueldaza
juanmanueldazaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdd-explore

Captures a read-only snapshot of a repository to identify files, interfaces, dependencies, and conventions for SDD planning.

Updated Apr 20, 2026
Search Tags:#workflow#context#codebase#analysis#memory#sdd
One-click install
npx skills add https://github.com/juanmanueldaza/invencible --skill sdd-explore-juanmanueldaza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/juanmanueldaza/invencible/tree/main/.claude/skills/sdd-explore
Command: npx skills add https://github.com/juanmanueldaza/invencible --skill sdd-explore-juanmanueldaza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture a read-only snapshot of the codebase to inform planned changes without proposing solutions.

Core Features & Use Cases

  • Context discovery: identify interfaces, modules, dependencies, and conventions relevant to the requested change.
  • Risk and pattern awareness: note potential risks, surrounding patterns, and integration touchpoints to guide SDD planning.
  • Use Case: start an SDD workflow by gathering the code context before proposing any architectural changes.

Quick Start

Inspect the repository to collect contextual information about the target change and save it to memory for later recall.

Frequently Asked Questions about sdd-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture codebase context for planned changes without modifying the source code?▼

Codebase context analysis involves inspecting the repository to collect contextual information about a target change. It identifies relevant modules, dependencies, and integration touchpoints to guide structured software design workflows.

What's the best way to start an SDD workflow by gathering code context?▼

Start an SDD workflow by inspecting the repository to collect contextual information and saving it to memory. This provides reliable recall of codebase conventions and interfaces for later decision-making.

Can I use this context discovery approach to identify integration touchpoints and risks across modules?▼

Yes, context discovery identifies interfaces, modules, dependencies, and conventions relevant to requested changes. It notes potential risks, surrounding patterns, and integration touchpoints to guide planning.

Does this codebase analysis propose architectural solutions for the identified changes?▼

No, this codebase analysis captures a read-only snapshot to inform planned changes without proposing solutions. It strictly focuses on memory-anchored context, structured notes, and identifying existing patterns.

Why do I need memory-anchored context and structured notes when analyzing a codebase?▼

Memory-anchored context and structured notes ensure reliable recall of discovered interfaces and dependencies during later decision-making. They provide a persistent, accurate reference point before architectural changes are proposed.

Are there limitations to using a read-only snapshot for codebase analysis?▼

The main limitation is that a read-only snapshot informs planned changes without proposing solutions or executing modifications. It strictly gathers context, meaning subsequent implementation requires separate downstream processing steps.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
dilhanzdilhanz
9

ship-design

Present architectural approaches for software features with trade-offs.

Community
Intermediate
koki3141koki3141
2

checkpoint-manager

Create, verify, and list git snapshot workflow checkpoints.

Community
Intermediate
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced