sdd-explore

Analyze codebase state and produce structured recommendations with risks.

3|Updated Apr 5, 2023
One-click install
npx skills add https://github.com/mrp4sten/.dotfiles --skill sdd-explore-mrp4sten
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/mrp4sten/.dotfiles/tree/main/development/IA/opencode/skill/sdd-explore
Command: npx skills add https://github.com/mrp4sten/.dotfiles --skill sdd-explore-mrp4sten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams think through feature ideas before coding, ensuring alignment and reducing scope creep by providing structured exploration of a codebase or project context.

Core Features & Use Cases

  • Structured exploration: analyze current state, identify affected areas, and compare options.
  • Decision-ready outputs: provide clear recommendations, risks, and trade-offs for feature decisions.
  • Safe, non-destructive guidance: returns a comprehensive plan without modifying code or files.

Quick Start

Describe the feature you want explored to the orchestrator and receive a structured analysis.

Frequently Asked Questions about sdd-explore

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

FAQPage Schema
How do I explore feature ideas before committing to codebase changes?

To explore feature ideas before committing to codebase changes, you can describe the feature context to receive a structured analysis. This non-destructive guidance provides a comprehensive plan covering current state, affected areas, and approaches without modifying any files.

What is structured codebase investigation for requirement clarification?

Structured codebase investigation for requirement clarification is a process of analyzing project context to align teams before coding. It provides decision-ready outputs that compare options, assess risks, and identify affected areas to reduce scope creep.

How do I analyze risks and trade-offs for a new feature decision?

You can analyze risks and trade-offs for a new feature decision by describing the desired feature for structured exploration. The analysis generates decision-ready outputs detailing clear recommendations, potential risks, and comparative approaches for safe planning.

Can I investigate a codebase without modifying existing files?

Yes, you can investigate a codebase without modifying existing files. The exploration process provides safe, non-destructive guidance, returning a comprehensive plan that analyzes the current state and affected areas while keeping all code intact.

What's the best way to compare approaches for a feature development plan?

The best way to compare approaches for a feature development plan is to use structured exploration tailored to your project context. It evaluates the current state and affected areas to deliver clear recommendations and trade-offs for feature decisions.

When do I need structured exploration for a software engineering project?

You need structured exploration for a software engineering project when you must think through feature ideas before coding. It is essential for requirement clarification, codebase investigations, and ensuring alignment to prevent scope creep.