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.
npx skills add kelegele/oh-my-pm --skill feature-launchgit clone --depth 1 https://github.com/kelegele/oh-my-pmWrote 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.
[](https://agentmods.dev/skills/kelegele/oh-my-pm/feature-launch)<a href="https://agentmods.dev/skills/kelegele/oh-my-pm/feature-launch"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/kelegele/oh-my-pm/feature-launch"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/feature-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00165 | $0.03185 |
| Opus 5 | $0.00082 | $0.01592 |
| Sonnet 5 | $0.00033 | $0.00637 |
| Haiku 4.5 | $0.00016 | $0.00318 |
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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Launch
从 PRD 到上线后分析的功能发布：物料库为主，Plan-and-Execute 编排为可选骨架。
What This Workflow Does
两类能力，按需取用：
-
发布物料库（核心价值）—— 发布策略选型、灰度放量计划、回滚计划、上线后监控基线、分阶段 checklist、风险管理。PM 每次发布都要现编、又易漏的东西。
- read
references/launch-playbook.mdwhen planning a release（定类型、选策略、画灰度、备回滚、设监控、过 checklist）。
- read
-
可选 Plan-and-Execute 编排 —— 当你要走完整的"PRD 定稿 → 发布 → 复盘"四阶段流水线时，按下文骨架执行（带状态追踪与质量门控）。轻量发布可跳过编排，直接取用物料库。
Workflow Architecture（可选骨架）
⚠️ 下面的四阶段编排是可选的。多数发布只需 read
references/launch-playbook.md取用对应物料；只有需要完整阶段定义、状态追踪和质量门控的全流程协调时，才走这条骨架。
本编排采用 Plan-and-Execute 模式，Spans:
- Design: PRD finalization, prototype validation
- Delivery: PRD 预审尾门（prd-gen）、发布策略与上线 checklist（read
references/launch-playbook.md） - Validation: Retrospective (impact + next iteration), feedback synthesis
五层对应阶段
| Stage ID | 名称 | 对应层 | 说明 |
|---|---|---|---|
| S0 | Setup | 初始化 | 创建工作流状态文件 |
| S1 | Design | 方案设计 | PRD 定稿、原型验证 |
| S2 | Delivery | 交付协调 | PRD 预审尾门、发布策略与上线 checklist |
| S3 | Validation | 价值验证 | 复盘、反馈综合 |
Workflow Stages
| Stage ID | 名称 | 质量门控 | 下阶段 |
|---|---|---|---|
| S0 | Setup | - | S1 |
| S1 | Design | PRD 定稿 + 原型验证 | S2 |
| S2 | Delivery | 发布完成 | S3 |
| S3 | Validation | 效果评估 | 完成 |
阶段执行顺序：S0 → S1 → S2 → S3
Stage 0: Setup
目标：初始化工作流状态和上下文目录
活动：
- 创建
docs/product/launch-{feature-name}/目录用于发布产物 - 初始化
docs/product/.ompm/current-workflow.json当前状态文件
输出：
docs/product/launch-{feature-name}/目录docs/product/.ompm/current-workflow.json空模板
质量门控：
- ✅ 目录结构创建完成
- ✅ 状态模板初始化完成
Stage 1: Design (方案设计)
目标：完成方案设计层的 PRD 定稿和原型验证
活动：
- PRD 生成 -
prd-genskill（最终版本） - 原型设计 -
prototype-designskill（验证）
技能调用：
- Step 1.1: 调用 prd-gen 技能生成最终 PRD
- Step 1.2: 调用 prototype-design 技能验证或创建原型
输出：
docs/product/prd/{feature-name}-final-v{version}.mddocs/product/prototypes/{feature-name}.html（如选择）
质量门控：
- ✅ PRD 完整（9 章）
- ✅ 原型已验证
- 质量门控通过 - 进入 Delivery 阶段
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 369 lines · 165 tokens per session scan A 16767b9d8b1b
feature-launch is a skill published in the GitHub repository kelegele/oh-my-pm (4 stars, last pushed 1mo ago), licensed MIT. It adds 165 tokens to every session and 3,185 once invoked, about $0.0008 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.
Other skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.