# Projects
The Projects workspace is where you keep delivery aligned: one place to see project health, ownership, and cross-links into plans, sprints, and tasks. Use it as your starting point before jumping into deeper task or planning flows.

## Projects list

{{< thumbcard src="/images/ui/projects/projects-list.png" alt="Projects list table with status, owners, and last updated" caption="Projects workspace list" >}}

The list shows every project with the fields leaders use to keep delivery on track:
- **Project + key:** canonical handle used across plans, tasks, and MCP commands.
- **Status:** Planned / In Progress / Paused so you can spot stalled initiatives quickly.
- **Owners:** who to page for decisions; add more in the project detail view.
- **Updated:** quick freshness check before a standup or review.

{{% steps %}}

### Step 1 - Filter or sort
Use the search box to find projects by name, owner, or status. This is the fastest way to jump to a single initiative during triage.

### Step 2 - Open a project
Click a row to open the detail view. This is where you'll see description, current state, related services, and tabs for sprints/tasks/metadata.

### Step 3 - Add a project
Select **New Project** to create via MCP. Keep keys short and slug-friendly so they work in CLI and UI contexts.

{{% /steps %}}

> [!TIP]
> Keep “Paused” projects to a minimum; if a project sits with an old updated date, assign an owner and move it to **In Progress** or archive it.

## Project detail

{{< thumbcard src="/images/ui/projects/project-detail-overview.png" alt="Project detail overview tab with description, status, owners, and related services" caption="Project detail — Overview tab" >}}

Every project opens with tabs across the delivery lifecycle:
- **Overview:** description, related services, current state bullets, and the status badge (click to change). Owners live here—keep at least one owner set.
- **Planning:** links into planner artifacts for the project key.
- **Sprints:** sprint cadence and current/previous sprint snapshots.
- **Tasks:** project-scoped backlog entry point (UI work noted below).
- **Collaboration:** contacts and coordination notes.
- **Metadata:** project key, handles, and integration fields.
- **Audit / Docs:** change history and references to supporting docs.

### Tasks tab (in progress)

{{< thumbcard src="/images/ui/projects/project-detail-tasks-tab.png" alt="Tasks tab showing work in progress notice and link back to tasks view" caption="Tasks tab — current state" >}}

The Tasks tab currently routes you to the global Tasks view while inline creation/editor work (UI-007 / UI-012) lands. Use it to keep context but do edits in Tasks until the inline experience ships.

## Navigation tips

- Use the breadcrumb (`PROJECTS`) to return to the list without losing filter context.
- Tabs deep-link (e.g., `?tab=tasks`) so you can bookmark specific views.
- Keep descriptions concise and service references current; they’re used by MCP for quick lookups.

## Next steps

- Pair this view with the [Dashboard](/valdr/docs/ui/dashboard/) to identify projects that need attention.
- Use [Tasks](/valdr/docs/ui/tasks/) to assign work before moving a project to **In Progress**.