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.
Install
npx skills add jeremybrasher/grokbot-skills --skill discoverygit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/discovery ~/.claude/skills/discoveryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 retention, SLA RPO/RTO) ### 4. What's the budget? - Monthly cost ceiling (LLM + infra) - Headcount: 1-person task vs cross-team effort - Calendar: "must ship by X" vs "best by Y" If unstated, default to "small project_size, 1-engineer-week, <$200/mo
Details
- Skill name
discovery- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/discovery/SKILL.md- Repo updated
- 15 September 2026
FAQ
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 the Discovery skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill discovery. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Discovery popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Pre Mortem
38jeremybrasher/grokbot-skills
Imagine the project has already shipped and failed catastrophically — work backwards from the failure to identify the most likely causes BEFORE building. Forces concrete risk identification, not vague "what could go wrong" lists.
Create Verification Skill
38jeremybrasher/grokbot-skills
Generate a project-local verification skill that drives your app the way a user does \u2014 any language, framework, or platform. Use for /create-verification-skill, \\"make a control skill for this repo\\", or when a project has no scripted way to prove UI/CLI/service behavior. Observe required inputs first; HOLD when they are missing rather than guessing.
Systematic Debugging
38jeremybrasher/grokbot-skills
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Observe the failure first. Do not use it to implement an already-approved design, to add a feature with no failing behavior, or to guess a root cause from a one-line complaint.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.