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

# ShipSpace

> Plan work, track issues, and collaborate with AI-aware team context.

ShipSpace is Shipyard's planning workspace. It gives your team one place to track issues, organize priorities, discuss work, and hand ready tasks into ShipCode.

<Card title="Open ShipSpace" icon="circle-dot" horizontal href="https://space.shipyard.lol" cta="Go to ShipSpace">
  Start from a new workspace, import existing issues, or review the work already assigned to your team.
</Card>

## What ShipSpace is for

<Columns cols={2}>
  <Column>
    <Card title="Issue tracking" icon="list-checks">
      Track status, priority, ownership, due dates, comments, and implementation context in one shared view.
    </Card>
  </Column>

  <Column>
    <Card title="Planning with context" icon="sparkles">
      Keep workspace knowledge, imported issues, and team discussion close to the work Leo uses to help you plan.
    </Card>
  </Column>

  <Column>
    <Card title="Team collaboration" icon="users">
      Invite teammates, sync changes across devices, assign work, and keep conversations attached to active issues.
    </Card>
  </Column>

  <Column>
    <Card title="ShipCode handoff" icon="code">
      Move planned work into ShipCode when it is ready for implementation, review, testing, and pull requests.
    </Card>
  </Column>
</Columns>

## Start here

<Steps>
  <Step title="Learn the core objects">
    Read [ShipSpace basics](/shipspace-basics) to understand workspaces, issues, Company Knowledge, and messages.
  </Step>

  <Step title="Set up your workspace">
    Use [Initial setup](/shipspace-setup) to create a workspace or import existing Linear issues.
  </Step>

  <Step title="Bring in collaborators">
    Use [Collaboration](/shipspace-collaboration) to invite teammates and work with Leo.
  </Step>
</Steps>

<Tip>
  Start with one workspace and a small set of real issues. You can expand structure, permissions, and team workflows after the first planning loop works.
</Tip>