---
title: "Projects"
description: "Create projects, find your way around a project page, and rename, archive or delete chats and projects."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.myspec.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

A project holds everything for one product or codebase: its chats, spec files
and attachments. Your project role (**Read**, **Write** or **Admin**) decides
whether you can open a project and what you can do in it. See
[Teams and project access](/guides/teams-and-project-access/).

## The Projects page

**Projects** in the top bar is where MySpec opens after you sign in. It shows
the active organization's projects as cards, each with its name, description
and last activity. You only see the projects you have access to.

- **Search projects...** searches the list.
- **All projects** shows every active project you can see. **Created by me**
  shows only the active projects you created. **Archived** shows archived
  ones.
- Page numbers at the bottom move through long lists.

Select a card to open the project.

## Create a project

Every project has a type. When you create one, MySpec shows a card for each:

| Type | What the card says |
|---|---|
| **Greenfield** | A brand-new project starting from scratch. Describe what you want to build and MySpec will draft the specs with you. |
| **Brownfield** | An existing codebase you want to improve. MySpec explores the code first, so a description is optional. |
| **Auto** | Not sure yet? Let MySpec decide based on the selected workflow. |

1. **Start**

   On the **Projects** page, select **New Project**.
2. **Pick a type**

   MySpec asks **What kind of project is this?** Pick one card, then select
   **Next**.
3. **Name and describe it**

   Fill in **PROJECT NAME** and **DESCRIPTION**. The rules depend on the type:

   - **Greenfield**: the description must reach a minimum length. A counter
     next to the field shows your progress, and **Create Project** stays
     disabled until you reach it.
   - **Brownfield**: the description is optional, because the AI explores
     your codebase to understand it.
   - **Auto**: the description is optional.

   Select **Back** to change the type without losing what you typed.
4. **Create it**

   Select **Create Project**. MySpec opens a new chat in the project and
   asks **What would you like to do?** Choose **Generate**, and the message
   box is pre-filled from the project's name and description. Edit it if you
   like, then send it.

The type decides which workflows a new Generate or Edit chat offers:
Greenfield workflows for **Greenfield**, Brownfield workflows for
**Brownfield**, and all of them for **Auto**. See
[Core concepts](/get-started/concepts/#workflows-and-stages).

Every member can create projects, and you get **Admin** on each project you
create.

If your organization has used all the projects its plan allows, MySpec tells
you instead of creating one. See [Usage and limits](/guides/usage-and-limits/).

## Edit a project's details

Open the project's **Settings** tab. **General** shows the project's
**PROJECT NAME**, **DESCRIPTION** and **PROJECT TYPE** (**Auto**,
**Greenfield** or **Brownfield**). Change them and select **Save Changes**. A
new type applies to the workflows that new chats offer.

You can also do this from the **Projects** page: open the project card's
**More options** menu and choose **Edit details**. **Edit Project** has the
same fields and a **Save Changes** button.

Editing, archiving and deleting a project need **Admin** on it. Below Admin,
**General** shows the details read-only, and a project card has no **More
options** menu.

## The project page

A project opens as a workspace with tabs, on its **Home** page: the project's
activity, newest first. A project with no spec files and no chats has no
activity yet, so it opens a new chat instead (unless you only have **Read**
access or the project is archived). Select the project name in the top bar to
return to **Home**.

| Part | What it holds |
|---|---|
| Top bar | The project name (it leads to **Home**), the **Chats**, **Discussions**, **Tasks** and **Settings** tabs, avatars of who else is here (on wider screens), **Share**, the comments button, the notification bell and your avatar. |
| Left sidebar | The file explorer. **Specs**: your spec files, grouped by bundle, with their revisions. **Attachments**: files you uploaded for the AI to read. **Trash Bin**: spec files you removed, when there are any. On the **Settings** tab, the settings menu takes its place. |
| Main area | **Home**, or the tab you selected. |

| Tab | What it shows |
|---|---|
| **Chats** | The project's sessions, on a **Generate** tab and an **Edit** tab. |
| **Discussions** | Every comment thread in the project, grouped by spec file. |
| **Tasks** | The task board, as a table or a Kanban board. Shown only when the task board is available to your organization. |
| **Settings** | The project's details, who has access, and the project's MCP servers and Custom Skills. |

The file explorer stays as you left it, with the same width and the same
folders open, when you switch between **Home**, **Chats**, **Discussions** and
**Tasks**.

With **Read** access, a notice under the top bar says "You have read-only
access to this project. Ask a project admin for Write access to make changes."
on every tab, and the controls that change things are hidden. See
[What Read users see](/guides/teams-and-project-access/#what-read-users-see).

Select the MySpec logo at the top of the left sidebar to go back to
**Projects**.

### Home

**Home** lists everything that has happened in the project, newest first:

- Chats started, completed and archived.
- Spec files created, updated and moved to the Trash Bin.
- Comments opened, replied to and resolved.

Each entry says who did it: **You**, a teammate's name, or an AI assistant
such as **Your AI assistant** or "Alice's AI assistant" for work the AI did in
someone's chat. Several spec files created or updated in a row by the same
person or AI share one entry. Select **Show all** to list them.

Select a chat to open it, or a spec file or comment to open it in the preview.
A file that is now in the Trash Bin is marked **In Trash**. Select **Show older
activity** at the bottom to load earlier entries.

### Chats

**Chats** is a tab of its own. The **Generate** tab lists Generate sessions and the **Edit** tab lists Edit
sessions.

- To start a chat, select **Chat** on the **Generate** tab or **Edit** on
  the **Edit** tab. A new Generate chat starts with its message box
  pre-filled from the project's name and description. Starting a chat needs
  **Write** access.
- **Search chats...** filters the list by chat name.
- **Active**, **Archived** and **All** filter by archive state.

Each chat card shows its name, its workflow and its state: the current stage,
**In progress** or **Completed**. A chat a teammate started also says who
started it. An archived chat's card says who archived it and when, for example
"Archived by Alice · 2 hours ago".

See [Generate sessions](/guides/generate-sessions/) and
[Edit sessions](/guides/edit-sessions/).

### Discussions

The **Discussions** tab shows the comments panel full screen: every comment
thread in the project, grouped by spec file. The tab's badge shows how many
threads are open. Filter the threads, reply and resolve them, or select **Open
in file** to see a thread next to its passage. See
[Comments](/guides/comments/#the-discussions-tab).

### Tasks

The **Tasks** tab shows the project's task board, as a table or a Kanban
board. The tab appears only when the task board is available to your
organization. The file explorer stays on the left. In a task's details, select
the `tasks.md` file name to open that file in the preview.

A task can be linked to other tasks of the project. In a task's details, under
**Relationships**, select **Add relationship**, choose **Blocked by**,
**Blocks** or **Related to**, and pick the other task. Two tasks have one
relationship at most: picking a new one replaces the old one, and the other task
shows the same link from its side (if A blocks B, B is blocked by A). Select a
linked task to open it, or remove the link with its **×** button. On the table
and the board, a lock badge marks a task that is still blocked by tasks that are
not done.

Changes you make on the board are not saved straight away. Each change to a
task's status, assignee, priority, labels, relationships, dates, points or cycle
waits in your browser, and the changed tasks are highlighted. A bar along the bottom of the
board counts your unsubmitted changes:

- **Review** lists every change, grouped by `tasks.md` file, with a way to undo
  one field or a whole task.
- **Submit** saves all of them at once. Each `tasks.md` file gets one new
  revision, however many of its tasks you changed.
- **Discard** throws them away, after asking.

Your unsubmitted changes stay in this browser if you reload the page or come
back later, and are cleared when you sign out. If someone else changed a task
after you did, the review marks it, and it is not submitted until you choose to
keep your change.

### Settings

On the **Settings** tab, the left sidebar shows a menu instead of the file
explorer:

| Page | What it holds |
|---|---|
| **General** | The project's name, description and type, and for Admins the **Danger zone**. See [Edit a project's details](#edit-a-projects-details), [Archive a project](#archive-a-project) and [Delete a project](#delete-a-project). |
| **Access** | The **Access** card, then **People with access** and **Collaborators**. See [Project access](#project-access). |
| **MCP servers** | MCP servers available only in this project's AI sessions. See [Connect your own MCP servers](/guides/your-mcp-servers/#add-a-server-to-a-project). |
| **Custom skills** | The skills included in this project's AI sessions. See [Custom Skills](/guides/custom-skills/#choose-skills-for-a-project). |

**MCP servers** and **Custom skills** are for project Admins. Below **Admin**,
the menu shows only **General** and **Access**.

### Spec files and attachments

In the file explorer, select a spec file to open it, or expand it to see its
revisions. Each bundle can be downloaded as a ZIP file with **Download
bundle**. See [View and edit spec files](/guides/spec-editor/).

Use **Upload attachment**, or drop files onto **Attachments**, to give the AI
documents to read. See [Attachments and local files](/guides/attachments/).

### People and comments

- The avatars in the top bar show who else is viewing the project or working
  in one of its chats right now.
- **Settings** → **Access** lists **People with access** and
  **Collaborators**. See [Project access](#project-access).
- The comments button shows how many comment threads are unresolved and opens
  the **Comments** panel. The **Discussions** tab shows the same threads full
  screen.

See [Working together](/guides/collaboration/) and [Comments](/guides/comments/).

### Share

**Share** creates a public, read-only link to the spec files you choose. It
needs **Write** access. See [Share links](/guides/share-links/).

### Project access

Open **Settings** → **Access**. The **Access** card shows who can see and
change this project: the organization's default project access, organization
owners and admins (always Admin), and the teams and people the project gives
access to. Everyone who can open the project can see it.

If you have **Admin** on the project, select **Add access** to give a person or
team **Read**, **Write** or **Admin**, or change or remove access next to their
name. See
[Give people and teams access to a project](/guides/teams-and-project-access/#give-people-and-teams-access-to-a-project).

Below the card:

- **People with access** lists everyone who can open this project, with their
  role.
- **Collaborators** lists everyone who has written a revision in this project,
  with their number of revisions and when they were last active.

## Rename, archive or delete a chat

Renaming, archiving, unarchiving and deleting chats need **Write** access.
Open a chat card's **More options** menu:

| Action | What it does |
|---|---|
| **Rename** | Opens **Rename chat**. Enter a new **Chat name** and save. |
| **Archive** | Makes the chat read-only. It moves to the **Archived** filter. |
| **Unarchive** | Makes an archived chat active again. |
| **Download** | Downloads the chat's spec files as a ZIP file. Shown only for completed chats, to everyone who can open the project. |
| **Delete** | Deletes the chat permanently. Shown only for archived chats. |

An archived chat can't be continued. Its page says who archived it: **This
session was archived by** _name_**. It is read-only and cannot be
continued.**

When you archive a chat that never finished, its spec files leave the file
explorer. The spec files of a completed chat stay visible after you archive it.

### Delete a chat

1. **Archive it**

   Choose **Archive** in the chat card's menu.
2. **Find it**

   Select the **Archived** filter.
3. **Delete it**

   Choose **Delete** in the card's menu and confirm. The chat is deleted
   permanently and cannot be recovered.

## Archive a project

You need **Admin** on the project. Archive it in either place:

- In the project, open **Settings** → **General**. Under **Danger zone**,
  select **Archive** and confirm.
- On the **Projects** page, open the project card's **More options** menu and
  choose **Archive**.

The project moves to the **Archived** tab of the **Projects** page and shows an
**Archived** badge. Its card says who archived it and when, for example
"Archived by Alice · 2 hours ago".

To bring it back, select **Unarchive** in the project's **Danger zone**. It
doesn't ask you to confirm. Or open the **Archived** tab on the **Projects**
page and choose **Unarchive** in the card's menu.

## Delete a project

You need **Admin** on the project, and you can only delete an archived
project.

From the project:

1. **Archive it**

   Open **Settings** → **General**. Under **Danger zone**, select **Archive**
   and confirm.
2. **Delete it**

   **Delete** is enabled once the project is archived. Select it and confirm
   **Delete project?**. The project is deleted permanently and cannot be
   recovered, and MySpec returns you to **Projects**.

From the **Projects** page:

1. **Archive it**

   Choose **Archive** in the project card's menu.
2. **Find it**

   Open the **Archived** tab on the **Projects** page.
3. **Delete it**

   Choose **Delete** in the card's menu and confirm **Delete project?**. The
   project is deleted permanently and cannot be recovered.

Source: https://docs.myspec.dev/guides/projects/index.mdx