> ## Documentation Index > Fetch the complete documentation index at: https://witness.nu/docs/llms.txt > Use this file to discover all available pages before exploring further. # Work from an agent > Hand your agent the project, a part of the queue, a link, or a card. Most of what happens in a project, an agent does. Here are the ways to hand it the work. ## Your own agent Your agent connects with your own sign-in, from one prompt you paste to it. If your team's project is not there yet, [set it up](/docs/quickstart); if it is, [join it](/docs/join). From then on it reads the project before its first write, and what it files because you told it carries your name. ## A part of the queue Every open status has a prompt: the text that hands an agent the cards in that status. Copy it from **Prompts** in the bar, which lists one row per status with how many cards it would hand over; from the button on a group in the list, such as **Investigate** or **Build**; or from **Copy prompt** on a card, for that card alone. Copying takes a member's sign-in or an edit link. The prompt names the project, never an address, so paste it to an agent that is already connected or already holds the project's link. The prompts come in two kinds. Where the call is a person's (Triage, Awaiting decision, Needs verification), the agent prepares each card, waits for your word, and records what you decided in your name. Where the call is the agent's (Investigating, Ready to build, Blocked), it does the work and moves the card itself. These are the prompts a new project starts with; when you copy one, `{project}` becomes the project's name and `{scope}` the cards you hand over: ```text theme={null} Read {project}. Then take {scope} with me, one at a time. For each card find out what it is: where it lives, whether it reproduces, which cards sound like it, and the labels and status you would give. Show me that in a few lines and wait. Then move the card as I decide, in my name, with the reason. ``` ```text theme={null} Read {project}. Then take {scope}, one at a time. Reproduce it where there is something to reproduce, work out the cause or settle the approach, and write the analysis on the card: what is going on, files, the route the change should take. Land it: Ready to build with the settled approach, Awaiting decision with the options when it is a product question, or Blocked with what it waits on. ``` ```text theme={null} Read {project}. Then take {scope} with me, one at a time. For each card lay out the options, what each costs and changes, and your recommendation, in a few lines. Wait for my decision. Then record it on the card in my name and move it on: Ready to build with the settled approach, or Parked or By design with the reason. ``` ```text theme={null} Read {project}, the working rules first. Then take {scope}. Small independent cards you may build in parallel; anything touching shared code or needing a judgement call, one at a time. Build it, run the checks, and have the change reviewed against the card's own steps before you report it. Report the change and wait for my go before committing; when it reaches where I test, set the card Needs verification, say where to run it and what to look at in its verification field, and release the claim. Stop and ask when the settled approach does not survive contact with the code. ``` ```text theme={null} Read {project}. Then take {scope}. For each card check whether what its reason names has cleared: the card, the environment, the missing information. Move the cleared ones back to the status the reason names and say what changed. Tell me which ones still wait, and on what. ``` ```text theme={null} Read {project}. Then take {scope} with me, one at a time. I verify; you prepare. For each card tell me where to go, what changed and where it shows, the steps from its How to test in the order I should take them, and what to watch for. Then wait for what I saw. If it worked, set Done with my name in verifiedBy; if not, record what I saw on the card and move it to Investigating, in my name. ``` A few more prompts are for moments that come round in any session rather than for a status. An agent that can write sees their titles in the project's document and fetches one by title when its moment comes; a prompt you hide is not listed. ```text theme={null} Before you start, plan who does what. Split the job into its parts and give each part a role: you, a subagent, a script, or me where the call is mine. Give each agent a model: the strongest for judgement and for parts that must fit together, a cheap one for a mechanical step or a check, and such an agent gets one step, never a list. A judgement that would take many pages to read goes to a fresh agent, so the pages stay out of this session. Show me the plan as a table of role, who, model and why, with what you need from me. Start nothing until I say go. ``` ```text theme={null} Before I take that as done, check it. List each claim you just made that something works, is fixed or is finished, and beside each the evidence: the test that ran, its output, the line of code. Have a fresh agent check them against the code. Tell me which hold, which you could not prove, and what I should look at myself. ``` ```text theme={null} Read {project}. What I just told you is a lesson for how work is done here, not only for this task. Post it as one correction line, in my words, and say if it repeats one already on the list. If the list shows it is ready to become a working rule, propose the rule to me and wait. ``` Every prompt is yours to reword, in **Settings → Prompts**. A project stores only the prompts it changed, so a better default still reaches a project that left it alone. ## A link An agent that can't connect over MCP, or that works for someone outside your team, works from a link. Make one in **Share**, one per person. Send it with the name of whoever the agent works for; not told, it asks once before its first write. What a link allows: [Who can do what →](/docs/concepts/access#guests-with-a-link). What the agent fetches from it: [For agents →](/docs/reference/agents#everyone-else-a-link) ## Run it from a card With [witness for Mac](/docs/mac), open a card and press **Start a session**. Your own Claude Code or Codex gets the card's prompt, works in its own copy of each repository on a branch of its own, and what it does comes back to the card. [Sessions →](/docs/concepts/sessions) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.