> ## 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. # Docs > Where decisions get written down: briefs drafted from real customer evidence, shaped with Lane, and sent straight to the tools your team builds in. A Doc is where a decision becomes something your team can build. Most specs start from memory and a blank page, and the customer evidence that justified the work gets lost on the way to engineering. In Lane, a Doc starts from that evidence: the feedback, the customers asking, the revenue at stake, already in the draft. Lane writes the first version in your team's structure, you shape it together, and then it goes straight to the tool where the work happens, with the customers behind it still attached. ## Start a Doc Start from wherever the decision is: * **From an [Opportunity](/opportunities)**, for the bigger bets. Choose **Create Doc** at the top of the Opportunity. Lane drafts from every Signal in it and the feedback behind them, and the Opportunity and its Signals are marked **Accepted**: one step records the decision. * **From a [Signal](/signals)**, for a single problem. Choose **Create Doc** on the Signal. The Doc stays linked to the Signal and its feedback. * **From a piece of [feedback](/insights)**, when one request is worth acting on directly. Choose **Doc** on the feedback item. * **From scratch**, with the **+** next to **Docs** in the sidebar. * **From [Ask Lane](/agent)**, by asking: "draft a brief for the SSO Opportunity". With **Use Lane**, Lane drafts the Doc for you: the problem, the evidence and who it affects, written from the real feedback, the customers behind it with their revenue and tier, and your workspace [Context](/context). Pick a template for the structure. Drafting uses AI credits. With **Write it myself**, you start from the title and summary and write it yourself. ## Templates Templates make every draft come out in your team's format. Lane comes with a built-in brief template, and on Pro you can add your own under **Settings → Doc templates**: the structure of a PRD, an opportunity brief or a release note, the way your team writes them. While writing, type **/** and choose **Template** to drop a ready-made outline, like a PRD, a bug report or release notes, into any Doc. ## Write with Lane Lane works alongside you in the Doc: * **Ask Lane** opens a chat about this Doc, for drafting new sections, sharpening ones that miss, or pulling in more evidence. * **Type /** and choose **Ask Agent** to have Lane write right where your cursor is. * **Select text** and use **AI Rewrite** to **Polish**, **Summarize**, **Elaborate** or make it **More Formal**, then replace the original or copy the result. When Lane changes a Doc that a person wrote, or one someone has edited since Lane last touched it, it asks for approval first. Your writing is never overwritten silently. ## Send it where the work happens When a Doc is ready to build, use the button at the top of the page: * **Send to** [Linear](/linear), [Notion](/notion), [Jira](/jira) or [Asana](/asana) creates the issue, page or task from the Doc. In Linear, the customers behind the Doc arrive as customer requests, so engineers see who's waiting and the revenue at stake. The button then shows the item's live status. * **Open in** hands the Doc to a coding agent: **Cursor cloud** or **Cursor app** (see [Cursor](/cursor)), or **Lovable**. * **Copy as markdown** to paste it anywhere. AI apps connected through the [MCP server](/mcp-server), like Claude or Cursor, can read your Docs too. ## Collaborate and share * **Comments**: highlight text to start a thread, @mention teammates, and resolve threads when they're settled. * **Subscribe** with the bell to hear about comments and changes. * **Visibility**: Docs you create start **Private**, visible only to you. Switch to **Workspace** so everyone in the workspace can view and Editors can edit, or **Public** to share a read-only link with anyone, no Lane account needed. * **Favorites**: star a Doc to keep it in your sidebar. Contributors can read the Docs shared with them. ## Docs Lane writes Docs created by Ask Lane, by [Automations](/automation) or by connected AI apps show Lane's icon in the Docs list and are visible to the workspace, ready for your team to review. Private Docs are never shared with automations or AI apps. ## Getting better results * **Start from evidence.** Create the Doc from the Opportunity or Signal it's about, so the draft is grounded in the real feedback and customers. * **Make the template yours.** A custom template in your team's format saves editing every draft. * **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, tell Lane what to fix rather than rewriting by hand or starting over. ## FAQs **Q: Who can see a Doc?**\ A: Docs you create start Private. Switch any Doc to Workspace or Public from the visibility menu at the top of the page. **Q: Can coding agents build from a Doc?**\ A: Yes. Use **Open in** for Cursor or Lovable, or connect Claude, Cursor or another AI app through the [MCP server](/mcp-server). **Q: Does a sent Doc stay in sync with the tracker?**\ A: The button shows the item's live status in Linear, Notion or Asana. To have shipping close the loop with customers, use status sync on the Signal in [Linear](/linear) or [Notion](/notion). **Q: What if I run out of AI credits?**\ A: Drafting and rewriting pause until credits are available; you can still create and edit Docs yourself. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.