Explore proposed features and code areas before committing changes.
npx skills add https://github.com/sebasmzg/sebas.dot --skill sdd-explore-sebasmzg
Please help me install this Agent Skill. Skill: sdd-explore Source: https://github.com/sebasmzg/sebas.dot/tree/main/.config/opencode/skills/sdd-explore Command: npx skills add https://github.com/sebasmzg/sebas.dot --skill sdd-explore-sebasmzg
This Skill helps teams and orchestrators investigate proposed features, design options, and code changes before committing to implementation by producing concise, structured exploration and impact analysis.
Ask the skill to explore a topic, specify the artifact mode (engram | openspec | hybrid | none), and include an optional change name to save the exploration.
High-intent search queries and answers about installing and using this skill.
You can explore and analyze proposed features by reading entry points, related files, and tests to identify affected areas and dependencies. This pre-change analysis produces a structured exploration report to help your team decide on the next steps.
Approach comparison lays out multiple implementation options with pros, cons, and estimated effort. This helps teams evaluate architecture design choices and decide on the best refactoring path before committing to implementation.
To save exploration artifacts, specify the artifact mode (engram, openspec, hybrid, or none) and include an optional change name. The skill follows the persistence contract to save exploration.md or mem_save artifacts according to the chosen convention.
Yes, you can analyze ambiguous requirements by triggering a pre-change analysis through an orchestrator. The skill loads available project context, investigates the codebase, and produces a structured exploration report to clarify design choices before committing changes.
No, existing engram or openspec project context is not strictly required. The skill loads project context when available but can still investigate proposed features and code areas independently to produce a structured exploration report.
You should avoid pre-change analysis for trivial code fixes where the impact is obvious and no design comparison is needed. It is designed for architecture investigations, complex refactors, and ambiguous requirements where evaluating implementation options and codebase impact is necessary.
RamonsDkaAnalyze codebases to explore design options and risks before implementation.
Sridhar-RanganaboinaGenerate 2-4 design options with pros, cons, complexity, and risk.
Alan-TheGentlemanTranslate change tasks into code following specs and design.
baekenoughTriage CVE reports to assess impact, reproduction feasibility, and remediation options.
