> ## 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 > What you decide to build — the bets you commit to, grounded in real customer signal, shaped with Lane, and wired straight to delivery. A Plan is what you decide to build. It's the unit of work that carries a decision from discovery to delivery — the bet you commit to, with the [Signals](/signals), [Feedback](/insights), and [Customers](/customers) behind it linked in and kept in sync as that data changes. Where a Signal is a pattern worth acting on, a Plan is the thing you're actually doing about it. Each Plan holds the brief for that work — the problem, the scope, the decisions — and connects to everything around it: the customer evidence that justifies it, the team weighing in, and the delivery tool that builds it. Shape it with Lane, align as a team, then push it to where the work ships. ## Start a Plan Begin wherever your thinking is: * **From a Signal** — the most common path. Open a Signal and draft a Plan from it; the underlying Insights, customer segments, and revenue impact come in as context. Ideal for turning a recurring pattern into an opportunity brief. * **From a piece of Feedback** — when a single request is worth acting on directly, draft a Plan straight from it. * **From the Plans page** — start blank when you already know what you're building and want to drive the structure yourself. When you draft with **Use Lane**, Lane assembles a structured first draft from the linked data; **Write it myself** opens a Plan seeded with that data linked so you can write it yourself. Plans started from a Signal or Feedback stay linked back to their source. ## Inside a Plan A Plan isn't a single page — it's a small set of pages that belong together. Every Plan opens with an **Overview**, and you can add live pages alongside it. **Overview** — the one writable page, where the brief for this work lives. Organize it into sections (problem, scope, success criteria); Lane can read and rewrite any section on its own, so you refine one part at a time without disturbing the rest. **Live pages** pull from your workspace and stay in sync — you configure what they show rather than write into them: * **Insights** — a live view of the Insights relevant to this Plan, so the work stays backed by raw customer signal. * **Figma** — embed a file or prototype so design sits next to the writing. A simple Plan is just an Overview. A larger initiative might pair it with an Insights view and a Figma page. ## Write with Lane Lane works alongside you in the Plan, not as a separate step: * **In the side panel** — a chat scoped to the Plan, best for drafting and refining sections and pulling in linked data. * **In the editor** — highlight text or type `/` to ask about the surrounding content without leaving the page. * **Rewrite** — select any text for **Polish**, **Summarize**, **Elaborate**, or **More Formal**. The rewrite streams in below your selection; apply it to replace the original or copy it out. Lane never silently changes a Plan — its edits come through as proposals you accept or reject. ### Templates To avoid a blank page, apply a **template** to the Overview — PRDs, opportunity briefs, competitive analyses, release notes, and more. A template gives you a structured outline, and Lane can fill each section from the data linked to the Plan. Your workspace's own templates are managed in **Plan templates** settings. ## Link a Plan to your work A Plan connects to records across your workspace — [Feedback](/insights), [Signals](/signals), [Customers](/customers), and Tags. Linked records appear as chips below the title, stay in sync, and drive what your live pages show (link a Customer, and the Insights view narrows to that account's footprint). There's a meaningful distinction in how feedback links: a Plan can **commit** specific feedback — the exact requests it will answer, which is what drives [Linear](/linear) customer requests and closing the loop — or carry broader **Signal and customer context** for grounding. Lane keeps those two separate so a Plan's commitments stay precise. ## Statuses and closing the loop Every Plan carries a status, starting at **Parked** and moving through your workspace's stages to a shipped state. Statuses are configurable under [Properties](/fields). Status is what closes the loop. When a Plan reaches a shipped status, the customers behind its committed feedback can be told automatically — a reply in the original [Slack](/slack) thread, an internal note in [Intercom](/intercom) or [Zendesk](/zendesk) — so delivery flows back to the people who asked. See [Closing the loop](/close-the-feedback-loop). ## Ship it When a Plan is ready to build, send it where the work happens — from the same **Open in** / **Send to** control: * **Open in** hands the Plan to a coding agent, formatted for it: **Cursor cloud**, **Cursor app**, or **Lovable**. See [Cursor](/cursor) for the connected setup. You can also **Copy as Markdown** to paste anywhere. * **Send to** pushes the Plan into a delivery tracker — **[Notion](/notion)**, **Linear**, **[Jira](/jira)**, or **[Asana](/asana)** — as a page, issue, or epic. For Notion, Linear, and Asana, status changes in the tool sync back onto the Plan, so Lane reflects where the work actually is. For any other assistant, connect Lane over the [Model Context Protocol](/mcp-server) and reference a Plan in a prompt to pull its full content and linked context. ## Collaborate and share * **Comments** — discuss decisions in context, useful when engineers, designers, and stakeholders weigh in on the same draft. The creator is subscribed automatically, and subscribers are notified on comments, replies, and status changes. * **Visibility** — every Plan is **Private** by default. Switch to **Workspace** (everyone in your workspace can view; non-contributors can edit) or **Public** (share with anyone via a link, no Lane account needed). Contributors are always read-only. * **Export** — copy a Plan as Markdown, or generate a share link. ## Editor essentials The Overview supports the formatting you'd expect — bold, italic, underline, strikethrough, highlight, and inline code; three heading levels, bullet, numbered, and checklists, blockquotes, code blocks, and tables; and images via upload or paste. Type `/` for the slash menu. ## Getting better results * **Start with thinking, not drafting.** Talk through the problem with Lane first, then ask for a draft. Plans that begin as "write up X" tend to be thin because no exploration happened. * **Link before you draft.** Attach the Signals, Feedback, or Customers you want reflected first — Lane uses linked records as primary context. * **Refine section by section.** Lane is sharpest improving one section at a time; tightening as you go beats cleaning up a whole one-shot draft. * **Say what's wrong.** If a section misses, reply in the side panel with what to fix rather than rewriting by hand or starting over. ## FAQs **Q: Can a Plan have multiple pages?**\ A: Yes. Every Plan has an Overview where you write, and you can add live Insights and Figma pages alongside it that stay in sync with your data. **Q: Who can see a Plan?**\ A: Private by default. Switch any Plan to workspace-visible or share it publicly via a link. **Q: Can coding agents build from a Plan?**\ A: Yes — use **Open in** (Cursor or Lovable), or read Plans over Lane's [MCP server](/mcp-server) from any compatible tool. **Q: Does pushing a Plan keep it in sync?**\ A: Sending to Notion, Linear, or Asana links the Plan to the created item, and status changes there sync back onto the Plan. **Q: What if I run out of AI credits?**\ A: Lane's drafting and rewrite features pause; you can still create and edit Plans manually.