Playbook catalog
Overview
Section titled “Overview”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 / time / plan
Section titled “Who / time / plan”- 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
Catalog by audience
Section titled “Catalog by audience”Founders & first week
Section titled “Founders & first week”- Founder to Cursor in 15 minutes — Signup → gos_ key → one claim on an ACTIVE sprint
- Evaluate GrowthOS in one week — Path A or B, Native board, one agent claim
- Free vs Pro — When sprints and unlimited MCP handoffs matter
- 5-person startup — Team seats, roles, Native vs Connected
- Without a PM — Founder as Owner + Planner, invite later
Plan & ship
Section titled “Plan & ship”- Ship an enterprise app — Production depth, Build-ready PRD, Figma, Sprint 0, one-task agent loop
- How to ship a feature — Idea Lab or next wave → phases → UX Spec → backlog → sprint
- Onboard an existing SaaS — Living PRD + one next-wave goal — not a rewrite
- Paste an existing PRD — Bring a written PRD into Idea Lab, then phases
- Next wave after MVP — Continue planning on the same project
- Blank / Architect project — Skip the full wizard; add AI later
- Share PRD for review — Share-for-review link before finalize
- First sprint — AI plan (Pro+), start ACTIVE, claimable work
- After sprint 1 — Continue vs advance_sprint — always ask first
Agents & design
Section titled “Agents & design”- Agent-first workflow — Keys, skills, one task per turn, when to use humans
- Explore a repo — Coding agent seeds product context from the codebase
- UX Spec → Figma — Design-intent screens to frames, figmaUrl back
- Engineer day — Today → My Tasks → sprint loop
- Designer day — UX Spec queue, Figma CTA, skip non-UI
Team & execution
Section titled “Team & execution”- Native only (no Jira) — Ship on the GrowthOS board, Today, and My Tasks
- Run with Jira — Plan in GrowthOS; execute in Jira — Enterprise Connected
- Run with Linear — Same Connected pattern; Jira-only fields are N/A
- First teammate invite — Roles vs seats; invite after a backlog exists
What you can do here
Section titled “What you can do here”- 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.
When to use
Section titled “When to use”- 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.
Prerequisites
Section titled “Prerequisites”- A GrowthOS account. Seed login for local: see the backend README.
Where to find it
Section titled “Where to find it”- This catalog: sidebar Playbooks.
- Homepage hero Playbooks CTA.
Step-by-step
Section titled “Step-by-step”- Scan the groups below (also in the sidebar).
- Open one playbook. Read Who / time / plan before you start.
- Follow its steps. Use related guides when you need the full feature page.
What success looks like
Section titled “What success looks like”- You opened the right playbook for your plan — not a Connected guide on Free/Team.
- You know which feature pages to read next.
Tips & best practices
Section titled “Tips & best practices”- 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).
Common mistakes
Section titled “Common mistakes”- Treating playbooks as a promise that Free includes sprints.
- Assuming Jira/Linear connect on Team.