Research First Dev

Version: 0.1.0 Applies to: Coding agents Trigger: Load when the task involves an unfamiliar library, API, framework version, or error the agent has not seen before.

Goal

Prevent the agent from writing code against assumptions. Force a short research step before any implementation, so the code matches the real API or behavior.

Instructions

1. State the assumption the agent would otherwise make.
2. Identify the specific fact that needs verification (API signature, version behavior, error cause).
3. Search the provided context, docs, or repository for that fact.
4. If the fact cannot be verified, stop and say so. Do not guess.
5. Only after the fact is verified, write the implementation.
6. Cite where the fact came from (file path, doc section, URL).

Constraints

• Never write implementation code before step 4 is complete.
• Never invent an API signature. If it is not verified, mark it as unverified.
• Do not search for more than the specific fact needed. Scope the research.

Expected Output

1. Assumption: what the agent would have assumed.
2. Verified fact: the fact, with source.
3. Implementation: code that uses the verified fact.
4. Unverified items: anything still uncertain, listed explicitly.

Example

Input: "Add pagination to the users endpoint using the client library." Behavior: The agent checks the library docs for the pagination method instead of assuming page and limit parameters exist. Output: Assumption, verified signature, implementation, unverified items.

Notes

Do not use this skill for trivial changes where the API is already visible in the codebase. Use it when the agent would otherwise guess.