sdd-explore

Assess code changes through structured investigation, dependency analysis, and impact assessment.

Updated May 9, 2026
One-click install
npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-explore-leandrobenjaminl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/LeandroBenjaminL/lend-ai/tree/main/skills/sdd-explore
Command: npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-explore-leandrobenjaminl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers and engineers avoid jumping to conclusions about code changes, by requiring a thorough understanding of the existing situation first.

Core Features & Use Cases

  • Problem Understanding: Provides a structured process for analyzing the code, its context, and potential impacts before suggesting a change.
  • Impact Assessment: Assesses potential changes on the system, including dependencies, risk, and potential issues.
  • Decision Support: Offers a menu for different levels of investigation (quick scan, impact analysis, complete investigation) to help decide the next steps.
  • Contextual Information: Allows users to check previous decisions and knowledge stored in Engram for informed decision-making.

Quick Start

Use the 'sdd-explore' skill to initiate a code investigation before deciding on a code change.

Frequently Asked Questions about sdd-explore

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

FAQPage Schema
How do I assess code change impact before modifying a system?

To investigate code before proposing changes, apply a structured process that includes context retrieval, dependency analysis, and impact assessment. This approach ensures informed decision-making and prevents jumping to conclusions about code modifications.

Why do a dependency analysis and risk assessment before proposing code changes?

Conducting dependency analysis and risk assessment before proposing changes prevents developers from jumping to conclusions. It provides a thorough understanding of the existing code context, identifying potential issues to enhance code quality and system stability.

What is the best way to structure a code investigation for decision support?

The best way to structure a code investigation for decision support is to use a tiered menu offering a quick scan, impact analysis, or complete investigation. This helps evaluate potential changes and decide the next steps effectively.

Can I use previous decisions to inform my current code investigation?

Yes, you can use previous decisions to inform your current code investigation by checking contextual information stored in Engram. This allows you to retrieve historical knowledge for better decision support and risk analysis.

Does this code investigation approach work for quick scans and complete assessments?

Yes, this code investigation approach works for both quick scans and complete assessments by offering a decision support menu. You can select the level of investigation needed, from a quick scan to a full impact analysis.