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 full-pm-cyclegit 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/full-pm-cycle)<a href="https://agentmods.dev/skills/kelegele/oh-my-pm/full-pm-cycle"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/full-pm-cycle/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/full-pm-cycle"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/full-pm-cycle.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.00111 | $0.05689 |
| Opus 5 | $0.00056 | $0.02844 |
| Sonnet 5 | $0.00022 | $0.01138 |
| Haiku 4.5 | $0.00011 | $0.00569 |
Grade A, and why
full-pm-cycle 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 — 642 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full PM Cycle Workflow
What This Workflow Does
Orchestrates complete product management lifecycle across all five layers:
- Perception: Market & user research, competitive analysis
- Strategy: Product strategy (positioning, prioritization, roadmap)
- Design: PRD generation (含预审尾门), prototype design (HTML)
- Delivery: PRD 预审尾门确认、发布计划（采用 feature-launch 的发布策略与 checklist）
- Validation: Retrospective (impact + iteration), feedback synthesis
Workflow Architecture
本工作流采用 Plan-and-Execute 模式组织，确保完整的阶段定义、状态追踪和质量门控。
五层对应阶段
| Stage ID | 名称 | 对应层 | 说明 |
|---|---|---|---|
| S0 | Setup | 初始化 | 创建工作流状态文件 |
| S1 | Perception | 需求感知 | 市场与用户研究、竞品分析 |
| S2 | Strategy | 策略规划 | 产品策略（定位、优先级、路线图） |
| S3 | Design | 方案设计 | PRD 生成、原型设计 |
| S4 | Delivery | 交付协调 | PRD 预审尾门、发布计划 |
| S5 | Validation | 价值验证 | 复盘（效果分析+迭代规划）、反馈综合 |
Workflow Stages
| Stage ID | 名称 | 质量门控 | 下阶段 |
|---|---|---|---|
| S0 | Setup | - | S1 |
| S1 | Perception | 市场研究完成 | S2 |
| S2 | Strategy | 定位完成、S2.5 策略确认 | S3 |
| S3 | Design | PRD 完整 | S4 |
| S4 | Delivery | 发布完成 | S5 |
阶段执行顺序：S0 → S1 → S2 → S3 → S4 → S5
Stage 0: Setup
目标：初始化工作流状态和上下文目录
活动：
- 创建
docs/product/.ompm/workflow-state/目录用于工作流快照 - 创建
docs/product/product-package/目录用于完整产品包 - 初始化
docs/product/.ompm/current-workflow.json当前状态文件
输出：
docs/product/.ompm/workflow-state/目录docs/product/product-package/目录docs/product/.ompm/current-workflow.json空模板
质量门控：
- ✅ 目录结构创建完成
- ✅ 状态模板初始化完成
Stage 1: Perception
目标：完成需求感知层的数据收集和分析
本阶段必答问题：背景触发（为什么是现在做这件事）？用户场景（目标用户在什么场景遇到什么问题）？问题证据（什么证据表明这个问题真实且值得解决）？
活动：
- 市场与用户研究 -
market-researchskill - 竞品分析 -
competitive-analysisskill
技能调用：
- Step 1.1: 调用 market-research 技能（市场研究 + 用户研究）
- Step 1.2: 调用 competitive-analysis 技能
输出：
docs/product/.ompm/market-analysis.jsondocs/product/.ompm/user-research.jsondocs/product/.ompm/competitive-analysis.json+docs/product/competitive-analysis/{feature-name}-{date}.md
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 · 642 lines · 111 tokens per session scan A bd5efd301826
full-pm-cycle is a skill published in the GitHub repository kelegele/oh-my-pm (4 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 5,689 once invoked, about $0.0006 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
build-flow
Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it.
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
route-environments
Check Power Platform environment routing status and understand default environment resolution. Use when the user asks about environment routing, developer environments, or new maker landing. Routing is configured in the admin center, not here. NOT for listing flows or managing connections.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.