> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.islo.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.islo.dev/_mcp/server.

# Feature delivery

> Plan a Linear ticket, then implement, review, and verify its pull request.

The **Ship a planned ticket** Suggested Line (`ship-planned-ticket`) implements a Linear ticket, opens a pull request, and sends the change through review and verification. Use it when the ticket already has a clear scope and acceptance criteria.

## Prepare the ticket and factory

1. Connect GitHub and Linear in [Manage → Integrations](https://app.islo.dev/integrations).
2. Prepare a [Machine](/concepts/machines) with the repository and tools the Agents need.
3. [Deploy the Suggested Line](/concepts/suggested-lines) in the factory. It uses implementer, reviewer, and verifier Agents.
4. Add the `Islo` label to the planned Linear ticket. The Line's Linear trigger starts a run when the issue is updated with that label. You can also start the Line with the ticket URL as its `input`.
5. Inspect the run and its pull request. The Manager sends concrete review or verification failures back to the implementer. The Line leaves the pull request open for your normal merge process.

If the ticket needs a plan first, deploy **Plan a ticket** (`plan-ticket`) and add the `Islo-plan` label. That Line reviews a plan in the Linear issue without changing code. Add `Islo` when the ticket is ready to ship.

For a reported bug, [Issue triage](/concepts/issue-triage) can produce the ticket first. To change stages, triggers, or review rules, [build a custom Line](/concepts/custom-lines).