sdd-explore

Analyze codebase ideas and generate structured exploration artifacts.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill sdd-explore-jnzader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/JNZader/javi-ai/tree/main/delta/overrides/sdd-explore
Command: npx skills add https://github.com/JNZader/javi-ai --skill sdd-explore-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explore and investigate ideas before committing to a change to ensure well-informed decisions and risk-aware implementation plans.

Core Features & Use Cases

  • Orchestrator-triggered exploration: when asked to think through a feature, the agent analyzes the codebase, clarifies requirements, and surfaces risks.
  • Structured analysis: produces a concise, structured investigation that can be reviewed by engineers before coding.
  • Artifact generation: optionally persists exploration artifacts to support traceability and future reference.

Quick Start

Provide a topic or feature to explore along with optional project context to begin an analysis.

Frequently Asked Questions about sdd-explore

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

FAQPage Schema
How do I analyze a codebase before implementing feature changes?

Codebase exploration before committing to changes involves investigating ideas, clarifying requirements, and analyzing architecture to produce risk-aware implementation plans. This structured workflow loads project context and generates analysis artifacts for engineers to review.

What is the best way to document architecture decisions and requirement analysis?

Architecture decision documentation is produced through structured codebase exploration that generates concise analysis artifacts. These artifacts capture requirements, risks, and project context, optionally persisting results to support traceability and future reference.

How do I clarify requirements and surface risks for a new software feature?

Requirement clarification and risk surfacing happen through a structured exploration workflow that investigates the codebase and analyzes ideas before implementation. This produces a concise investigation document for engineers to review before committing to changes.

Can I persist codebase analysis artifacts for future reference and traceability?

Yes, you can persist codebase analysis artifacts using the built-in mem_save mechanism. This optional persistence within the exploration workflow ensures that structured investigation results support traceability and future reference across software projects.

When should I use a structured exploration workflow instead of directly coding changes?

A structured exploration workflow is needed when implementing complex features, making architecture decisions, or clarifying ambiguous requirements. It ensures well-informed decisions by analyzing the codebase and surfacing risks before committing to code changes.

Does codebase exploration work with orchestrator-driven tasks and automated workflows?

Yes, codebase exploration applies to orchestrator-driven tasks where an agent is triggered to think through a feature. The structured workflow integrates into automated software project workflows to analyze requirements and generate investigation artifacts.