Prepare work with the product context already attached.
Create development tasks from analyzed requirements. Your team can use them directly and agents or connected systems can retrieve them through MCP.
A project's Work tab holds tasks that sit next to the repository they change. Each task names the parts of the product it touches and carries at least one line saying what must be true when it is done. Anyone with Write on the project can write one; only an Admin of the project can accept it; and an agent — your own or GitMir Cloud Compute — is handed only what was accepted. When you come from a compared document, the parts it landed on travel with the task.
Open a project and go to the Work tab
Write a task, or press "Write this down as work" on a compared document
Add at least one line for what must be true when it is finished
As an Admin of the project, accept the task so agents can see it
Let a person or an agent take it and report what actually changed
The lines you write for "what must be true when it's done" are read by people and agents — GitMir does not run them and does not check them for you. There is no link to Jira or Linear, which remain good places to run a team's process; GitMir's work lives on the project's board and is read out through MCP. Writing a task needs Write on the project, accepting one needs Admin of it, and someone who can only read can do neither.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.