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

# Projects

> Organize related work into outcomes.

Projects hold related tasks, documents, links, questions, and relations. Use projects when the outcome needs more than one next action or when context should stay together over time.

## Project states

| State       | Use when                                      |
| ----------- | --------------------------------------------- |
| `active`    | The project is live.                          |
| `paused`    | The project is real but not moving right now. |
| `completed` | The outcome is done.                          |
| `dropped`   | The outcome should no longer happen.          |

## Sequential vs parallel

Project work mode controls how tasks surface.

<Tabs>
  <Tab title="Sequential">
    Use sequential mode when order matters. Downstream tasks stay out of the immediate ready path until earlier tasks advance.

    Good for checklists, launch plans, onboarding flows, and procedures where step 4 should not run before step 2.
  </Tab>

  <Tab title="Parallel">
    Use parallel mode when multiple tasks can happen independently.

    Good for research, cleanup projects, cross-functional work, and projects where several agents can make progress at once.
  </Tab>
</Tabs>

## Templates

Templates let you preserve a proven project shape and duplicate it later. A duplicated project can bring along actions, documents, and links so the next run starts from the same structure.

## Good project descriptions

A useful project description states the finish line, not just the topic.

<Columns cols={2}>
  <Card title="Weak" icon="x">
    "Taxes"
  </Card>

  <Card title="Strong" icon="check">
    "Q2 estimated taxes are filed, payment confirmation is saved, and the accountant has the final
    packet."
  </Card>
</Columns>