Ordered Window Sequencing Mip
benchflow-ai/skillsbench
Permutation and sequencing integer-programming formulations with ordered local-window variables, prefix/suffix continuity, and overlap penalties.
Plan who to talk to about a sunset, in what order, and what each conversation must cover.
Custom licenceAuto-check passed
Install Eol Stakeholder Sequence
$ npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-stakeholder-sequence --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/eol-stakeholder-sequence .claude/skills/eol-stakeholder-sequence && 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 "eol-stakeholder-sequence" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-stakeholder-sequence into .claude/skills/eol-stakeholder-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-stakeholder-sequence", 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/eol-stakeholder-sequenceType 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 eol-stakeholder-sequence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-stakeholder-sequence --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/eol-stakeholder-sequence .agents/skills/eol-stakeholder-sequence && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "eol-stakeholder-sequence" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-stakeholder-sequence into .agents/skills/eol-stakeholder-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-stakeholder-sequence", 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 eol-stakeholder-sequence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-stakeholder-sequence --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/eol-stakeholder-sequence .cursor/skills/eol-stakeholder-sequence && 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 "eol-stakeholder-sequence" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-stakeholder-sequence into .cursor/skills/eol-stakeholder-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-stakeholder-sequence", 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/eol-stakeholder-sequence--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 eol-stakeholder-sequence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills eol-stakeholder-sequence --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/eol-stakeholder-sequence .gemini/skills/eol-stakeholder-sequence && 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 "eol-stakeholder-sequence" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-stakeholder-sequence into .gemini/skills/eol-stakeholder-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-stakeholder-sequence", 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 eol-stakeholder-sequenceInstalls 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 eol-stakeholder-sequence -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/eol-stakeholder-sequence .github/skills/eol-stakeholder-sequence && 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 "eol-stakeholder-sequence" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-stakeholder-sequence into .github/skills/eol-stakeholder-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-stakeholder-sequence", 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 eol-stakeholder-sequence -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 eol-stakeholder-sequence --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/eol-stakeholder-sequence .opencode/skills/eol-stakeholder-sequence && 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 "eol-stakeholder-sequence" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-stakeholder-sequence into .opencode/skills/eol-stakeholder-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eol-stakeholder-sequence", 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
eol-stakeholder-sequence- GitHub stars
- 7.2k
- Token cost
- ~3.1k tokens
- SKILL.md length
- 1,594 words
- Files
- 4
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Plan who to talk to about a sunset, in what order, and what each conversation must cover.
- Works in 5 steps: Set the level → Order the stops → Build each stop → …
- An EOL decision is made and you want the landmines found before the announcement
- SKILL.md covers Purpose, Input, Key Concepts and Application, plus 3 more sections
- Reaches github.com
What it does
Eol Stakeholder Sequence is an agent skill from deanpeters/Product-Manager-Skills. Plan who to talk to about a sunset, in what order, and what each conversation must cover. Use when an EOL decision is made and you want the landmines found before the announcement.
Its SKILL.md is about 3.1k 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
- An EOL decision is made and you want the landmines found before the announcement
Example prompts
- “/eol-stakeholder-sequence”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Set the level
- Order the stops
- Build each stop
- Mark parallel vs. sequential
- Assumptions
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
Hosts in commands or code, which the agent is likely to contact:
github.com
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
Eol Stakeholder Sequence loads about 3.1k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 1,594 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 1,594 words (~3,072 tokens).
“Plan the order of EOL conversations, and what each one must cover. The output is a sequenced list of stops — each with what you need from them, what you owe to them, the red flags to listen for, and…”
- name
- eol-stakeholder-sequence
- argument-hint
- [product being sunset, and who already knows]
- intent
- Plan the order and content of stakeholder conversations for an EOL decision. Encodes the hard-won lesson that EOL engagement has a specific sequence — legal…
- type
- component
- theme
- eol-transition
- best_for
- Sequencing EOL conversations so each one informs the next, Knowing what to ask for and what to commit to at every stop, Finding the objection that would have…
- scenarios
- We're retiring a product and I don't know who to talk to first or what to bring them, Last sunset blew up because Sales had promised things we didn't know…
- estimated_time
- 20-35 min
Files
SKILL.md and 3 other files in skills/eol-stakeholder-sequence 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
Eol Stakeholder Sequence 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 |
|---|---|---|---|---|---|---|
| Eol Stakeholder Sequence this skilldeanpeters/Product-Manager-Skills | 7.2k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Ordered Window Sequencing Mipbenchflow-ai/skillsbench | 1.8k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| CSS Orderthedaviddias/Front-End-Checklist | 74k | — | ~404 | Automated safety check: Pass | MIT | |
| Focus Orderthedaviddias/Front-End-Checklist | 74k | — | ~519 | Automated safety check: Pass | MIT | |
| Heading Orderthedaviddias/Front-End-Checklist | 74k | — | ~452 | Automated safety check: Pass | MIT | |
| Food Orderingasgeirtj/system_prompts_leaks | 69k | — | ~1.4k | Automated safety check: Pass | CC0-1.0 |
Similar skills
CSS Order
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Order CSS files correctly.
Focus Order
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure logical focus order.
Heading Order
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Maintain logical heading order.
Food Ordering
asgeirtj/system_prompts_leaks
Prepare restaurant food orders for delivery or pickup; use for cart, checkout and tracking.
Conference Talk Slides from Papers
Orchestra-Research/AI-Research-SKILLs
Generates Beamer LaTeX PDF and editable PPTX slides from a compiled paper, with speaker notes and an optional talk script, sized to four talk lengths.
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 Eol Stakeholder Sequence
What does Eol Stakeholder Sequence do?
Plan who to talk to about a sunset, in what order, and what each conversation must cover. Eol Stakeholder Sequence is an agent skill from deanpeters/Product-Manager-Skills. Plan who to talk to about a sunset, in what order, and what each conversation must cover.
When should I use Eol Stakeholder Sequence?
Eol Stakeholder Sequence fits situations like: an EOL decision is made and you want the landmines found before the announcement.
How do I install Eol Stakeholder Sequence in Claude Code?
Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a claude-code`. Or copy the skill folder (skills/eol-stakeholder-sequence in deanpeters/Product-Manager-Skills) into .claude/skills/eol-stakeholder-sequence in your project. Claude Code loads it when a task matches its description.
How do I install Eol Stakeholder Sequence in Codex?
Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a codex`. Or copy the skill folder (skills/eol-stakeholder-sequence in deanpeters/Product-Manager-Skills) into .agents/skills/eol-stakeholder-sequence in your project. Codex loads it when a task matches its description.
Can I use Eol Stakeholder Sequence 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 eol-stakeholder-sequence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eol-stakeholder-sequence, .gemini/skills/eol-stakeholder-sequence, .github/skills/eol-stakeholder-sequence and .opencode/skills/eol-stakeholder-sequence in your project.
What does Eol Stakeholder Sequence need to run?
SKILL.md names no scripts, command-line tools or credentials: Eol Stakeholder Sequence is instructions for the agent only.
Does Eol Stakeholder Sequence access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Eol Stakeholder Sequence 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 Eol Stakeholder Sequence use?
Eol Stakeholder Sequence 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 Eol Stakeholder Sequence use?
About 3.1k tokens (SKILL.md is roughly 12k 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 Eol Stakeholder Sequence?
Skills that share tags, products or a category with Eol Stakeholder Sequence: Ordered Window Sequencing Mip (benchflow-ai/skillsbench, 1.8k stars), CSS Order (thedaviddias/Front-End-Checklist, 74k stars), Focus Order (thedaviddias/Front-End-Checklist, 74k stars) and Heading Order (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eol Stakeholder Sequence?
deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,209 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.