sdd-explore

Explore codebases to clarify requirements and guide feature decisions.

10|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Alan-TheGentleman/gentle-ai-enterprise --skill sdd-explore-alan-thegentleman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/Alan-TheGentleman/gentle-ai-enterprise/tree/main/skills/sdd-explore
Command: npx skills add https://github.com/Alan-TheGentleman/gentle-ai-enterprise --skill sdd-explore-alan-thegentleman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically organize and perform structured exploratory analysis of a codebase when prompted by an orchestrator, enabling informed decisions before implementing changes.

Core Features & Use Cases

  • Investigate entry points and key files
  • Compare approaches and assess trade-offs
  • Archive exploration results for future reference

Quick Start

Provide a topic and context to begin a structured exploration of a codebase.

Frequently Asked Questions about sdd-explore

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

FAQPage Schema
How do I explore a codebase to clarify requirements before implementing changes?

Codebase exploration clarifies requirements by investigating entry points, comparing approaches, and archiving structured analysis results to guide feature decisions before committing to a change.

What is the best way to review software architecture when the project context is incomplete?

Architecture reviews for incomplete contexts use structured analysis templates to investigate key files and assess trade-offs, ensuring informed decisions when project requirements are evolving.

Can I use structured exploration workflows for evolving requirement analysis?

Yes, deterministic workflows support requirement clarification across codebases by applying structured analysis templates to evolving contexts, ensuring consistent feature exploration and decision tracking.

How do exploration persistence contracts work with engram or openspec modes?

Persistence contracts via engram or openspec modes archive exploration results for future reference, ensuring structured analysis outputs remain accessible when clarifying requirements or guiding feature decisions.

Do I need to provide specific context to start a structured codebase analysis?

Yes, you must provide a topic and relevant context to begin a structured exploration, allowing the analysis to investigate entry points, compare approaches, and archive results effectively.

Why perform feature exploration before committing to architecture changes?

Feature exploration before architecture changes prevents costly rework by comparing approaches and assessing trade-offs, ensuring that feature decisions align with actual codebase requirements and constraints.