research-driven-development

Investigates codebases and external sources to ground implementation decisions in cited evidence.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/lunarmoon26/agent-skills --skill research-driven-development-lunarmoon26
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-driven-development
Source: https://github.com/lunarmoon26/agent-skills/tree/main/skills/research-driven-development
Command: npx skills add https://github.com/lunarmoon26/agent-skills --skill research-driven-development-lunarmoon26

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineering decisions often rely on guesswork, popularity signals, or surface-level documentation. This Skill enforces an evidence standard for technical research: it traces how systems actually work in source code and tests, compares alternatives against local constraints, and produces a recommendation with labeled confidence levels. ## Core Features & Use Cases - Scoped research depths: Choose Quick, Standard, or Deep investigation based on risk, avoiding unnecessary landscape surveys. - Source deep dives: Trace entry points, state flow, failure paths, and tests in local or external repositories using the deep-dive rubric in references/deep-dive-guide.md. - Evidence discipline: Label claims as direct evidence, inference, or unknown, with file and line citations pinned to commits or tags. - Use Case: When choosing between Temporal, Inngest, and Trigger.dev for durable workflow execution, the Skill first inspects your existing job state and tests, then drills into each candidate's persistence and retry mechanisms, and returns an adopt/adapt/experiment/reject recommendation with remaining validation steps. ## Quick Start Ask the agent to compare how two open-source libraries implement a mechanism you need and recommend which approach to adopt for your project.

Frequently Asked Questions about research-driven-development

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

FAQPage Schema
How do I compare open-source implementations before choosing a library?▼

Frame the decision criteria from your local project first, then select a few high-signal sources and trace their entry points, state flow, failure handling, and tests. Finish with an adopt, adapt, experiment, or reject recommendation tied to your constraints rather than a feature checklist.

How to research an unfamiliar codebase before making changes?▼

Start from the public entry point and follow the shortest path through dispatch, core abstractions, state ownership, side effects, and error handling. Record file and line anchors for each claim and stop once the mechanism and its failure boundaries are directly evidenced.

When should I not use a deep research workflow?▼

Skip it for routine code navigation, simple documentation lookups, or architecture writing that needs no source research. A quick primary-documentation check answers questions like a current CLI command without multi-source comparison.

What evidence standard should technical research meet?▼

Label important claims as direct evidence, inference, or unknown, and cite exact repository files with line ranges plus a commit or tag when versions matter. Treat documentation as intended contract and source or tests as evidence of actual behavior.

Can repository stars or README quality indicate production readiness?▼

No. Popularity, polished READMEs, and one successful happy-path test are not evidence of production quality. Inspect tests, failure paths, maintenance activity, and hidden assumptions instead, and include negative evidence in the evaluation.