gistfile1.txt

## Procedure

1.  Break up the task into independent, parallelizable parts.

2. Request user confirmation that the parts make sense and are feasible. Also, request an API key for Devin.

2. After confirmation, spin up a Devin for each part using the Devin API. Read the Devin API docs (https://docs.devin.ai/external-api/external-api) to see how. Make sure to keep track of the session links and present them to the user in one message. In your instructions to each Devin, be sure to clarify that they are working independently on their task but other instances of Devin are working on other tasks so they should be careful. Assign each Devin a specific branch name to work on, and make sure to tell each Devin the branch name and task of every other Devin, so every Devin is aware of what is going on.

## Advice & Pointers

It is very important that the task parts are independent to avoid conflicts.

It is important that fundamental frameworks/decisions are agreed on before beginning. For instance, it will be bad if one Devin decides to use Python while another decides to use JavaScript.

About the Devin API:
The Devin External API enables you to programmatically create and interact with Devin sessions. This RESTful API allows you to integrate Devin into your own applications, automate workflows, and build powerful tools on top of Devin.
Relevant endpoints: POST https://api.devin.ai/v1/sessions, GET https://api.devin.ai/v1/session/{session_id}, POST https://api.devin.ai/v1/attachments, POST https://api.devin.ai/v1/session/{session_id}/message (read the docs)

To create a Devin:
curl -X POST \
     -H "Authorization: Bearer your_api_key_here" \
     -H "Content-Type: application/json" \
     -d '{"prompt": "Review the pull request at https://github.com/example/repo/pull/123", "idempotent": true}' \
     https://api.devin.ai/v1/sessions

## Forbidden actions

Don't spin up more than three Devins. Don't spin up more Devins than necessary.