In this chapter
Everyone may have their own preferences. What matters is that agents read the same project rules and that the team can check their work. Our team workshop includes Cursor and Claude; Codex is another option.
Connect the task, knowledge, and code
Open the project in the account used by the company. Point the agent to one Jira task, the appropriate Confluence page, repository, and playbook. In Codex, project rules can be in AGENTS.md; in another tool, point to its instructions. This is not about a list of installed extensions. Check that the agent can read the needed materials.
Ask it to connect these sources for your task:
| Source | What the agent must extract from it |
|---|---|
| Jira task | What the user wants to do, why they need it, and how you will accept the result. |
| Confluence documentation | Operating rules for the changed feature, exceptions, and the person who can explain gaps. |
| Code and tests of the selected version | Files responsible for the changed feature and existing checks; specific paths after reading. |
| Playbook | Who leads the change, who checks it, and how you show the demo. |
The agent did not open a page? Have it say what it could not read. Supply a fragment permitted to that tool or ask an administrator for the right access. Do not replace a missing rule with an assumption and do not use someone else’s account.
If you use Codex, use the tool setup in One Man Army. It includes instructions, skills — ready ways to perform tasks — and browser-work extensions. Adapt them to company rules; a personal configuration does not grant access to team systems.
Keep documents where they already work
Follow a simple order: conversation → agreement → appropriate document → check. The agent adds an accepted agreement to the existing plan or documentation. You do not need to copy Confluence into new files simply because you started using AI. In the next step, you will prepare and complete system documentation.
For a new repository, you can use the files and prompt from the project-preparation lesson. In a working system, compare them first with what you already have. A starter must not replace your rules.
Read task [Jira link], rule [Confluence page], playbook [link], and project code [repository, version]. For now, read only. In one table show: user need, acceptance criteria, rule and exceptions, and corresponding places in code and tests. For every entry give the source and version you read; if access is missing, say exactly what remained unread. Do not invent paths or document content. Identify one thing we can safely check in a local preview. Do not install extensions or change accounts and permissions.
Result: another person and their agent find the same agreements. Depending on the project, the toolset may also include Google Cloud, Tailscale, Terraform, Vault, Keycloak, and domains in GoDaddy. Not every task needs all of them.