AI Blocks › Build a product people want
Launch a feature through a beta and read the numbers
Give it the feature. Get a launch plan, a beta, pre-set metrics, release notes and a results read.
Launch a feature through a beta and read the numbers is a free AI workflow for the job "Build a product people want". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks · Thinking: high
What it does
Features launch to everyone at once, with a changelog line nobody reads, and the team decides afterwards which number proves it worked. Whatever went up is the success metric. The users who would have told you it was confusing never got asked. This workflow launches in order. It plans the launch: who gets it first, what could go wrong, what the rollback is. It sets up a beta with the users who feel the problem most and a way to hear from them weekly. It decides the metrics before anything ships: what success looks like, what the guardrails are, and the number that would make you pull it. It writes the release notes in plain words, saying what changed for the user. After launch, it reads the numbers against the metrics you set and says what they mean, including when they mean nothing yet.
You give it
- The feature: what it does and who it is for
- How you can reach users and roll out to a subset
- What the business needs from this feature
- After launch, the numbers and the beta feedback
- Codebase (optional)
You get
- A launch plan with order, risks and rollback
- A beta programme: who, how many, how you hear from them
- The metrics decided before launch, with success, guardrails and the pull number
- Release notes in plain words, and a results read after launch
Use it when
- A feature is two weeks from done and nobody has planned the launch.
- Your last launch went to everyone and broke something.
- Your team argues after launch about whether it worked.
Steps
- Feature launch planner: Name your feature. Get a launch plan with messaging, support prep, rollout steps and rollback triggers.
- Beta program planner: Describe your launch. Get who to invite, what to ask them, and clear rules for when the beta ends.
- Product metrics planner: Say your product stage. Get the KPIs to track, a dashboard layout and how to read retention and adoption.
- Release notes writer: Point it at your commits. Get tidy release notes and the right version bump from Conventional Commits.
- Product metrics review writer: Give it your product numbers. Get trends against targets, what moved and what to do about it.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
- Paste the feature and who it is for. It plans the launch, the beta and the metrics.
- Run the beta. Collect the feedback it asks for.
- Approve and publish the release notes. After two to four weeks, paste the numbers for the results read.