# Growth Studio Test a clear message and learn whether it helps people take the intended next step. Category inspiration: The Growth Department, from the supplied @unicodef1wn chart. Cabinet treatment: New crew built around existing Pulse and Story. Version: 0.1 · October 6, 2026. Status: Published manual setup instructions with Codex text-only exercise evidence. Native imports, tools, and Bot-to-Bot handoffs remain untested. Category-chart inspiration: [unicodef1wn’s grokbot field notes](https://github.com/unicodef1wn/grokbot-field-notes). These are original Bot Cabinet instructions inspired by the categories, not exact ports of the chart’s templates. ## Bots and jobs | Bot | Treatment | Job | |---|---|---| | [Pulse](https://botcabinet.com/bots/pulse/) | Existing Cabinet Bot | Define the baseline, primary result, success rule, and stop rule. | | [Story](https://botcabinet.com/bots/story/) | Existing Cabinet Bot | Shape positioning from approved evidence and audience needs. | | [Campaign Builder](../specialists/campaign-builder.md) | Published manual role | Prepare paused campaign specifications and copy variants. | | [Coder](https://botcabinet.com/bots/coder/) | Existing Cabinet Bot | Prepare an approved landing-page change in a project copy. | Use Researcher for market evidence and Ad Spend Review for a separate cost check. Chief of Staff can coordinate when several real handoffs need it; do not install a manager merely to make the roster bigger. ## When a crew helps A message test across a landing page and a paid channel has different implementation and measurement tasks. One audience or funnel question can stay with Pulse. ## Bring these inputs Audience and goal, confirmed product claims, current page and baseline data, proposed channel and budget, tracking definition, stop rule, and approval owner. ## Set up and run 1. Select only the roles this job needs. Existing role links lead to Cabinet's current setup pages; new role links contain full manual-test instructions. 2. Put each selected role in its own conversation or Bot. Paste the new role's Role instructions section, or add the task extension below to an existing role. These files are not native import archives or add-to-app links. 3. Start with the fictional first task below. Supply the same approved source records to each role that needs them. A copied handoff alone is not evidence for a factual claim. 4. Pass reviewed results in the order below. If your app lacks Bot-to-Bot handoff, copy the small handoff yourself. Do not assume a shared folder, tool connection, or group conversation creates separate security boundaries. 5. Record each actual answer and failed attempt. Review before connecting real accounts or adding a schedule. Set read-only access and service-side cost caps where available; these written limits cannot enforce a billing cap. ## Who passes what to whom 1. Pulse defines what counts as a result and identifies missing measurements. 2. Story returns evidence-supported positioning. 3. Campaign Builder proposes variants and Coder proposes the matching page change. 4. Pulse defines how results will be assessed; the person approves implementation, launch, and spending. Use this handoff: - Task and current version: - Approved source records: - Result and its status: draft, checked, or approved: - Unresolved questions: - Next owner and action: - External action awaiting specific approval: If a role cannot finish, it returns the missing input or failed attempt. The next role must not manufacture a success record. ## Task extensions for existing Bots ### Pulse Keep the existing Bot's role and boundaries. For this crew: Define the baseline, primary result, success rule, and stop rule. Define the goal, baseline, and result measure. Separate observations from interpretations and decisions. Propose a bounded test with success and stop rules. Use only the input assigned to you for this task. Return the result, supporting records, unresolved questions, and next owner. A handoff does not approve an external action. ### Story Keep the existing Bot's role and boundaries. For this crew: Shape positioning from approved evidence and audience needs. Find a clear central message in confirmed facts. Preserve important qualifications and distinguish evidence from aspirations. Use only the input assigned to you for this task. Return the result, supporting records, unresolved questions, and next owner. A handoff does not approve an external action. ### Coder Keep the existing Bot's role and boundaries. For this crew: Prepare an approved landing-page change in a project copy. Prepare only the approved software change inside the named project and run allowed checks when tools exist. Report commands, actual results, and remaining limits. Use only the input assigned to you for this task. Return the result, supporting records, unresolved questions, and next owner. A handoff does not approve an external action. ## First task Fictional product: appointment reminders for tutoring firms. Known claim: sends reminders; no evidence about reducing no-shows. Prepare a landing-page outline and two search-ad variants with a proposed $100 cap, seven-day stop, and completed-demo metric. No tracking or repository is supplied. ## Check the result - Makes no claim of fewer missed appointments or improved revenue. - Flags missing demo tracking and repository access. - Keeps the $100 and seven-day limits. - Reports draft specifications, with no live page or campaign claim. Save the app, model if shown, date, answers, actual external actions, and pass/fail/not-checked against each item. A written checklist or a favorable review does not prove a runtime pass. ## Limits for this sample One message test and two variants. All spending and launch actions remain disabled; proposed budget does not authorize spending. Stop when the task finishes, a required input is missing, a tool fails, or an action needs new approval. No automatic retries. No new credentials, private connectors, external messages, purchases, publishing, or deployment are part of the sample. ## Finished output A message brief, page proposal, paused campaign specification, and measurement plan. ## Exercise evidence The [collection record](../specialists/collection.json) preserves the original Codex text answer, checks, failures, limitations, and any revised attempt. These records are instruction exercises, not native-app validation. Proposed operational tests remain unrun where the record says so.