Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.laneapp.co/llms.txt

Use this file to discover all available pages before exploring further.

Plans are living product documents — PRDs, opportunity briefs, strategy docs, release notes — written with the Agent and grounded in real workspace data. A Plan reads your product directly: Features, Customers, Signals, and Objectives all carry their full context in. Plans are also where your team works together. PMs draft, engineers comment, stakeholders read — one source of truth that stays connected to the underlying data instead of going stale the moment it’s written.

​
Start a Plan

There are four places to begin, depending on where your thinking is. From a conversation with the Agent — when an exploration converges on something worth recording, convert the chat into a Plan in place. The Plan inherits the context you’ve already built. From the Plans page — start blank when you know what kind of document you want and want to drive the structure yourself. From a Feature — open any Feature and create a Plan from it. The Agent pulls the Feature’s linked Insights, requesting Customers, total revenue, priority score, and the Objective it serves. Ideal for PRDs and feature briefs. From a Signal — open a Signal and create a Plan from it. The Agent synthesizes the underlying Insights, customer segments, and revenue impact into a single document — ideal for turning a recurring pattern into an opportunity brief. New Plans started from a Feature or Signal are automatically linked back.

​
Inside a Plan: pages

A Plan isn’t a single page — it’s a small collection of pages that belong together. Every Plan starts with an Overview, and you can add more pages alongside it.

​
Overview

The Overview is where you write. It’s the only writable page in a Plan — your PRD, brief, or strategy lives here. Templates — to avoid starting from a blank page, apply a template to the Overview. Built-in templates include PRDs, opportunity briefs, competitive analyses, release notes, and more. A template gives you a structured outline; the Agent can fill in each section using the data linked to the Plan. Sections — the Overview can be organized into sections (problem, scope, success criteria, etc.). The Agent can read and rewrite any section independently, which is what makes it easy to refine one part of the document at a time without disturbing the rest.

​
Live pages

Beyond the Overview, you can add live pages that pull from your workspace data. You don’t write into these — you configure what they show, and they stay in sync as the underlying data changes.
  • Insights — a live view of the Insights relevant to this Plan. Useful when the document needs to be backed by raw customer signal.
  • Objectives — the Objectives this Plan supports, as a list.
  • Roadmap — Features connected to this Plan, as a list or board. Useful for quarterly planning, release notes or feature briefs.
  • Figma — embed a Figma file or prototype so design lives next to the writing.
A simple Plan is just an Overview. A larger initiative might pair the Overview with a Roadmap, an Insights view, and a Figma page.

​
Write with the Agent

Inside a Plan — a chat scoped to the Plan opens in the side panel. Best for drafting, refining sections, and pulling in linked data. In the editor — highlight text or type / to ask the Agent about the surrounding content without leaving the page.

​
AI rewrite

Select any text in the editor to access rewrite options:
  • Polish — tighten prose and fix grammar
  • Summarize — condense into a concise version
  • Elaborate — expand with additional detail
  • More Formal — rewrite in a professional tone
The rewritten text streams in below your selection. Apply it to replace the original or copy it to the clipboard. For more on how to work with the Agent across Lane, see Agent.
A Plan can connect to records across your workspace:
  • Features
  • Objectives
  • Signals
  • Customers
  • Insights and Feedback
  • Tags
Linked records appear as chips below the title and stay in sync. They also drive what shows up in your live pages — for example, linking a Customer narrows the Insights and Roadmap pages to that Customer’s footprint. Open any linked Feature or Objective and you’ll see the Plan listed in its Plans section.

​
Collaborate and share

Comments — leave comments on a Plan to discuss decisions in context. Useful when engineers, designers, and stakeholders are weighing in on the same draft. Sharing — every Plan has three visibility modes:
  • Private (default) — only you can see the Plan
  • Workspace — visible to everyone in your Lane workspace
  • Public — share with anyone via a link, no Lane account needed
Workspace members can edit; Contributors are read-only.

​
Hand off to a coding agent

When a Plan is ready to build, send it to a coding agent. Click Open in and pick Cursor, Cursor Cloud, or Lovable — the Plan is formatted for agent consumption (context, requirements, linked data) and picked up to start building. For any other AI tool, connect Lane through the Model Context Protocol. Claude, Cursor, Windsurf, or any MCP-compatible assistant can reference a Plan in a prompt and pull its full content along with linked Features, Customers, and Signals.

​
Export

Copy a Plan as Markdown to paste anywhere, or generate a share link to send it to people outside Lane.

​
Editor essentials

The Overview supports the formatting you’d expect:
  • Text — bold, italic, underline, strikethrough, highlight, inline code
  • Blocks — three heading levels, bullet lists, numbered lists, checklists, blockquotes, code blocks, tables
  • Media — images via upload or paste
Type / to open the slash menu for quick access to any block type.

​
Getting better results

A few habits that lead to sharper Plans:
  • Start with thinking, not drafting. Talk to the Agent about the problem first. Once the direction is clear, ask it to draft. Plans that start as “write a PRD for X” tend to be thin because no exploration happened.
  • Refine section by section. The Agent is sharpest when improving one section at a time. Drafting a whole document in one shot leaves you with prose to clean up everywhere; tightening section by section produces a better result.
  • Link before you draft. Attach the Features, Customers, or Signals you want the Plan to reflect before asking the Agent for content — it uses linked records as primary context.
  • Tell the Agent what’s wrong. If a section misses the mark, reply in the side panel with what to fix. Don’t rewrite by hand and don’t start over.

​
Good to know

  • Live pages stay in sync with the underlying data. If a Feature’s customer list changes, the Roadmap page reflects the new state.
  • The Agent never silently changes a Plan — Plan edits come through as proposals you accept or reject.
  • If AI credits run out, AI features pause but you can still create and edit Plans manually.

​
FAQs

Q: Can coding agents like Cursor build from a Plan?
A: Yes. Use Open in (Cursor, Cursor Cloud, or Lovable), or read Plans via Lane’s MCP server from any MCP-compatible tool. Q: Can a Plan have multiple pages?
A: Yes. Every Plan has an Overview where you write. You can add Insights, Objectives, Roadmap, and Figma pages alongside it — these are live views that stay in sync with your data. Q: Who can see a Plan?
A: Plans are private by default. You can switch any Plan to workspace-visible or share it publicly via a link. Q: Can a Plan link to multiple records?
A: Yes. Any number of Features, Objectives, Signals, Customers, Insights, Feedback, or Tags. Q: What happens if I run out of AI credits?
A: AI features pause; manual editing keeps working.