Projects

Create, structure, and manage projects — the top-level container for milestones and tasks.

A project is the container for a body of work. It can be generated by AI or created entirely by hand.

Fields

Field	Meaning
Name	The project's title.
Description	What the project is about; also feeds AI context for generation.
Workspace	Personal (private to you) or a Team (shared). Set by `team_id`.
Tech stack	A list of technologies. Suggested by AI generation; freely editable.
Success metrics	The outcomes that define "done well".
Sprints	`current_sprint` and `total_sprints` for week/sprint planning.
AI-generated	A flag indicating the project originated from AI generation.

Creating a project

With AI — see AI Generation. You provide a prompt, type, duration, and complexity; sprintrr produces the project with milestones and tasks already populated.

Manually — create an empty project and add milestones and tasks yourself. Manual projects behave identically; the only difference is the AI-generated flag.

A project belongs to a personal workspace when it has no team, or to a team workspace when it is created (or moved) under a team. Team projects are visible to team members per their role; personal projects are private to you. Switch workspace from the sidebar to see the corresponding projects.

Organizing with folders

Projects in the sidebar can be grouped into folders, up to two levels deep:

Folder
└── Subfolder
    └── Project

Subfolders can hold projects but cannot themselves contain more folders — the database rejects a third level of nesting.

Folder scope mirrors project scope: in a team workspace folders are shared across the team, in a personal workspace they're private to you. The two are never mixed — you can't move a personal project into a team folder.

Working with folders from the sidebar:

New Folder — creates a root folder. Click the action menu (⋯) on a folder to add a subfolder, rename, or delete it.
Move to folder… — open a project's action menu and pick a destination (or "No folder (top level)") from the indented tree.
Expand / collapse — click the chevron next to a folder name. State persists across reloads.
Deleting a folder keeps every project inside — they move back to the top level. Folder delete never deletes projects.

Archiving vs. deleting

Two distinct actions for retiring a project:

Archive — soft state. The project disappears from the main sidebar list but is still there in a collapsible Archived section at the bottom. Unarchive at any time to restore it. Tasks, milestones, and the folder location are all preserved. Use this for projects you've wrapped up but want to keep around.
Delete — permanent. Removes the project and every task and milestone under it. There is no trash/restore. Export first if you want a copy (see Data & Export).

Deletion cascades: removing a project removes every task and milestone under it. There is no trash/restore — archive instead if you might want it back later.

Milestones — checkpoints within a project.
Tasks — the unit of execution.
Data & Export — export a project as JSON, CSV, or a reusable template.

PreviousCore Concepts NextTasks