product-os: Command for Claude Code

.claude/commands/learn-5-build-launch.md

learn-5-build-launch is a command for Claude Code from motorway-sandbox/product-os. It costs 0 tokens per session (2,052 once invoked), scanned A, original, MIT.

A coaching command for the fifth module of a six-part product-management course, focused on preparing and running a launch through discussion and scenarios.

In plain words
What is it for?
Use it to work through a launch checklist and kill criteria for an experiment. Kill criteria are predefined conditions for stopping an experiment or rollout.
Why use it?
It gives a product manager a structured way to practise launch readiness and deciding when to stop an experiment.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is motorway-sandbox/product-os's own configuration. It tells Claude Code how to work on product-os itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything product-os configures →

Reuse

Borrowing it

Nothing to install: this file belongs to motorway-sandbox/product-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/motorway-sandbox/product-os/main/.claude/commands/learn-5-build-launch.md
Clone the repo
git clone --depth 1 https://github.com/motorway-sandbox/product-os

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for learn-5-build-launch

README.md
[![agentmods](https://agentmods.dev/badge/commands/motorway-sandbox/product-os/learn-5-build-launch/github.svg)](https://agentmods.dev/commands/motorway-sandbox/product-os/learn-5-build-launch)
Your own site
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/learn-5-build-launch"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/learn-5-build-launch/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for learn-5-build-launch

Your own site · 80×15
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/learn-5-build-launch"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/learn-5-build-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,052 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02052
Opus 5 $0.00000 $0.01026
Sonnet 5 $0.00000 $0.00410
Haiku 4.5 $0.00000 $0.00205

Measured 6d ago against content hash 4ad7b5fe0e11, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

learn-5-build-launch scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/learn-5-build-launch.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a PM coach running Module 5 of 6 in the PM training course. Your job is to teach the PM how to prepare for and execute a launch through discussion and concrete scenarios.

Setup

Before starting, read these files silently (do not output their contents):

  • pm-playbook/process/5-build-and-launch.md
  • pm-playbook/templates/launch-checklist.md
  • pm-playbook/templates/event-tracking-template.md
  • pm-playbook/training-course/scenario-brief.md
  • pm-playbook/training-course/analytics-data.md
  • context/brand/messaging/how-we-sound.md
  • data/funnel-context.md

Scene Setting

Module 5: Build & Launch

Engineering has been building for 2 weeks. Sam (Tech Lead) tells you the experiment is ready for QA and could launch next Monday. You've already communicated the build timeline and expected launch date to cross-functional team members — User Ops, Customer Services, CRM, and the Data team all know this is coming. Your focus now is on launch preparation.

This module has 2 exercises: launch readiness and kill criteria.

Tell the PM:

Before we begin:

  1. Your experiment doc is at projects/user-onboarding/reduced-invite-requirements-experiment.md. You'll add your rollout plan and kill criteria there.
  2. Read the process doc for this stage: pm-playbook/process/5-build-and-launch.md. Pay attention to the launch checklist.

Read the process doc now.

After they've read, do a quick comprehension check:

Quick check before we start. Imagine a different experiment launched last week. Here are the dashboard numbers after 24 hours:

Metric Control Treatment
Users entering step 204 51
Step completed 98 34
Completion rate 48% 67%
Tracking events firing Yes Yes

The PM on that experiment messaged the team: "Great news — treatment completion rate is 19pp higher than control! Looks like this is working."

Do you spot anything odd here? And would you trust their conclusion?

Read the full file on GitHub · 170 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 170 lines · 0 tokens per session scan A 4ad7b5fe0e11

Subscribe to this mod's changes

learn-5-build-launch is a command published in the GitHub repository motorway-sandbox/product-os (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,052 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.