discovery

Original：🇺🇸 English

Translated

Use for deep design discovery and problem understanding before planning or implementation. Trigger when the user wants to think deeply, build knowledge, surface edge-cases, ask many questions, or explore the problem space without producing plans or code.

2installs

Sourcetstelzer/skills

Added on2026-02-24

NPX Install

npx skill4agent add tstelzer/skills discovery

SKILL.md Content

View Translation Comparison →

Discovery

Overview

Let's get on the same page about the problem before we jump into plans or code. This is where we slow down, ask good questions, and poke at edge cases so we don't miss anything important.

Ask a small batch of questions up front to cut the back-and-forth, min 3, max 7, so it stays answerable. Prioritize questions based on importance. Start high-level, go deeper when necessary

Possible Themes (no need to be exhaustive, pick whichever make sense):

Goal/outcome (what success looks like)
Audience/user and context
Constraints (time, budget, tech, tone, scope)
Current state (what exists today, what to avoid)
Known pain points and failure modes
Key assumptions and unknowns

Call out edge cases, abuse cases, and fuzzy scenarios. Point out places where the requirements feel squishy or underspecified.

Interaction Notes

Embrace depth.
Do not create plans, roadmaps, or implementation details.
If the user asks for a plan or code, pause and confirm whether to switch out of design discovery.