sdd-explore

Scan repository structure and scaffold exploration.md with selected context and handoff prompts.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/davidarce/devrune-starter-catalog --skill sdd-explore-davidarce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-explore
Source: https://github.com/davidarce/devrune-starter-catalog/tree/main/workflows/sdd/sdd-explore
Command: npx skills add https://github.com/davidarce/devrune-starter-catalog --skill sdd-explore-davidarce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface contextual codebase information to enable safe planning and handoff for an SDD change.

Core Features & Use Cases

  • Scaffold exploration.md from a template and incrementally enrich it with Selected Context, Architecture, and Selected Files Tree.
  • Generate a clear handoff prompt for the next planning phase, ensuring comprehensive context.
  • Provide optional Jira context when a ticket ID is provided to align requirements and acceptance criteria.

Quick Start

Run this skill with a change name to scaffold exploration.md and begin incremental discovery of the codebase.

Frequently Asked Questions about sdd-explore

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

FAQPage Schema
How do I gather codebase context for safe planning and handoff before making changes?

To gather codebase context for safe planning and handoff, this skill scans your repository structure, selects relevant files, and scaffolds an exploration.md with incremental updates to bound ambiguity for the next phase.

What is the best way to document codebase exploration for an SDD change?

The best way to document codebase exploration for an SDD change is to scaffold an exploration.md file, incrementally enriching it with Selected Context, Architecture, and a Selected Files Tree.

Can I integrate Jira ticket context into my codebase exploration and planning phase?

Yes, you can integrate Jira context into your codebase exploration by providing a Jira ticket ID, which aligns requirements and acceptance criteria within the generated exploration.md file.

How do I generate a handoff prompt for the next planning phase of a codebase change?

You generate a handoff prompt for the next planning phase by enforcing a strict handoff contract that ensures the next model receives complete, actionable context from the exploration.md file.

Do I need any specific dependencies to scaffold exploration.md for repository discovery?

No specific dependencies are required to scaffold exploration.md for repository discovery, as the skill operates independently to scan structure and surface contextual information.

Why does my codebase handoff prompt lack actionable context for the next model?

Your codebase handoff prompt lacks actionable context due to insufficient exploration bounding, which this skill resolves by enforcing a strict handoff contract and capturing Selected Context.