skills.rest
Strocs
StrocsCOMMUNITY
Explore all skills by this author →
Website𝕏@_StrocsGitHub

sdd-explore

Analyze feature ideas and codebase contexts to produce structured design analysis.

Updated Nov 19, 2024
Search Tags:#architecture#codebase#sdd#explore#decision-support#technical-analysis
One-click install
npx skills add https://github.com/Strocs/.dotfiles --skill sdd-explore-strocs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/Strocs/.dotfiles/tree/main/.config/opencode/skills/sdd-explore
Command: npx skills add https://github.com/Strocs/.dotfiles --skill sdd-explore-strocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers and architects investigate feature ideas, codebase impact, and ambiguous requirements before committing to changes, producing a concise, actionable analysis for decision-making.

Core Features & Use Cases

  • Structured Exploration: Read code and project context, summarize current state, and identify affected areas and dependencies.
  • Options Analysis: Compare alternative approaches with pros, cons, and estimated effort.
  • Artifact Integration: Optionally persist findings as exploration.md following engram or openspec conventions when tied to a named change.
  • Use Case: When asked to evaluate a proposed feature or refactor, produce a short report that lists current behavior, files impacted, possible approaches, recommendation, and risks.

Quick Start

Explore the requested topic and return a concise structured analysis with Current State, Affected Areas, Approaches, Recommendation, Risks, and Ready for Proposal status.

Frequently Asked Questions about sdd-explore

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

FAQPage Schema
How do I analyze codebase impact before implementing a new feature?▼

Codebase impact analysis involves investigating project context, summarizing current behavior, and identifying affected files and dependencies to produce a concise structured report for decision-making before implementation.

What is the best way to compare technical approaches for a software refactor?▼

Comparing technical approaches for a refactor requires evaluating alternative options with pros, cons, and estimated effort. This structured analysis yields a recommendation and risk assessment to guide your implementation choice.

How do I document architectural decisions for ambiguous requirements?▼

Documenting architectural decisions for ambiguous requirements involves exploring the codebase context and persisting findings as an exploration.md file following engram or openspec conventions, capturing current state, approaches, and risks.

Can I use structured exploration for bug fix analysis in an existing codebase?▼

Yes, structured exploration supports bug fix analysis by investigating the codebase context, summarizing current behavior, identifying affected areas, and producing a concise report with recommendations and risks to guide the fix.

What should be included in a technical analysis report for a proposed feature?▼

A technical analysis report for a proposed feature should include current state, affected files and dependencies, approach comparisons with pros and cons, a recommendation, risks, and a ready-for-proposal status indicator.

Related Skills

Explore More Software Engineering Skills→
workinprogress-aiworkinprogress-ai

devenv-chat-with-code

Explain codebase architecture with cited references to files and line numbers.

Official
Advanced
JNZaderJNZader

sdd-tasks

Generate phase-based tasks.md from change proposals, specs, and designs.

Community
Intermediate
ScottRBKScottRBK
28

serena-code-architecture

Analyze code architecture and map dependencies into knowledge graphs.

Community
Advanced
orekyuuorekyuu

sdd-spec

Guide code investigation, requirement elicitation, and specification document creation.

Community
Advanced