Utility Pm Workflow Orchestrator
product-on-purpose/pm-skills
Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step.
Create a phased activation plan using the EvoNexus standard structure — single index file + folder-per-phase + file-per-item, each item detailed with owner, dependencies, decisions pending…
Install Prod Activation Plan
$ npx skills add evolution-foundation/evo-nexus --skill prod-activation-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install evolution-foundation/evo-nexus prod-activation-plan --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/evolution-foundation/evo-nexus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prod-activation-plan .claude/skills/prod-activation-plan && 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 "prod-activation-plan" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/prod-activation-plan into .claude/skills/prod-activation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prod-activation-plan", 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/evolution-foundation/evo-nexus/tree/main/.claude/skills/prod-activation-planType 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 evolution-foundation/evo-nexus --skill prod-activation-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install evolution-foundation/evo-nexus prod-activation-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/prod-activation-plan .agents/skills/prod-activation-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prod-activation-plan" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/prod-activation-plan into .agents/skills/prod-activation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prod-activation-plan", 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 evolution-foundation/evo-nexus --skill prod-activation-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install evolution-foundation/evo-nexus prod-activation-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/prod-activation-plan .cursor/skills/prod-activation-plan && 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 "prod-activation-plan" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/prod-activation-plan into .cursor/skills/prod-activation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prod-activation-plan", 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/evolution-foundation/evo-nexus.git --path .claude/skills/prod-activation-plan--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 evolution-foundation/evo-nexus --skill prod-activation-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install evolution-foundation/evo-nexus prod-activation-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/prod-activation-plan .gemini/skills/prod-activation-plan && 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 "prod-activation-plan" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/prod-activation-plan into .gemini/skills/prod-activation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prod-activation-plan", 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 evolution-foundation/evo-nexus prod-activation-planInstalls 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 evolution-foundation/evo-nexus --skill prod-activation-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/prod-activation-plan .github/skills/prod-activation-plan && 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 "prod-activation-plan" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/prod-activation-plan into .github/skills/prod-activation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prod-activation-plan", 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 evolution-foundation/evo-nexus --skill prod-activation-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install evolution-foundation/evo-nexus prod-activation-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/prod-activation-plan .opencode/skills/prod-activation-plan && 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 "prod-activation-plan" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/prod-activation-plan into .opencode/skills/prod-activation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prod-activation-plan", 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
prod-activation-plan- GitHub stars
- 545
- Token cost
- ~2.9k tokens
- SKILL.md length
- 843 words
- Files
- 1
- Skills in repo
- 117
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Create a phased activation plan using the EvoNexus standard structure — single index file + folder-per-phase + file-per-item, each item detailed with owner, dependencies, decisions pending…
- Works in 5 steps: Create the folder structure → Write the INDEX file → Write one file per item → …
- The user asks for an activation plan
- SKILL.md covers When to use, What this skill does NOT do, Inputs required and Standard structure, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Prod Activation Plan is an agent skill from evolution-foundation/evo-nexus. Create a phased activation plan using the EvoNexus standard structure — single index file + folder-per-phase + file-per-item, each item detailed with owner, dependencies, decisions pending, suggested agent team. Use when the user asks for an activation plan, implementation plan, rollout plan, or any phased plan for business/engineering initiatives. Also triggered by Oracle's Step 6 (implementation plan delivery) instead of writing an ad-hoc plan.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Planning and Feature launches and release readiness. The repository describes itself as: The open source operating system for AI-powered businesses.
When your agent uses it
- The user asks for an activation plan
- Implementation plan
- Any phased plan for business/engineering initiatives
Example prompts
- “/prod-activation-plan”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Create the folder structure
- Write the INDEX file
- Write one file per item
- Agent routing rules (for the "Agente sugerido" section)
- Report back
What it can do on your machine
Read from SKILL.md and the folder at commit 7f5dd76. 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 (its code samples are markdown and bash).
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
Prod Activation Plan loads about 2.9k tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 843 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 843 words (~2,896 tokens).
“This skill creates a phased activation plan using the EvoNexus standard structure that has been battle-tested: a single index file at the top, folders per phase, one file per item with a rich template. Every file declares its owner agent…”
- name
- prod-activation-plan
Files
Just SKILL.md in .claude/skills/prod-activation-plan of evolution-foundation/evo-nexus.
Open the folder on GitHubat commit 7f5dd76
Compare with similar skills
Prod Activation Plan 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 |
|---|---|---|---|---|---|---|
| Prod Activation Plan this skillevolution-foundation/evo-nexus | 545 | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Utility Pm Workflow Orchestratorproduct-on-purpose/pm-skills | 715 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Agent Workflowmenkesu/awesome-pm-skills | 429 | — | ~5.2k | Automated safety check: Pass | Custom licence | |
| Rfc Writermohitagw15856/pm-claude-skills | 1.4k | — | ~4.1k | Automated safety check: Pass | MIT | |
| SpikeDeL-TaiseiOzaki/claude-code-orchestra | 199 | — | ~6.9k | Automated safety check: Pass | MIT | |
| Todos Reviewhanamizuki/solopreneur | 152 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Agent Workflow
menkesu/awesome-pm-skills
Sets up how you and your team build and work with AI agents, and produces an Agent Workflow Charter (agent lanes, plan-mode loop, autonomy ladder with promotion criteria, rules file, review policy…
Rfc Writer
mohitagw15856/pm-claude-skills
Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach.
Spike
DeL-TaiseiOzaki/claude-code-orchestra
Time-boxed technical investigation/feasibility study with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams).
Todos Review
hanamizuki/solopreneur
Deep-review a single todo or backlog item to decide whether it is worth building: problem clarity, solution quality, and implementation priority.
Refactor Design Report
penwyp/ClaudePreference
Produce a professional, code-grounded refactor or implementation design report from identified technical problems, product gaps, review findings, architecture concerns, or frontend-backend contract…
More from evolution-foundation/evo-nexus
All 117 skills in this repoAI Image Creator
evolution-foundation/evo-nexus
Generates PNG images through OpenRouter models, with transparent backgrounds and reference-image edits, and describes existing images with multimodal vision.
MongoDB Query Client
evolution-foundation/evo-nexus
Runs read-only MongoDB finds, aggregations and collection listings against databases named in your .env, choosing the connection by label or index.
MySQL and MariaDB Query Tool
evolution-foundation/evo-nexus
Queries MySQL or MariaDB databases declared in .env by label, read-only by default unless a connection explicitly allows writes.
Postgres Query Client
evolution-foundation/evo-nexus
Runs read-only SQL queries and schema exploration against PostgreSQL databases declared in .env, chosen by label or index, with writes blocked unless a connection allows them.
Redis Inspector
evolution-foundation/evo-nexus
Reads keys and server state from Redis instances configured in .env through a read-only Python client, choosing connections by label or index.
Int Bling
evolution-foundation/evo-nexus
Bling ERP integration via API v3. An agent skill from evolution-foundation/evo-nexus.
Related
Categories
Questions about Prod Activation Plan
What does Prod Activation Plan do?
Create a phased activation plan using the EvoNexus standard structure — single index file + folder-per-phase + file-per-item, each item detailed with owner, dependencies, decisions pending…. Prod Activation Plan is an agent skill from evolution-foundation/evo-nexus. Create a phased activation plan using the EvoNexus standard structure — single index file + folder-per-phase + file-per-item, each item detailed with owner, dependencies, decisions pending, suggested agent team.
When should I use Prod Activation Plan?
Prod Activation Plan fits situations like: the user asks for an activation plan; implementation plan; any phased plan for business/engineering initiatives.
How do I install Prod Activation Plan in Claude Code?
Run `npx skills add evolution-foundation/evo-nexus --skill prod-activation-plan -a claude-code`. Or copy the skill folder (.claude/skills/prod-activation-plan in evolution-foundation/evo-nexus) into .claude/skills/prod-activation-plan in your project. Claude Code loads it when a task matches its description.
How do I install Prod Activation Plan in Codex?
Run `npx skills add evolution-foundation/evo-nexus --skill prod-activation-plan -a codex`. Or copy the skill folder (.claude/skills/prod-activation-plan in evolution-foundation/evo-nexus) into .agents/skills/prod-activation-plan in your project. Codex loads it when a task matches its description.
Can I use Prod Activation Plan 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 evolution-foundation/evo-nexus --skill prod-activation-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prod-activation-plan, .gemini/skills/prod-activation-plan, .github/skills/prod-activation-plan and .opencode/skills/prod-activation-plan in your project.
What does Prod Activation Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Prod Activation Plan is instructions for the agent only.
Does Prod Activation Plan 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 Prod Activation Plan 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 Prod Activation Plan use?
Prod Activation Plan 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 Prod Activation Plan use?
About 2.9k 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 Prod Activation Plan?
Skills that share tags, products or a category with Prod Activation Plan: Utility Pm Workflow Orchestrator (product-on-purpose/pm-skills, 715 stars), Agent Workflow (menkesu/awesome-pm-skills, 429 stars), Rfc Writer (mohitagw15856/pm-claude-skills, 1.4k stars) and Spike (DeL-TaiseiOzaki/claude-code-orchestra, 199 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prod Activation Plan?
evolution-foundation (a GitHub organization) maintains it in evolution-foundation/evo-nexus, which has 545 GitHub stars. The repository holds 117 skills in this directory. The repository was last updated on May 13, 2026.
Source: evolution-foundation/evo-nexus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.