OpenMAIC Stage Document Map
THU-MAIC/OpenMAIC
Maps the structure of an OpenMAIC stage document so an agent can find the right path, read it and patch quizzes, widgets, actions and project pages without guessing.
Map a product's lifecycle stage and choose between extension, replacement, and retirement plays.
Custom licenceAuto-check passed
Install Product Lifecycle Plays
$ npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills product-lifecycle-plays --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product-lifecycle-plays .claude/skills/product-lifecycle-plays && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "product-lifecycle-plays" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/product-lifecycle-plays into .claude/skills/product-lifecycle-plays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-lifecycle-plays", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/product-lifecycle-playsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills product-lifecycle-plays --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/product-lifecycle-plays .agents/skills/product-lifecycle-plays && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "product-lifecycle-plays" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/product-lifecycle-plays into .agents/skills/product-lifecycle-plays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-lifecycle-plays", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills product-lifecycle-plays --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/product-lifecycle-plays .cursor/skills/product-lifecycle-plays && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "product-lifecycle-plays" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/product-lifecycle-plays into .cursor/skills/product-lifecycle-plays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-lifecycle-plays", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/deanpeters/Product-Manager-Skills.git --path skills/product-lifecycle-plays--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills product-lifecycle-plays --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/product-lifecycle-plays .gemini/skills/product-lifecycle-plays && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "product-lifecycle-plays" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/product-lifecycle-plays into .gemini/skills/product-lifecycle-plays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-lifecycle-plays", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install deanpeters/Product-Manager-Skills product-lifecycle-playsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/product-lifecycle-plays .github/skills/product-lifecycle-plays && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "product-lifecycle-plays" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/product-lifecycle-plays into .github/skills/product-lifecycle-plays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-lifecycle-plays", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deanpeters/Product-Manager-Skills product-lifecycle-plays --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/product-lifecycle-plays .opencode/skills/product-lifecycle-plays && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "product-lifecycle-plays" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/product-lifecycle-plays into .opencode/skills/product-lifecycle-plays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-lifecycle-plays", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
product-lifecycle-plays- GitHub stars
- 7.2k
- Token cost
- ~4.2k tokens
- SKILL.md length
- 2,200 words
- Files
- 4
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Map a product's lifecycle stage and choose between extension, replacement, and retirement plays.
- Works in 6 steps: Diagnose the stage → Identify what's driving the pressure → Test the extension play first → …
- A product is maturing
- SKILL.md covers Purpose, Input, Key Concepts and Application, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Product Lifecycle Plays is an agent skill from deanpeters/Product-Manager-Skills. Map a product's lifecycle stage and choose between extension, replacement, and retirement plays. Use when a product is maturing or declining and the next move isn't obvious.
Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `examples/sample-industrial.md`, `examples/sample.md` and `template.md`).
The repository describes itself as: Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.
When your agent uses it
- A product is maturing
- Declining and the next move isnt obvious
Example prompts
- “/product-lifecycle-plays”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Diagnose the stage
- Identify what's driving the pressure
- Test the extension play first
- If replacing, build the risk register before committing
- If retiring, hand off
- Run it across the line
What it can do on your machine
Read from SKILL.md and the folder at commit 1b5a524. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Product Lifecycle Plays loads about 4.2k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 2,200 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,200 words (~4,214 tokens).
“Decide what to do with a product that has stopped growing. There are three plays — extend, replace, retire — and picking the wrong one is expensive in a different way each time. This skill gives you the stage diagnosis…”
- name
- product-lifecycle-plays
- argument-hint
- [product or product line, and the signal that something needs to change]
- intent
- Diagnose where a product sits in the Product Life Cycle and choose deliberately among the three plays available at the decline inflection — extend the…
- type
- component
- theme
- product-lifecycle
- best_for
- Deciding whether a fading product should be extended, replaced, or retired, Diagnosing whether a product has actually crossed from mature into decline…
- scenarios
- Revenue is flattening on our flagship and people are arguing about a rewrite versus a refresh, We have four aging SKUs and no consistent way to decide what…
- estimated_time
- 25-45 min
Files
SKILL.md and 3 other files in skills/product-lifecycle-plays of deanpeters/Product-Manager-Skills.
- SKILL.md
- examples/sample-industrial.md
- examples/sample.md
- template.md
Open the folder on GitHubat commit 1b5a524
Compare with similar skills
Product Lifecycle Plays next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Product Lifecycle Plays this skilldeanpeters/Product-Manager-Skills | 7.2k | — | ~4.2k | Automated safety check: Pass | Custom licence | |
| OpenMAIC Stage Document MapTHU-MAIC/OpenMAIC | 40k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Hunk Extension Authoring Mapmodem-dev/hunk | 9.6k | — | ~5.8k | Automated safety check: Pass | MIT | |
| Token Mapnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Browser Extension Buildersickn33/agentic-awesome-skills | 47k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Browser Extension Launchsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Hunk Extension Authoring Map
modem-dev/hunk
Maps the hunkdiff/extension API for building Hunk terminal diff viewer extensions: panes, file views, commands, dialogs, themes, VCS backends and lifecycle events.
Token Map
nexu-io/open-design
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
Browser Extension Builder
sickn33/agentic-awesome-skills
Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions.
Browser Extension Launch
sickn33/agentic-awesome-skills
Builds, tests, packages, and prepares Chrome extensions for store launch from a plain-language idea; use for new extensions, fixes, releases, and submission recovery.
Browser Extension Reverse
sickn33/agentic-awesome-skills
Authorized reverse engineering of Chrome/Firefox extensions: manifest analysis, background workers, content scripts, and extension-based credential or data-exposure research.
More from deanpeters/Product-Manager-Skills
All 75 skills in this repoUser Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
TAM SAM SOM Calculator
deanpeters/Product-Manager-Skills
Calculates total, serviceable available and serviceable obtainable market size for a product idea with explicit assumptions, methods and caveats.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Questions about Product Lifecycle Plays
What does Product Lifecycle Plays do?
Map a product's lifecycle stage and choose between extension, replacement, and retirement plays. Product Lifecycle Plays is an agent skill from deanpeters/Product-Manager-Skills. Map a product's lifecycle stage and choose between extension, replacement, and retirement plays.
When should I use Product Lifecycle Plays?
Product Lifecycle Plays fits situations like: A product is maturing; declining and the next move isnt obvious.
How do I install Product Lifecycle Plays in Claude Code?
Run `npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a claude-code`. Or copy the skill folder (skills/product-lifecycle-plays in deanpeters/Product-Manager-Skills) into .claude/skills/product-lifecycle-plays in your project. Claude Code loads it when a task matches its description.
How do I install Product Lifecycle Plays in Codex?
Run `npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a codex`. Or copy the skill folder (skills/product-lifecycle-plays in deanpeters/Product-Manager-Skills) into .agents/skills/product-lifecycle-plays in your project. Codex loads it when a task matches its description.
Can I use Product Lifecycle Plays in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deanpeters/Product-Manager-Skills --skill product-lifecycle-plays -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-lifecycle-plays, .gemini/skills/product-lifecycle-plays, .github/skills/product-lifecycle-plays and .opencode/skills/product-lifecycle-plays in your project.
What does Product Lifecycle Plays need to run?
SKILL.md names no scripts, command-line tools or credentials: Product Lifecycle Plays is instructions for the agent only.
Does Product Lifecycle Plays access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Product Lifecycle Plays safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Product Lifecycle Plays use?
Product Lifecycle Plays has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Product Lifecycle Plays use?
About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Product Lifecycle Plays?
Skills that share tags, products or a category with Product Lifecycle Plays: OpenMAIC Stage Document Map (THU-MAIC/OpenMAIC, 40k stars), Hunk Extension Authoring Map (modem-dev/hunk, 9.6k stars), Token Map (nexu-io/open-design, 100k stars) and Browser Extension Builder (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Product Lifecycle Plays?
deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,224 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 1, 2026.
Source: deanpeters/Product-Manager-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.