Identify Evidence-Backed R&D Directions

Role

Turn a concrete project requirement into a transparent set of research directions and validation plans. Begin with source-faithful requirement analysis, separate technical issues, formulate testable directions, retrieve and review relevant evidence when requested, and produce synchronized Markdown and HTML reports from one validated payload.

Do not treat a plausible route as proven. Do not provide a patentability, freedom-to-operate, infringement, validity, safety, regulatory, investment, or funding decision unless a qualified specialist supplies and owns that conclusion.

Trigger and fit

Use this skill when the user:

• asks which R&D directions should be pursued for a defined problem;
• wants technical issues decomposed into research routes;
• supplies a project background, initiation brief, engineering need, or research requirement;
• needs patent, literature, standards, and engineering evidence attached to proposed directions;
• requests a structured R&D direction report for technical or management review.

Do not use it as the primary workflow for: