feature-launch

feature-launch is a command for Claude Code from kelegele/oh-my-pm. It costs 15 tokens per session (181 once invoked), scanned A, original, MIT.

A command that coordinates a feature from its product requirements document through release and analysis after launch. A product requirements document describes what a feature should do and why.

In plain words
What is it for?
It is for finalising requirements, validating prototypes, planning implementation, managing deployment, measuring impact, and collecting feedback.
Why use it?
It keeps design, preparation, release, and post-launch review in one workflow instead of treating them as unrelated tasks.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the oh-my-pm plugin — 12 skills, 4 commands shipped together

Good fit It is for finalising requirements, validating prototypes, planning implementation, managing deployment, measuring impact, and collecting feedback.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kelegele/oh-my-pm/feature-launch
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/kelegele/oh-my-pm

Made for: Claude Code.

Or install oh-my-pm, the plugin that ships this one along with the rest of its 12 skills, 4 commands.

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 feature-launch

README.md
[![agentmods](https://agentmods.dev/badge/commands/kelegele/oh-my-pm/feature-launch/github.svg)](https://agentmods.dev/commands/kelegele/oh-my-pm/feature-launch)
Your own site
<a href="https://agentmods.dev/commands/kelegele/oh-my-pm/feature-launch"><img src="https://agentmods.dev/badge/commands/kelegele/oh-my-pm/feature-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 feature-launch

Your own site · 80×15
<a href="https://agentmods.dev/commands/kelegele/oh-my-pm/feature-launch"><img src="https://agentmods.dev/badge/commands/kelegele/oh-my-pm/feature-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 181 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.00015 $0.00181
Opus 5 $0.00008 $0.00090
Sonnet 5 $0.00003 $0.00036
Haiku 4.5 $0.00002 $0.00018

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

Security

Grade A, and why

feature-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 8d 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.

commands/feature-launch.md · 29 lines

What it actually says

Feature Launch Workflow

Ship features successfully from PRD to post-launch analysis.

What This Does

Orchestrates the end-to-end feature launch:

  • Stage 1 (Design): PRD finalization, prototype validation
  • Stage 2 (Prepare): Requirement review, project planning
  • Stage 3 (Release): Release management and deployment
  • Stage 4 (Validate): Impact analysis, feedback synthesis

Usage

  • /feature-launch "user onboarding flow"
  • /ompm feature-launch "checkout redesign" 2026-04-15

Execution

This command activates the feature-launch workflow skill.

Your input: $ARGUMENTS

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. 8d ago First seen · 29 lines · 15 tokens per session scan A 6bf5c2987b77

Subscribe to this mod's changes

feature-launch is a command published in the GitHub repository kelegele/oh-my-pm (4 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 181 once invoked, about $0.0001 per session on Opus 5. 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-08-31.