> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/concepts/projects.md).

# Projects

## Projects

### Projects

A Project is the primary unit of planned work in DuploCloud. It brings together everything needed to take a goal from idea to completion — a spec, an implementation plan, and a series of tickets that the AI Engineer executes.

**Structure of a Project**

Every Project consists of three building blocks:

**Spec** — A detailed description of what needs to be accomplished. The spec is drafted collaboratively with the AI Engineer and approved before any implementation begins. It captures requirements across areas such as infrastructure, CI/CD, workloads, observability, compliance, security, and cost.

**Plan** — A step-by-step implementation plan derived from the approved spec. The plan is broken down into discrete tasks, organized into stages, and approved before execution starts.

**Tickets** — The individual units of work that the AI Engineer executes. Each ticket corresponds to a task in the plan and tracks everything that happens during execution — commands run, decisions made, context carried forward. Tickets created under a Project automatically get access to that Project's shared context — its approved Spec and Plan — in addition to the usual Workspace and platform settings, so the agent can reference them directly during execution without being told to look them up.

**Stages and Parallel Execution**

Tasks in a plan are grouped into stages. Each stage contains tickets that are independent of one another — they have no dependencies on other tickets within the same stage, which means all tickets in a stage can be executed in parallel. Stages are completed in sequence: the next stage begins once all tickets in the current stage are done.

This structure gives you both predictability (stages enforce order where it matters) and speed (parallelism within each stage).

**Scope**

Projects can optionally define their own Scope as a subset of the assigned Engineer's Scope. If no custom Scope is set, the Project defaults to the Engineer's full Scope — controlling exactly which cloud environments, clusters, and resources the AI Engineer can access when executing work for that Project.

**Creating a Project**

Projects are created from the DuploCloud platform UI. Once a project exists, you can take all subsequent actions — drafting the spec, writing the plan, and executing tickets — directly from your IDE or terminal using the DuploCloud plugin.

***

### Projects Tutorial

Projects in AI DevOps help you organize multi-stage engineering work. Each project contains an AI-generated specification, a phased plan, and a set of executable tasks — all managed through an AI Planner conversation and tracked across an Execution view.

***

### Step 1 — Navigate to Projects

In the left sidebar, click **Projects** under the **AI DevOps** section.

![Projects list](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-1d738bfecb7ade5e932d4492d9f4b40c3c298bf3%2Fprojects-step-01-projects-list.png?alt=media)

The Projects page lists all existing projects in a table. Each row shows the project's name, description, priority, accumulated cost, assigned scopes, start date, creator, and last modified date.

***

### Step 2 — Create a Project

Click the **Add** button in the top right corner of the table.

![Add button](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-69579fedc737a6da61893d9014bdef602451873b%2Fprojects-step-04-add-button.png?alt=media)

The **Add Project** form opens.

![Add Project form](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-8221dbbd7390d7fb9fbfcb8551458c33532766b3%2Fprojects-step-05-add-form-overview.png?alt=media)

Fill in the project details:

**Name** — give the project a clear, descriptive name.

![Name field](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-540a1eed370ca38f16b973ec57fe168aa11a102e%2Fprojects-step-06-form-name.png?alt=media)

**Description** *(optional)* — briefly describe the project goal.

![Description field](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-99f71366e6832c937a2172909bc6a237da60f539%2Fprojects-step-07-form-description.png?alt=media)

**Scopes** — select one or more scopes to grant the AI agents the cloud access they need.

![Scopes field](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-107aed347597265f2a47a3dab1f613d0e401ff6b%2Fprojects-step-08-form-scopes.png?alt=media)

**System Prompt** *(optional)* — add instructions that the AI agent follows when working on this project's tickets, such as preferred approaches or reporting requirements.

![System Prompt field](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-a767b50b96545d911bb50adb65f10db140b3dcd5%2Fprojects-step-09b-form-system-prompt.png?alt=media)

**Priority** *(optional)* — set a priority level: Low, Medium, High, or Critical.

![Priority field](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-39f7cfdb9c2af1df97f0cd9cfcb737091b179bfd%2Fprojects-step-09-form-priority.png?alt=media)

**Start Date / End Date** *(optional)* — set the intended project timeline.

![Date fields](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-bf04d80d691a6bb1c8f3064f4e1ff68830827bfe%2Fprojects-step-10-form-dates.png?alt=media)

> **AI-Powered Workflow** — after creating the project, you can use AI agents to help create specifications, generate detailed plans, and break them down into actionable tasks.

![AI workflow callout](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-5b3837fd6098bf1c6a28aec4b027657e76c8d5ea%2Fprojects-step-11-ai-workflow.png?alt=media)

When ready, click **Create**.

![Create button](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-3595bf9c61a6c6b84fce4c0ba7b3724c66785062%2Fprojects-step-12-form-create-button.png?alt=media)

The new project appears in the list. You can now open it to begin the AI planning workflow.

***

### Step 3 — Open a Project

Click a project name in the list to open it.

![Project in list](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-b12b19817354c298aae915ae5096e92dce757ef2%2Fprojects-step-13-project-in-list.png?alt=media)

The project detail page opens. It has two tabs — **Project Overview** and **Execution** — and a right sidebar with project context and metadata. If the project already has execution tasks, the page opens on the **Execution** tab.

![Project detail overview](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-3ef27556cfbf0df70388220d2db7f5ffb2c0e862%2Fprojects-step-14-project-detail-overview.png?alt=media)

The **Project Overview** tab shows the **Project Workflow** as three cards:

* **Specification** — **Edit** the spec or view its **Git Diff**.
* **Plan** — **Edit** the plan or view its **Git Diff**.
* **Execution** — **View Board** to open the task board.

**Git Diff** is available only when the project has Source Control configured.

![Project Workflow on the Project Overview tab](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-cc2cee2ff6c3a17e8b23624d3ec7538062b40d8e%2Fprojects-duplocloud-project-workflow.png?alt=media)

The **Execution** tab shows the project's stages as columns, each listing its tasks. Use the search box to find tasks, and the **All**, **Open**, **In Progress**, and **Closed** filters to narrow the board by status. Each filter shows its task count.

![Execution tab search and filters](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-72d484baac08c2321797810576591b6805250d1d%2Fprojects-step-16-execution-tab.png?alt=media)

Use **Generate Summary** to get a plain-language status update from the AI across all tasks.

![Generate Summary](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-9b39ca2dcaad17be2d1b27d5b8faf5d442692c52%2Fprojects-step-17-generate-summary.png?alt=media)

The right sidebar contains:

* **Add relevant context for your project** — upload documents, code, and other files for AI DevOps to reference in project chats.
* **Details** — creator, scopes, total cost, priority, last modified date, start date, and target date.
* **Reports** and **Secrets** — click **View** to see the reports and secrets attached to the project.
* **Source Control** — click **+ Add** to connect a repository by selecting a **Scope**, **Organization**, **Repository**, **Branch**, and **Folder Path**.

![Reports, Secrets, and Source Control in the sidebar](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-23023c6913b37a1f7a2ad5989e19e0ea004dea49%2Fprojects-step-19b-sidebar-reports-secrets-source-control.png?alt=media)

* **Specs**, **Plan**, and **Execution** — the project's saved artifacts. The Execution section shows the number of stages and tasks, how many tasks have linked tickets, and overall progress.

![Specs section in sidebar](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-f34fd852d8acfa99debadfc1e53e906ce388125b%2Fprojects-step-19-specs-section.png?alt=media)

***

### Step 4 — Open the AI Planner

Click **Open AI Planner** to launch the AI planning conversation for the project.

![Open AI Planner button](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-44c541170a9c2916dc29c301e0e43730fb42a437%2Fprojects-step-18-open-ai-planner-btn.png?alt=media)

The AI Planner opens as a conversation, with **Back** at the top left to return to the project. The right panel has **Details**, **Files**, and **Activity** tabs; **Details** shows the planner ticket's status, LLM, cost, scopes, personas, skills, priority, and permissions. During planning, the AI runs discovery against your environment and generates a specification, a phased plan, and an execution task set. All three are accessible as artifact blocks in the conversation.

![AI Planner overview](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-15ca79977f77bcc660e09e4d7043d445b62977d7%2Fprojects-step-22-ai-planner-overview.png?alt=media)

***

### Step 5 — Review and Save the Spec

Scroll up in the AI Planner conversation to find the **spec.md** artifact block — the project specification the AI generated from your initial prompt.

![spec.md artifact in chat](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-45da1adc49b7a4c65f70a9bfd00a25696bd98b7a%2Fprojects-step-24-spec-artifact.png?alt=media)

Click the **spec.md** block to open the specification alongside the conversation. The spec documents your environment's current state, goals, and constraints that the plan and tasks are built against.

![Spec view](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e9e1f9bc808cbe80474c43dd6f3b3cc805f21a4e%2Fprojects-step-25-spec-view.png?alt=media)

The toolbar above the open artifact shows **View Diff**, to review the changes in this version, and **Save Spec**. Click **Save Spec** to persist this version of the specification to the project.

![View Diff and Save Spec](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-abfccc30d771af51bdfda068b2984655c73604dd%2Fprojects-step-25b-spec-toolbar.png?alt=media)

***

### Step 6 — Review and Save the Plan

Navigate back to the AI Planner and click the **plan.md** artifact block to view the phased plan.

![plan.md artifact in chat](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e4e89580c96b85414a5d34f30a0ac730796a4644%2Fprojects-step-26-plan-artifact.png?alt=media)

The plan breaks the project into named phases, each with specific tasks, acceptance criteria, and an implementation approach.

![Plan view](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-b8022e1208dfe55bdbf3def9a02aa61a28a68ded%2Fprojects-step-27-plan-view.png?alt=media)

Click **Save Plan** to save it to the project.

![Save Plan](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-404a88c1c8b570934328495333256fef1af698e8%2Fprojects-step-27b-save-plan.png?alt=media)

***

### Step 7 — Review and Save the Execution Tasks

Navigate back to the AI Planner and click the **execution\_tasks.json** artifact block to view the full execution task set.

![Execution tasks artifact in chat](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e6f2356da06acc5cceac36d4bc41c35835c38e2c%2Fprojects-step-28-execution-artifact.png?alt=media)

The execution tasks view shows all stages and their tasks in structured form. Each task includes a title, description, acceptance criteria, and stage assignment.

![Execution tasks view](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-32459f20465aacd5de3a75ed487a6fdc7399674f%2Fprojects-step-29-execution-view.png?alt=media)

Click **Save Execution Tasks** to write these tasks to the project. Saving populates the Execution tab with the complete task breakdown, organised by stage.

![Save Execution Tasks](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-6892e053ca74e89afc0d34d3ca7729f6e8a1cd1c%2Fprojects-step-29b-save-execution.png?alt=media)

***

### Step 8 — Track Execution

Navigate back to the project and click the **Execution** tab to see the task board.

![Execution tab active](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-cd0f2e3512770f3f77e2efe37f729ccdf42dfc6a%2Fprojects-step-31-execution-tab-active.png?alt=media)

Each stage is a column. The stage header shows the stage name, its task count, and a short summary of the stage's goal, and each task card shows its current status.

Stages progress sequentially — earlier stages typically cover baseline work that must complete before later stages begin. Tasks within a stage are independent and can run in parallel.

![Phase 1 stage column](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-877248248dd7a2821e1e85216ed959d4c6da38b1%2Fprojects-step-33-phase1.png?alt=media)

At the bottom of each stage, **Create New Task** adds a task manually, and **Create Tickets** opens the **Create Stage Tickets** dialog. Select the tasks to create tickets for and set the **LLM**, **Scopes**, **Personas**, and **Command Execution Permissions** for each; use **Apply to checked** to copy one task's settings to all selected tasks. Then click **Create** — the button shows how many tickets will be created.

![Create Stage Tickets dialog](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e3f1c53ed1ee5c45068a70a35774067a36be9867%2Fprojects-step-33b-create-stage-tickets.png?alt=media)

Tasks that have been linked to AI tickets show the ticket ID on the task card.

![Task with ticket ID](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-037b84f38a735d294fc372a8f66823c25c72d648%2Fprojects-step-34-task1-in-list.png?alt=media)

Click the **⋮** menu on a task card to **Edit** the task, **Open Ticket**, **Open Ticket in New Tab**, or **Delete** the task.

![Task menu](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-465dc55e04532fb7e96237c737c60cfe7f1b7ef4%2Fprojects-step-34b-task-menu.png?alt=media)

***

### Step 9 — Open a Task Ticket

Click a task's ticket ID, or choose **Open Ticket** from its **⋮** menu, to open the AI conversation that executed that task.

![Task ticket overview](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-270200cfba3c0fad6bcebfeab3e94d2d00c8da14%2Fprojects-step-35-task1-overview.png?alt=media)

The ticket shows the full AI agent conversation for the task — including tool calls made, command output returned, and the agent's step-by-step reasoning. The right sidebar shows ticket metadata: status, LLM, total cost, ticket summary, scopes, personas, skills, priority, and the ticket ID, followed by command permissions, MCP tool permissions, workspace memory, ticket secret, context files, reports, and feedback.

![Ticket ID in sidebar](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-c8c188b9dbbaca577e3cfa60feebfd9d91c066b9%2Fprojects-step-36-ticket-id.png?alt=media)

Each task ticket is a self-contained record of exactly what the AI did to complete that unit of work, making it auditable and resumable.

***

## VSCode Integration

The DuploCloud Claude plugin lets you work on projects entirely from your local VSCode session. All work — specifications, plans, execution tasks, and ticket conversations — is automatically synced back to the DuploCloud platform for full team visibility.

**Prerequisites:**

* Visual Studio Code is installed.
* Claude Code CLI is available in your terminal.
* The DuploCloud Claude plugin is installed and configured. See the [duplo-claude-plugin](https://github.com/duplocloud/duplo-claude-plugin) repo for installation instructions.
* Your project codebase is available locally.

***

### Step 1 — Connect to the Project from VSCode

Open VSCode in your project directory and launch Claude with the DuploCloud plugin:

```bash
claude
```

Claude greets you and lists all available Workspaces.

![Claude Code launching with the DuploCloud plugin](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-6bc2c284e59e12cfb87ff6da8de386df1c639dc6%2Fprojects-vscode-plugin-launch.png?alt=media)

Enter the number of your workspace.

![Workspace selection](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-c618cedb178af5e950f0abac522894202f7dadf2%2Fprojects-vscode-workspace-list.png?alt=media)

Claude lists the available projects in that workspace. Enter the number of your project.

![Project selection](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-bac81d159091cf7d355724d5b01ebc5fdaede970%2Fprojects-vscode-project-select.png?alt=media)

Claude activates the project and displays a status table showing the current state of the Spec, Plan, and Execution artifacts. If the project is new, all three will show as empty and ready to begin.

![Project activated — all artifacts empty](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-b004b2830564d2f1526016fcf2ff8d707754dc52%2Fprojects-vscode-project-activated.png?alt=media)

> **Authentication:** When prompted, provide your DuploCloud platform URL and user access token: `authenticate to duplo using url: https://<helpdesk-url> and token: <user-access-token>`

***

### Step 2 — Write the Specification from VSCode

The Specification defines the goals, requirements, scope, and success criteria for the project. Claude helps you write and refine it through a conversational interview.

#### Activate the Spec Ticket

When the project is first activated with no Spec or Plan, Claude prompts you to activate the Spec ticket. Type `yes` to proceed. Claude creates the Spec Creation Ticket, sets it to In Progress, and asks what you'd like to do — choose option 1 to start writing the spec.

![Claude activates the Spec ticket and prompts to begin](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-a466910126a4dd7ad667345a8409c0c3c47aa7b6%2Fprojects-vscode-spec-ticket-activate.png?alt=media)

#### Describe Your Requirements

Describe the project goal in plain language. Claude will explore your codebase and ask clarifying questions about domain boundaries, stakeholders, database constraints, and scope limits.

![Claude explores the codebase and asks clarifying questions](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-532e772c6d71934a36afd31aa92e82c1271cee91%2Fprojects-vscode-spec-questions.png?alt=media)

#### Review and Approve the Spec

Once Claude has enough information it drafts the full specification and presents it for review. You can ask for changes, or confirm it looks good. Claude then asks how to save:

* **Save** — push to the platform in Draft status
* **Save and Approve** — push to the platform and mark as Approved
* **Cancel** — keep the local draft only

Choose **Save and Approve** to mark the spec as approved and move to planning.

![Spec draft review with save options](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-80da56fbc4c76a0bcbe73c42d54696080047d94c%2Fprojects-vscode-spec-save-options.png?alt=media)

![Spec saved and approved — platform confirms ready for planning](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-56ae008bae8f3fd6dfc03e6773f13caebf0b8461%2Fprojects-vscode-spec-approved.png?alt=media)

#### View the Spec on DuploCloud

Once saved, the spec is immediately visible on the DuploCloud platform in the **Project Workflow** on the project's **Project Overview** tab. Click **Edit** on the Specification card to open it in the AI Planner.

![Project Workflow showing the saved Specification and Plan](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-cc2cee2ff6c3a17e8b23624d3ec7538062b40d8e%2Fprojects-duplocloud-project-workflow.png?alt=media)

![Spec content open in the DuploCloud AI Planner](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e9e1f9bc808cbe80474c43dd6f3b3cc805f21a4e%2Fprojects-step-25-spec-view.png?alt=media)

> All conversation messages from your local VSCode Claude session are automatically mirrored to the corresponding ticket on the DuploCloud platform once saved.

***

### Step 3 — Create the Implementation Plan from VSCode

With the spec approved, Claude moves to the planning phase. The plan converts the specification into a detailed, phased implementation roadmap.

#### Generate the Plan

After the spec is approved, Claude automatically moves to planning. It loads the `create_plan` skill, reads the approved spec, and begins drafting the plan. Claude may ask additional clarifying questions (e.g. about inter-service communication patterns). The plan covers goals, architecture overview, tech stack, numbered tasks with file lists, and shell commands.

![Claude generating the implementation plan in VSCode](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-46252132847a4667f61060f82a6e7cf0e72dfeb4%2Fprojects-vscode-plan-generating.png?alt=media)

![Draft plan with tasks and architecture details](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e6b9fd948420d25f6ff2860e9cdbc0ae87f8d409%2Fprojects-vscode-plan-draft.png?alt=media)

#### Review and Approve the Plan

Claude opens `plan.md` in the VSCode editor for easy reading alongside the terminal conversation.

![Plan preview in VSCode with architecture diagram](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-b01b527ab6e02db60c5b632899f02e8d24de091d%2Fprojects-vscode-plan-preview.png?alt=media)

Provide feedback or confirm the plan looks good, then choose **Save and Approve** to push it to the DuploCloud platform.

![Plan saved and approved](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-117a4e0d781f944ba8d5984ea6e050953b6cf172%2Fprojects-vscode-plan-approved.png?alt=media)

***

### Step 4 — Generate and Create Execution Tasks

With both spec and plan approved, Claude can break the plan into granular, actionable execution tasks organised into stages.

#### Request Execution Tasks

Ask Claude to create execution tasks: `Can you create execution tasks?` Claude processes the plan and generates a hierarchical breakdown of stages and tasks. Once saved, the tasks appear in the project on the DuploCloud platform.

![Execution tasks in the DuploCloud AI Planner](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-32459f20465aacd5de3a75ed487a6fdc7399674f%2Fprojects-step-29-execution-view.png?alt=media)

#### Create Tickets

Once the execution tasks are saved, navigate to the project's **Execution** tab in DuploCloud and click **Create Tickets** at the bottom of a stage. In the **Create Stage Tickets** dialog, select the tasks, confirm the LLM and other ticket settings, and click **Create**. DuploCloud creates a dedicated ticket for each selected task with an Open status, visible to the whole team.

![Create Stage Tickets dialog](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e3f1c53ed1ee5c45068a70a35774067a36be9867%2Fprojects-step-33b-create-stage-tickets.png?alt=media)

> You can add tasks with **Create New Task**, or edit a task from its **⋮** menu, on the Execution tab before creating tickets if you need to adjust the AI-generated breakdown.

***

### Step 5 — Work on Individual Tickets from VSCode

Once tickets are created, developers pick them up one by one and complete the work within their local VSCode Claude session. The plugin automatically loads the ticket context and syncs progress back to the platform.

#### Select a Task

Start a new Claude Code session with the DuploCloud plugin and select your workspace and project. Claude displays the current project status and lists all execution tasks with their ticket status. Enter the task number to begin.

![Task list with ticket status in VSCode](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-5a06837f09b3c57a25582baa7611134027cafcdb%2Fprojects-vscode-task-selection.png?alt=media)

#### Execute the Task

Claude loads the ticket context (task description, spec, plan) and begins executing autonomously — reading existing code, creating new files, and verifying the output in your local working directory. Claude presents a verification summary when complete.

![Verification summary showing files created and routes registered](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-6178b2682ddb902434a11efb1a8c9eda18701071%2Fprojects-vscode-task-verification.png?alt=media)

#### Close the Ticket and Move to the Next Task

Once the output looks good, Claude saves a summary to the ticket and asks if you are ready to close it. Confirm to close — Claude sets the ticket status to Closed/Resolved on the platform and immediately prompts you with the next task in the sequence.

![Claude closes the ticket and suggests the next task](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-4cc542655e9fffb41ff4023dc5ad49750b5d5a28%2Fprojects-vscode-task-close-next.png?alt=media)

***

### Step 6 — Team Collaboration: Conversation Mirroring

Every conversation you have in your local VSCode Claude session is automatically mirrored to the corresponding ticket on the DuploCloud platform when saved. This provides full transparency and enables effective team collaboration.

**What gets mirrored:**

* Specification writing conversations → Spec-Creation ticket
* Plan generation conversations → Plan-Creation ticket
* Execution task conversations → Individual task tickets

![DuploCloud ticket showing the full conversation mirrored from VSCode](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-270200cfba3c0fad6bcebfeab3e94d2d00c8da14%2Fprojects-step-35-task1-overview.png?alt=media)

![Execution tab tracking task status](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-cd0f2e3512770f3f77e2efe37f729ccdf42dfc6a%2Fprojects-step-31-execution-tab-active.png?alt=media)

Team leads can review AI-generated specs and plans directly in DuploCloud without needing access to individual developer machines. All decisions and rationale are captured in the ticket conversation history.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/concepts/projects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
