Project setup

A project holds one engagement: its tasks, the systems and files involved, the playbooks in use and the artifacts produced. Sessions started inside a project prioritize that context, so the agent does not need to be told which client you mean.

Create a project

There are two ways to create one from Projects:

• New project creates an empty project immediately. Use it when you already have a plan.
• Create project (top right) starts an agent session that plans the engagement with you.

To plan with the agent, describe the engagement: the client, the source and target systems, the scope and the target go-live date. Attach the statement of work and any kickoff notes. The agent drafts tasks with descriptions, dependencies and rough timelines. Review them, adjust, and ask the agent to save the project.

For example:

Plan the migration of Contoso from Dynamics GP to Sage Intacct. Scope: GL, customers,
vendors, open AR and AP, and 24 months of GL history. Go-live is 1 December.
Use the kickoff notes from last Tuesday's Circleback meeting.

i

A planning request does not start execution. The agent creates the project and tasks, and nothing is written to a client system until you ask for it and approve it.

Work with tasks

The project page has a Tasks tab with Board and Table views, and a Resources tab.

Each task has a status (Not started, In progress, Waiting or Done), an optional due date and assignee, and a description. Use Waiting for tasks blocked on the client, such as missing credentials or an unanswered mapping question. Keep mapping decisions, validation rules and cutover details in the task descriptions, so the trace of why a decision was made stays with the work.

The agent updates tasks as it completes work in a project session. You can also ask it to reprioritize, add tasks after a scope change, or summarize progress for a status call.

Attach resources

The Resources tab lists the systems, tools, playbooks, artifacts and files linked to the project. Attach the client’s systems and the exports they sent, so every session starts with them in reach. Files attached to a task also join the project.

Linking a resource does not grant access to it. Team members still need their own credentials for a system and the usual access rules apply. See Handover for sharing.

Share, archive and close

Projects can be shared with team members, archived when the engagement ends, and deleted. Archiving hides the project and its sessions from the sidebar and blocks further task changes, while the run history and artifacts remain available.