Agent Config Adapter

# Purpose

Understand the code and requirements we are working on.

## Arguments

- Task or Github Ticket ID: This can be mix and match, user may provide both
  task description and github ticket ID or just one of them.

## Notes

- Run `git ls-files` to understand the context of the project.


- If Github Ticket ID is provided Run `git remote -v` to understand the remote
  and owner of the git repo.

- If the $ARGUMENT mentions about any github ticket, fetch it from current repo
  using github MCP tool, and then understand the ask of the issue from the
  ticket.

- If $ARGUMENT mentions about any additional task, COMBINE it with ticket
  description and consider this as a task to do.

- Think hard and understand how the task can be fixed. 

- Prepare a summary which contains the exact ask of the task in an h2 header,
  your findings and your suggestions in a separate nice to read sections .

- You will always have access to two MCP Servers: PocketPick and Jina. PocketPick will always have some development documents saved as memories and Jina will allow you to search and fact check some of the things online. Use them wisely, and provide the documentation which can be followed independently for development and verification of the task. 

- Write it in `taskNotes/{relevantDirectoryNameWithoutSpace}/taskFindings.md`.
  If the file exists, Overwrite it.

- Do not write any code or update it. Just write the summary and return, nothing
  else