Skip to content

Playbook catalog

Playbooks are scenario glue, not a second copy of Idea Lab or MCP feature docs. Each one states who it is for, how long it takes, which plan you need, numbered steps, and what not to promise.

Honest gates: Free is 1 seat, 1 project, 1 PRD, and 1 MCP handoff. Sprints are Pro+. API keys exist on Free. Connected (Jira, Linear, Asana, ClickUp, GitLab) is Enterprise / design-partner — not Team. Native is the default path.

Time tracking, automations, SSO, burndown/retro, and executive dashboards still show coming soon in the app. Do not treat those as live playbooks.

  • Who: Anyone picking a scenario instead of a feature page
  • Time: 5 minutes to pick a guide
  • Plan: Any — each playbook states its own gate
  • Pick a starter that matches your role and plan.
  • Follow numbered steps, then jump into the linked feature pages for depth.
  • Use Native unless you are on an Enterprise Connected workspace.
  • You know the outcome (ship a feature, connect Cursor) but not which screens to open.
  • You are evaluating GrowthOS and want an honest demo script.
  • A GrowthOS account. Seed login for local: see the backend README.
  • This catalog: sidebar Playbooks.
  • Homepage hero Playbooks CTA.
  1. Scan the groups below (also in the sidebar).
  2. Open one playbook. Read Who / time / plan before you start.
  3. Follow its steps. Use related guides when you need the full feature page.
  • You opened the right playbook for your plan — not a Connected guide on Free/Team.
  • You know which feature pages to read next.
  • Keep product names in English (Idea Lab, UX Spec, Native, gos_ key) even in हिन्दी / मराठी.
  • Agents work Native tickets. They must not overwrite synced Connected status (TASK_SYNCED_READ_ONLY).
  • Treating playbooks as a promise that Free includes sprints.
  • Assuming Jira/Linear connect on Team.