shunk031-research-before-implementation
About shunk031-research-before-implementation
shunk031-research-before-implementation is a research skill for development tasks that need external evidence. It guides users to consult official sources, inspect GitHub implementations, reconcile differences, then implement and verify based on the findings.
Key features
- 01Assess whether research is needed
- 02Consult official sources first
- 03Inspect GitHub implementations and configuration
- 04Reconcile documented and implemented behavior
- 05Implement and verify from evidence
Use cases
- 01Confirm API behavior that affects a design
- 02Check version or platform differences
- 03Gather evidence before choosing an implementation
- 04Record sources that informed a decision
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/shunk031-research-before-implementationin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlevals/evals.json
Details
From the project READMENote
After reading this
SKILL.md, say:🔎 I read shunk031-research-before-implementation.
Research before implementation
Use this skill when local files or stable knowledge cannot establish behavior that matters to the task. Skip the research workflow for self-contained edits and routine wording fixes unless the user asks for research.
- Follow explicit research routing in applicable environment guidance, then check current official documentation, specifications, release notes, or recommended approaches through an available web-research capability. Read the relevant source content, not only a URL or search-result title. Use a relevant non-GitHub source when one exists. Read a paper when its reported behavior is the thing being measured.
- Inspect representative implementation code or configuration on GitHub after the official sources. Read installed documentation and source only for the APIs, defaults, or entrypoints the task will use.
- Compare the documented behavior with the implementation. Resolve version, platform, maintenance, and activation differences before choosing the design.
- Implement and verify the change from that evidence. Scale the depth of research and verification to the risk and number of affected callers.
- Report the sources that changed the decision. Link at least one official non-GitHub source and one direct implementation or configuration file when both were consulted.
Research retry
If the research capability exits before producing sources because of a transient connection error, an HTTP 5xx response, or a stream disconnect, retry that stage at most 3 total attempts. A provider restriction or denied tool, including a 403, is stable: do not retry it, change credentials, or bypass the restriction. If the host exposes another permitted retrieval path, use that path; a research subprocess is permitted only when explicitly configured by the applicable environment guidance. Do not substitute memory. Accept an attempt only after reading the source content and recording its direct URL; do not rerun for format, length, or wording reasons, and do not rerun when the answer states that the documentation does not specify something. If no permitted research path succeeds, stop and report BLOCKED with the exact question and the failed paths.