> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/goals-and-okrs/creating-goals/draft-okrs-with-ai.md). # Draft OKRs with AI Rhythms can draft Key Results, Initiatives, child Objectives or whole OKR sets for you. For an existing Objective, open its **⋯** menu, choose **Add key result** (or **Add initiative**, **Add child objective**) and click **Generate**; Rhythms opens a chat, studies the Objective and proposes goals as editable cards. For a new set, click **Create OKRs → Create with Rhythms** or just describe what you want in chat. Nothing is created until you approve it. ## Generate Key Results, Initiatives or child Objectives for an Objective 1. In a tree view, click **⋯** on the Objective → **Add key result** → **Generate**. (The same submenu offers **Create manually**. In a flat list, switch to the tree view first.) 2. Chat opens with "Generate key results for *Objective*" and Rhythms proposes a set of Key Results drawn from the Objective's title, description, team and time period, each with a metric, owner and team. 3. Edit any card: change the type, title, owner, team, time period, metric or parent. Remove cards you don't want with the ×, or click **Add another**. 4. Click **Publish** to create them, or **Draft** to save them as drafts only you, the owners and their teams can see. You need manage permission on the Objective (its owners, their managers or a Rhythms Admin by default) to see **Generate**. The submenu appears only for child types your OKR model allows under that goal. ## Draft a full set of OKRs in chat 1. Click **Create OKRs → Create with Rhythms**, or open chat and describe the outcome: "We want to expand into enterprise accounts this quarter. Draft an Objective and Key Results for the Sales team." 2. Answer Rhythms' questions about team, time period and priorities. Attach planning documents if you have them. 3. Push back until it is right: "make the targets more aggressive", "add a Key Result for retention", "align these to the company revenue Objective". 4. Review the cards and click **Publish** or **Draft**. For the full walkthrough see [Create OKRs and initiatives](/goals-and-okrs/creating-goals/create-okrs-and-initiatives.md). ## Improve wording while you write In the create form, the title field has a **Suggest** button when it is empty and an **Improve** button once you have typed. Rhythms explains what is weak about the current wording and offers alternatives; click **Use** to take one. The Key Results section has its own **Suggest** (then **Suggest more**). In chat you can ask the same of any existing goal: "Is KR-042 measurable? How would you rewrite it?". ## Cascade an Objective to teams On an Objective, **⋯ → Cascade to Teams** starts a chat that proposes aligned child Objectives for the teams you name, each with its own owner and team. Review and publish as above. ## Tips * **Give context.** Name the team, the period and what success looks like; Rhythms also reads the Objective's description and the parent goals. * **Iterate.** Treat the first proposal as a starting point and ask for alternatives. * **Anchor to strategy.** Generated goals are aligned to the Objective you started from; check the **Aligned To** field on each card. ## Frequently asked questions **Are generated goals published automatically?** No. Every proposal waits for you to click **Publish** or **Draft**. If your workspace uses the [approval workflow](/goals-and-okrs/managing-and-tracking-goals/okr-approval-workflow.md), Draft is the primary action and publishing goes through approval. **Can I ask for a particular format?** Yes: "Write these as 'We will X as measured by Y'" or "Follow the Measure What Matters structure" works in chat. **Can Rhythms use my connected data when setting targets?** Yes. If the relevant connector is set up, ask, for example, "Based on last quarter's pipeline in Salesforce, suggest a realistic ARR target for Q3." **Why don't I see Generate?** Either you lack manage permission on the goal, the child type is not allowed under it by your OKR model, or you are in a flat list rather than a tree view. ## Related articles * [Create OKRs and initiatives](/goals-and-okrs/creating-goals/create-okrs-and-initiatives.md) * [Import OKRs from a spreadsheet](/goals-and-okrs/creating-goals/import-okrs-from-a-spreadsheet.md) * [Introduction to OKRs](/goals-and-okrs/okr-foundations-and-structure/introduction-to-okrs.md) * [Model Customization](/workspace-settings-and-administration/customize-rhythms-settings/model-customization-alignment-contribution-and-terminology.md) * [OKR Approval Workflow](/goals-and-okrs/managing-and-tracking-goals/okr-approval-workflow.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rhythms.ai/goals-and-okrs/creating-goals/draft-okrs-with-ai.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.