Menu
Research existing solutions before writing custom code
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pre-meeting context gathering across all connected systems. Pulls recent interactions, open items, and suggested talking points for any person or topic. Triggers on: "meeting prep", "prep for my meeting", "meeting with X", "prep for 1:1".
Pulls a Granola meeting transcript and updates people files with per-person intelligence: what they said, what they pushed back on, what they committed to. Compounds over time — each meeting adds a layer. Triggers on: "sync people", "update people from meeting", "update stakeholders", "/people-sync".
Competitive analysis and market research with source attribution. Parallel fan-out across web, review sites, and news. Triggers on: "market research", "competitive analysis", "competitor comparison".
Voice profile configuration and application for consistent writing. Configure once with 2-3 samples, apply everywhere. Triggers on: "writing style", "voice profile", "apply my voice", writing long-form content.
Platform-optimized Substack Notes creation. 500-char limit, hook-driven, engagement-focused. Triggers on: "write a Substack Note", "Substack content", "Note ideas".
Test-driven development enforcement with RED-GREEN-IMPROVE cycle
| name | search-first |
| description | Research existing solutions before writing custom code |
| origin | pm-pilot |
| version | 1.0.0 |
| triggers | ["before implementing anything new","search first","find existing solution"] |
Mandatory research before writing any new code. Reuse beats reinvention.
# Search for existing implementations
gh search repos "{feature keywords}" --limit 5
gh search code "{function signature or pattern}" --limit 10
Look for:
Check the relevant registry:
npm search {keywords}pip index versions {package} or web searchcargo search {keywords}pkg.go.dev searchEvaluate packages on:
Output one of:
REUSE: {package/repo} - {why it fits}
ADAPT: {package/repo} - {what needs modification}
BUILD: No suitable existing solution - {why}
Search: {what was needed}
GitHub: 3 repos found, 1 strong match
- github.com/user/repo (2.1k stars, MIT, active)
Registry: 2 packages evaluated
- package-name (50k weekly downloads, v3.2.1)
Decision: REUSE package-name
Rationale: Covers all requirements, well-maintained, MIT license
Install: npm install package-name