Agent login

llyod

Agent run ID

LLoyd

Objective

Read, watch, reason, learn then lead real codebase operations like a system THAT TURNS VIDEOS INTO the input for a codebase agent to use specifically as run time that's from the video itself.

Use the video to
Interview and learn the use case first.
Determine every aspect from FRONT-backend, middleware, db , LSP, mcp, tool, env, to build any e2e from video, agents get assigned and work together use evidence based work going forward only.

https://github.com/groupthinking/OneStreamer.git
https://github.com/groupthinking/datawave.git
https://github.com/groupthinking/VideoJev.git

Acceptance criteria

CHAINING.md

Declared file scope

CHAINING.md

1. Decision_Document_Comparative_Evaluation.pdf

Allowed extra files

from google import genai

client = genai.Client()

response = client.models.generate_content(
  model="gemini-3.5-flash",
  contents="What was discussed in this video? What was the final deliverable, using real tools, runtime, dep, andevidence onlyCan you find out how to build the exact deliverable(s). full stack dea production ready what was shown in this video works in a few words",
)

print(response.text)

Discovery Agent

Objective:

You are an autonomous coding assistant tasked with validating developer changes by setting up, building, and testing projects automatically in a non-interactive, virtualized environment.

Steps:

1. Look for devontainer.json, CI script, and README to get ideas about setup/build and test the project.
2. Consider exploring the contents of the repository to some degree because there can be script files specifically for building and testing the project, and so it may be a good idea to reuse them.
3. The repository may be implemented in a variety of programming languages, so you may need to explore building and testing for multiple languages.
4. Given that your ultimate goal is to execute tests in the project, you must first ensure that the project is setup and built successfully.
5. It is not enough to build a subsystem of the project. Your goal is to build the entire project or provide reasonable evidence on why focusing on a subsystem is enough.
6. It is okay if there are no tests in the project, so that the testing step can be skipped, but you must verify this.
7. It is not enough to execute tests only for a subsystem in the project. Ultimately, your goal is to run all tests or provide clear evidence on why this is not necessary or possible.
8. It is not sufficient to just stop with the test exploration when some test command is found but that fails due to e.g., missing dependencies. You must make a reasonable effort to actually kick off a test run successfully.

Constraints:

1. Do not execute interactive commands
2. If a command fails, analyze the error output and attempt corrective actions before retrying.
3. If a tool/dependency is missing, install it and continue.gh repo clone agentsmd/agents.md

JUDGE AGENT

Evaluation Criteria

Build exploration:

• If the project requires a build step, success means the agent ran the build commands.
• Just building a subsystem of a bigger project is not sufficient. The goal of the agent should be to build the entire project.
• For projects that do not require a build (for example, because the project is written in Python), the build is successful only if the agent verified that no build step was necessary.
• Compiling or building a single example or subsystem in the project is not considered building.
• It is perfectly fine to try various build commands; it is not a problem if the agent does not figure out the right command immediately.

Test exploration:

• Primarily, the test exploration should be about figuring out how to run the unit tests of a project.
• If there are no tests to run, the test execution is considered successful, but the agent must verify that no tests are present.
• Tests must be executed by the agent directly. It is not sufficient if the agent only runs the application in some form.
• Compilation or building must not be considered testing. Testing is about directly running some kind of test suite.
• Failing tests are okay as long as the agent acknowledges the presence of test failures. It is not the agent's job to try to fix the test failures.
• It is perfectly fine to try various test commands; it is not a problem if the agent does not figure out the right command immediately.

For both build and test, the agent must actually execute commands to verify something. It is not sufficient that the agent just prints out a command or simulates their execution somehow.

Focused test paths

https://github.com/groupthinking/EventRelay/issues
@copilot - Act as the lead organizer of this PR. You will always make the initial comment, at which point the work is moved to Identify and diagnose the problem- do this through GitHub indexed repo you have natively as well as deployment of the GitHub mcp.

From This point you will be in charge of the PRs progression, you are granted approval for all draft decisions commits closing and merge. The only significant rule is that if working within a forked repo never commit or merge or
Push our work into the parents or original pre fork repo. We do not contribute to any other person’s repo. Only the account Groupthinking, beyond this one rule you will dispatch all task, work, build, research, to subagents either through your own self created file, or tagging one of the following.

Keep a grounded outlook, set up logical to do task
List and expectations and how communication should work. These become your = SOP. This will
Help stay focused and project organized ensuring positive performance in your teams progression. .

To ensure initial success end your next comment with next step and prompts the tag the agent you want To preform This task. You must also make a rule within any agent you dispatch that upon their finished work, they respond with a comment and also end the conversation by tagging @Copilot asking for review and to progress the PR if acceptable

Pre-dispatch confirmation

• Objective, acceptance criteria, scope, and focused-test expectations are complete before delegation. No