Using a coding agent to audit projects for Jev integration points
A copyable prompt has a coding agent audit the whole workspace and, per project, find tasks Jev could take over such as organizing information, reviewing content or checking another agent's work, and define the inputs, references, question and output format.
here is how you audit your whole workspace and find what JEV could improve in each project (copy the prompt at the end and paste it into your coding agent) ask your agent to find where jev could help in each project look for tasks such as organizing information, reviewing content or checking another agent’s work your agent then identifies what jev needs to read and what question it should answer it also explains how your app would use the answer 1. find tasks jev could help with ask your agent to review your projects using the existing instructions, documentation, prompts and code have it find tasks that involve sorting information, reviewing content or checking another agent’s work (eval) for each task, have it explain how it works today and what jev could do 2. define what jev needs for each task, have your agent identify: > the information jev needs to read > the references it should check against > the specific question it should answer > the answer format: a choice, a score or a probability > what your app should do with the answer for a second brain, the references could include your topic descriptions, saved documents and rules for adding information ask your agent to flag missing references have it explain what happens if jev gives a wrong or uncertain answer 3. choose one task to test ask your agent to compare how often each task happens, the setup effort and the effect of a wrong answer include tasks that your existing code already handles well start with a repeated task where you have clear references and examples you have already reviewed those examples give you something to compare jev’s answers against 4. compare jev’s answers with your reviewed examples run jev on those examples and inspect where its answers differ from yours measure answer quality, response time and cost use the results to decide whether jev is useful before letting your app act on its answers COPY THIS PROMPT ---- " Audit the projects in this workspace to find tasks where JEV could improve. Keep the audit read-only. Do not change files or run integrations. Use the existing project instructions, documentation, prompts and relevant code. List any projects or files you cannot inspect. Find tasks that involve choosing between options, scoring something or evaluating whether something is true. For each task, explain: - The project and relevant file paths. - How the task works today. - Where JEV could help. - The information JEV needs to read. - The references it should check against. - One specific question it should answer. - The allowed choices, score scale or probability it should return. - What the app should do with the answer. - What happens if the answer is wrong or uncertain. Use a concrete example from the project where possible. Clearly label any example you invent. For projects that store knowledge, also consider search by meaning. Explain how the current setup finds relevant passages and keeps their source links. Identify where JEV could assess those passages or select useful source sentences. Adapt suggestions to the existing tools and project structure. Flag missing information and references. Do not assume a particular platform or search system. Include tasks that existing code already handles well. Identify projects where JEV has no clear use. Compare the candidates by usefulness, setup effort and ease of testing. Consider how often each task happens and the effect of a wrong answer. Mark unknown costs, usage frequency and performance as unknown. Recommend one task to test first using examples that have already been reviewed. Explain how to compare JEV's answer quality, response time and cost with the current process."
This post quotes another post: x.com/1455999313453195265/status/210105049420263…