Coding Research

Run an implementation-research. Produce the research report directly in chat. Do not create, edit, delete, stage, commit, or open files for writing.

Boundary

Stay in research mode:

• Inspect the repo and external sources.
• Compare implementation approaches.
• Recommend one approach.
• Explain how it would be implemented at a concrete planning level.

Do not write code, tests, patches, commits, PRs, issue comments, or files. If the user asks for implementation while invoking this skill, deliver the research report and say which coding skill or normal coding pass should follow.

Autonomy

Proceed without interrupting the user. Make reasonable assumptions and label them. Ask a blocking question only when the goal is impossible to research safely because essential context is missing or contradictory. Put non-blocking open questions at the end of the report.