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

# Projects

> How workers manage multi-step work that spans days, weeks, or many conversations

## What are Projects?

Projects are **living workspaces** your worker maintains for ongoing work that can't be finished in a single conversation. They give your worker a place to track goals, tasks, progress, and important context — so you can pick up exactly where you left off, every time.

You might also hear them called **Work Streams**. Same idea: a dedicated thread of work your worker actively owns and advances over time.

<Info>
  Projects are designed for work that has a clear goal but unfolds across multiple steps, decisions, and days. If a task takes five minutes, you don't need a project for it.
</Info>

## When to Use Projects

Projects shine when work is ongoing, multi-step, or needs to be tracked over time.

<CardGroup cols={2}>
  <Card title="Good for Projects" icon="check">
    * Recruiting a new hire (research, outreach, scheduling, follow-ups)
    * Launching a new product feature (coordination across multiple tools and people)
    * Onboarding a new client (weeks of tasks across email, docs, and calendar)
    * Running a content calendar (planning, drafting, publishing, reviewing)
  </Card>

  <Card title="Not Needed for Projects" icon="xmark">
    * One-off requests ("Summarize this document")
    * Quick lookups or simple questions
    * Tasks fully completed in a single conversation
    * Recurring automations handled by a skill
  </Card>
</CardGroup>

## Core Components of a Project

Every project your worker maintains has four key parts:

| Component   | What it is                                                           |
| ----------- | -------------------------------------------------------------------- |
| **Goal**    | The clear outcome you're working toward                              |
| **Tasks**   | Individual steps or actions needed to reach the goal                 |
| **Summary** | A running snapshot of where things stand right now                   |
| **Notes**   | Context, decisions, constraints, and anything else worth remembering |

Your worker keeps all of this updated automatically as work progresses. You don't need to re-explain the situation every time — the project holds that context for you.

## A Real Example: Hiring a Content Writer

Here's how a project keeps work moving across multiple conversations.

**Monday** — You ask your worker to find a freelance content writer.

> "Start a project to hire a content writer. We need someone with SaaS experience, €300–500 per article. Start by finding five candidates."

Your worker creates the project, defines the goal, and starts researching.

***

**Wednesday** — You check in.

> "What's the status on the content writer project?"

Your worker gives you a summary: three candidates found, two more to research, outreach emails drafted and ready to send.

***

**Friday** — You continue.

> "Send the outreach emails and add a task to follow up in five days."

Done. The project is updated with the new tasks and the follow-up is scheduled.

***

**The following week** — No re-explaining needed. Your worker already knows the goal, the candidates, what was sent, and what comes next.

<Tip>
  The longer a project runs, the more useful it becomes. Your worker builds up rich context over time — so your instructions can get shorter, not longer.
</Tip>

## How to Create a Project

Creating a project is just a conversation. There's no form to fill in.

<Steps>
  <Step title="Tell your worker what you're working toward">
    Describe the goal in plain language. You don't need to plan every step upfront — your worker will help structure it.

    > "I want to start a project to onboard our new client, Acme Corp. The goal is to have them fully set up and active within four weeks."
  </Step>

  <Step title="Your worker sets it up">
    They'll create the project, confirm the goal, and either draft an initial task list or ask a few clarifying questions to get started.
  </Step>

  <Step title="Work it conversation by conversation">
    Each time you come back, just ask for a status update or give the next instruction. Your worker tracks everything between conversations.
  </Step>

  <Step title="Complete tasks as they're done">
    As your worker finishes tasks, they'll mark them as **Completed**. You can also do this yourself: "Mark the contract task as done."
  </Step>
</Steps>

## Your Projects on the Board

Every project also has a visual home in the app. Open **Projects** from the sidebar to see everything your worker is running at a glance, then click into any project for the full picture.

<Steps>
  <Step title="Browse all your projects">
    The Projects area lists every active project, each card showing the worker who owns it and where things stand.
  </Step>

  <Step title="Work the Kanban board">
    Inside a project, the **Tasks** tab is a board with **To Do**, **In Progress**, and **Done** columns. Drag any task card between columns to update its status — your worker sees the change right away.
  </Step>

  <Step title="Set the goal and rules">
    The **Overview** tab is where you edit the project's goal and add working rules — standing guidance your worker follows every time it picks the project back up.
  </Step>

  <Step title="Keep resources in one place">
    Upload files as project **resources** so reference material lives with the work. Your worker can use them, and you can download or remove them anytime.
  </Step>

  <Step title="See the conversations behind the work">
    The **Conversations** tab links every chat connected to the project, so you can trace how the work has unfolded.
  </Step>
</Steps>

<Tip>
  You can manage projects entirely by chatting with your worker, entirely from the board, or any mix of the two — they always stay in sync.
</Tip>

## How Projects Stay Up to Date

Your worker actively maintains the project as work happens:

* **Tasks are added** when new work is identified
* **Tasks are updated** when progress is made
* **The summary is refreshed** to reflect the current state
* **Notes capture decisions** so nothing important gets lost

You can always ask: "What's the current status of \[project name]?" and get a clear, up-to-date picture.

## Completed Tasks and Projects

When tasks are finished, they're marked as **Completed** — they're never deleted. This is intentional.

<Note>
  Completed tasks and finished projects stay in your worker's history. You can always look back to see what was done, when, and why. It's your record of work — not a bin that gets emptied.
</Note>

This means you can:

* **Review what happened** on a past project
* **Refer back** to decisions or context from earlier work
* **Audit progress** over time
* **Reopen work** if a project needs to restart

When all tasks in a project are done, the project itself is marked **Completed** and moves out of your active view — but it's always there when you need it.

## Viewing and Managing Projects

You can ask your worker about projects at any time:

* **"What projects are active right now?"** — Get a list of everything in progress
* **"Give me a status update on \[project name]"** — See the current summary, tasks, and notes
* **"What tasks are still open in \[project name]?"** — Focus on what's left to do
* **"Show me completed projects"** — Browse past work for reference
* **"Add a task to \[project name]"** — Update the project mid-stream
* **"Mark \[task] as done"** — Record progress

You can also ask your worker to prioritize tasks, add deadlines, or reorganize a project as circumstances change.

## Projects vs Skills

Projects and skills are different tools for different kinds of work.

|                        | Projects                         | Skills                       |
| ---------------------- | -------------------------------- | ---------------------------- |
| **Best for**           | Ongoing, multi-step goals        | Repeatable, procedural tasks |
| **Duration**           | Days, weeks, or longer           | Minutes to hours             |
| **Changes each time?** | Yes — evolves as work progresses | No — same steps every time   |
| **Example**            | Launching a new product          | Processing weekly invoices   |

They can work together. A project might include a task that triggers a skill — for example, a client onboarding project where the "send welcome email" step uses a saved email skill.

## Next Steps

<CardGroup cols={2}>
  <Card title="Skills" icon="graduation-cap" href="/concepts/skills">
    Learn how workers save and reuse repeatable workflows
  </Card>

  <Card title="How Workers Learn" icon="brain" href="/concepts/how-workers-learn">
    Understand how your worker builds knowledge and context over time
  </Card>

  <Card title="Training & Feedback" icon="chalkboard-user" href="/guides/training-feedback">
    Get the most out of your worker by guiding their work
  </Card>

  <Card title="Scheduling Tasks" icon="clock" href="/guides/scheduling-tasks">
    Automate recurring work with schedules
  </Card>
</CardGroup>