sdd-explore

Explore codebase ideas and requirements to clarify design directions before implementation.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-explore-tiagofur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/tiagofur/kakoclaw/tree/main/.claude/skills/sdd-explore
Command: npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-explore-tiagofur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and clarify design directions by exploring ideas before committing to changes in a codebase.

Core Features & Use Cases

  • Exploration & analysis: read context, compare approaches, and document tradeoffs.
  • Requirements alignment: validate requirements with architectural considerations and risks.
  • Persistence and handoff: produce structured exploration reports and, if linked to a specific change, save to openspec.

Quick Start

Ask the sub-agent to start a structured exploration of the current feature or change request.

Frequently Asked Questions about sdd-explore

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

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

To explore codebase ideas before changes, you systematically investigate requirements and compare design approaches to clarify architectural directions. This involves reading context, analyzing tradeoffs, and validating risks prior to implementation.

What is the best way to clarify requirements for a software refactor?

Clarifying requirements for a software refactor involves validating the requirements against architectural considerations and analyzing design options. This structured exploration ensures the chosen refactor direction aligns with project goals and identifies potential risks before implementation.

How do I analyze design tradeoffs when planning a new feature?

To analyze design tradeoffs when planning a new feature, you read the existing codebase context and compare different implementation approaches. This structured exploration documents the benefits and drawbacks of each option to guide the final design direction.

Can I save structured exploration findings for a codebase change?

Yes, you can save structured exploration findings by linking them to a named change. When a specific change is provided during the exploration, the findings are persisted in openspec to ensure structured handoff and continuous tracking of design decisions.

Does this codebase exploration approach work for internal and open-source projects?

Yes, this codebase exploration approach works across software projects, including both open-source and internal codebases. It systematically coordinates exploration steps to analyze options and clarify design directions regardless of the project's deployment context.