sdd-explore

Analyze codebases and openspec artifacts to synthesize implementation options and impacts.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dallay/opencode-docker --skill sdd-explore-dallay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/sdd/sdd-explore
Command: npx skills add https://github.com/dallay/opencode-docker --skill sdd-explore-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and agents quickly investigate feature ideas or ambiguous requests by reading the codebase and open specification artifacts, synthesizing findings, and returning a concise, structured analysis so decisions can be made without committing to changes.

Core Features & Use Cases

  • Focused codebase investigation: Read entry points, related modules, and tests to identify affected areas and constraints.
  • Option analysis and recommendation: Compare multiple approaches with pros, cons, and effort estimates to guide design choices.
  • Spec-aware persistence: Follow openspec conventions and optionally save exploration output to openspec/changes/{change-name}/exploration.md when tied to a named change.
  • Use Case: Triage a proposed feature by summarizing current state, listing affected files, proposing two implementation options, and recommending the best path forward.

Quick Start

Ask the agent to "Explore the proposed feature X by summarizing the current state, listing affected files, comparing approaches with pros and cons, giving a recommendation, and identifying risks."

Frequently Asked Questions about sdd-explore

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

FAQPage Schema
How do I analyze the codebase impact of a proposed feature?

To analyze codebase impacts, read relevant entry points, modules, and tests to identify affected areas and constraints. The workflow synthesizes findings into a structured analysis envelope, comparing implementation options with pros, cons, and effort estimates to guide design choices.

Can I save exploration results directly into openspec change directories?

Yes, exploration results can be optionally saved into openspec/changes/{change-name}/exploration.md. This spec-aware persistence follows openspec conventions when the analysis is tied to a named change, keeping investigation artifacts organized.

Do I need openspec artifacts to perform codebase impact analysis?

You need openspec artifacts like config.yaml and openspec/specs/ for context, alongside relevant source files and tests. The workflow reads these project specifications to synthesize findings and produce a structured analysis of implementation impacts.

How do I triage a proposed feature by comparing implementation approaches?

Triage a proposed feature by summarizing the current state, listing affected files, and comparing multiple approaches with pros, cons, and effort estimates. The workflow then recommends the best path forward and identifies risks to guide decisions.

What are the limitations of early-phase feature proposal analysis?

Early-phase feature proposal analysis investigates options and impacts without committing to changes. It relies on reading openspec/config.yaml, openspec/specs/, and source files to produce a structured analysis envelope, meaning it cannot modify code or guarantee implementation success.