discovery
Structured pre-design questioning to surface hidden constraints before any architecture decision is locked in. Forces the architect/auditor/reviewer to enumerate what they DON'T know before proposing.
npx skills add majiayu000/claude-skill-registry --skill discovery --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Discovery — surface hidden constraints first The biggest cause of bad agent output is missing context. Before locking in a decision, enumerate what you don't know and surface it. ## The 7 discovery dimensions For any non-trivial request, walk through these and record findings in the report's "Context" section: ### 1. Who depends on this? - What other services / teams consume the thing you're changing? - Are there public consumers (open API, OSS users)? - Is there a deprecation path if you break compatibility? Grep for: `grep -rE "import.*<your-module>|require.*<your-module>"` in the repo and any sibling repos you have access to. ### 2. What's the scale today, what's it in 6 months? - Current traffic: requests/sec, queries/sec, MB/day, daily-active-users - Storage: rows in main tables, size on disk - Cost: monthly LLM spend, infra spend - 6-month projection: linear? exponential? unknown? If unknown, write: "scale unknown — request from user before proceeding." ### 3. What MUST not change? - Existing API contracts (backward compatibility window) - Database schema columns referenced by reporting / BI - File formats consumed by other tools - Regulatory commitments (audit log retentio
- The 7 discovery dimensions
- 1. Who depends on this?
- 2. What's the scale today, what's it in 6 months?
- 3. What MUST not change?
- 4. What's the budget?
- 5. What's the failure mode that matters?
- 6. What's already been tried?
- 7. Who decides?
- Output
- When to skip
- Common gotchas
What does the discovery skill do?
Structured pre-design questioning to surface hidden constraints before any architecture decision is locked in. Forces the architect/auditor/reviewer to enumerate what they DON'T know before proposing.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill discovery --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.