ShipSpace organizes product work around workspaces, issues, and shared context. Start with the smallest structure that reflects how your team already works, then add more detail as your workflow becomes clearer.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.
Workspaces
A workspace groups related projects, issues, teammates, and knowledge. Use separate workspaces when teams need different visibility or priorities.
Issues
Issues track the work itself: status, priority, ownership, discussion, and handoff into ShipCode.
Company Knowledge
Company Knowledge gives Leo and connected tools durable context about your product, team, decisions, and workflows.
Messages
Messages keep collaboration close to the work so teammates can discuss decisions without leaving ShipSpace.
How the pieces connect
From issue to implementation
Issues collect the planning context that ShipCode needs when work is ready to build.
From discussion to memory
Important decisions should be captured in issue details or Company Knowledge so Leo and teammates can reuse them later.
Keep the first setup simple
Import or create issues
Bring in existing work from Linear or create a few representative issues manually.
Review priorities
Confirm imported priorities, owners, due dates, and categories before using the board for planning.
You can revise the workspace structure later. ShipSpace is designed to grow from a lightweight issue tracker into a shared planning layer for your team.