sdd-explore

Explore codebases and generate formal analysis reports before code changes.

Updated Feb 1, 2026

Search Tags:#workflow #architecture #codebase #requirements #analysis #persistence #exploration

Ready to run

npx skills add https://github.com/adacosdev/dotfiles --skill sdd-explore-adacosdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/adacosdev/dotfiles/tree/main/dot_config/opencode/skills/sdd-explore
Command: npx skills add https://github.com/adacosdev/dotfiles --skill sdd-explore-adacosdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide focused, structured exploration of ideas before committing to changes, helping teams think through requirements, alternatives, and impacts.

Core Features & Use Cases

Investigate codebases, think through problems, compare approaches, and return a structured analysis.
Persist exploration artifacts according to mode (engram | openspec | hybrid | none) with optional named changes to enable upserts and history.
Load project context and existing specs before starting, and generate a formal exploration report for decision-making.

Quick Start

Tell me the feature to explore and any context, and I will start a structured exploration.

Frequently Asked Questions about sdd-explore

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

FAQPage Schema

How do I analyze a codebase before starting feature development?▼

Codebase analysis before feature development involves investigating requirements, exploring existing architecture, and comparing approaches. This exploration process loads project context to return a formal analysis report for confident decision-making.

What is structured exploration in software architecture?▼

Structured exploration in software architecture is the process of clarifying feature ideas and assessing impacts before committing to code changes. It investigates requirements and compares alternatives to produce a formal decision-making report.

How do I clarify feature requirements before writing code?▼

Feature requirement clarification before coding involves thinking through problems and loading existing project context. You provide the feature idea and context to start a structured exploration that evaluates alternatives and impacts.

Can I persist exploration artifacts for codebase analysis history?▼

Yes, exploration artifacts can be persisted for codebase analysis using optional modes like Engram, OpenSpec, Hybrid, or none. Named changes enable upserts and maintain history across multiple structured explorations.

Does codebase exploration work without external dependencies?▼

Codebase exploration operates without external dependencies, requiring only your feature idea and project context. It loads existing specs internally and applies architectural assessment across projects to return a formal analysis report.

What's the best way to compare architectural approaches for a new feature?▼

Comparing architectural approaches for a new feature is best handled by structured exploration, which assesses impacts across the codebase and evaluates alternatives. It generates a formal analysis report to support confident decision-making.