skills.rest
nico0695
nico0695COMMUNITY
Explore all skills by this author →
GitHub

sdd-explore

Inspects repository context and writes an explore.md discovery artifact for spec-driven development.

Updated Apr 2, 2026
Search Tags:#spec-driven development#codebase exploration#risk analysis#repository inspection#change planning#discovery phase
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill sdd-explore-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-v2/skills/sdd-explore
Command: npx skills add https://github.com/nico0695/ai-tools --skill sdd-explore-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a change without understanding the existing codebase leads to flawed proposals and wasted rework. This Skill performs the discovery phase of spec-driven development by grounding an initial request in observed repository reality before any design decisions are made. ## Core Features & Use Cases - Targeted Repository Inspection: Reads project maps, config files, and high-signal source files to identify the affected area, constraints, and blast radius of a requested change. - Structured Discovery Artifact: Writes a concise explore.md capturing the request summary, current-state observations, risks, open questions, and a recommended objective and mode for downstream phases. - Use Case: A developer asks to add caching to an API layer. The Skill inspects the relevant modules, notes existing middleware constraints and test coverage, flags risks, and produces an explore.md that the proposal phase can build on directly. ## Quick Start Explore the repository impact of adding rate limiting to the API and write the findings to explore.md.

Frequently Asked Questions about sdd-explore

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

FAQPage Schema
How do I explore a codebase before planning a change?▼

Start with existing project maps and configuration, then read only the files directly related to the request. Capture the affected area, constraints, risks, and open questions in a structured explore.md artifact rather than scanning the whole repository.

What is the discovery phase in spec-driven development?▼

The discovery phase turns an initial request into grounded understanding of the affected area, current constraints, blast radius, and early risks. It observes project reality without choosing implementation approaches or writing tasks.

What should an exploration artifact contain?▼

An exploration artifact should include the request summary, recommended objective and mode, the affected area, current-state observations, constraints, initial risks, and open questions. It should distinguish facts, inferences, and unknowns with concrete file references.

When should exploration be marked as blocked or partial?▼

Use partial when the affected area is usable but important unknowns remain. Use blocked when the request cannot be mapped to a meaningful area without a user decision or missing context checkpoint.

What are the limitations of a scoped repository exploration?▼

Scoped exploration intentionally avoids scanning the whole repository, so it may miss distant coupling not surfaced by the project map. It also does not design solutions, so downstream phases must still validate feasibility.

Related Skills

Explore More Software Engineering Skills→
evolution-foundationevolution-foundation
520

dev-deepinit

Generate hierarchical CLAUDE.md and AGENTS.md context documents for codebases.

Official
Intermediate
mrp4stenmrp4sten
3

sdd-propose

Generate openspec change proposals with Intent, Scope, Approach, and Risks.

Community
Intermediate
DinxeshhDinxeshh

Atlas

Analyze system dependencies to expose god classes and circular references.

Community
Advanced
fusebase-devfusebase-dev
6

lightweight-lane

Classify small code changes and run a streamlined build-verify-deploy workflow.

Official
Advanced