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.
SkillScore91Maintained
Automatic
◆Project Management pack
Last verified 8/19/2026
What it changes
Passed 20 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill91%
Checks it passed that the model alone missed
The index filename starts with the [C] prefix.
The index YAML frontmatter includes mode: index.
Item frontmatter specifies type: work-plan-item.
and 20 more in the full report
16 fixed4 passed either way2 still failing0 broke
Pass-rate lift
+73 pp
Tokens
+110%
Agent turns
0%
Response time
-25%
Model gemini-3.6-flashMeasured 8/19/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
Escreva o cabeçalho YAML frontmatter do arquivo de índice do plano portal-v2-activation data 2025-04-10.
What was checked, without and with the skill
Checked
Without skill
With skill
The index YAML frontmatter includes type: work-plan-index.
Missed
Passed
The index YAML frontmatter includes mode: index.
Missed
Passed
case-10 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md338 linessingle file
Activation Plan — Standard Structure
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, decisions pending, dependencies, and suggested implementation team. Oracle uses this skill instead of inventing a plan structure.
Always respond in the user's language (default: pt-BR if the workspace is pt-BR).
When to use
Oracle's Step 6 (implementation plan delivery) — the canonical trigger
User asks for an "activation plan", "implementation plan", "rollout plan", "plano de ativação"
Expanding an existing plan with new axes/pillars (extend, don't duplicate)
Any multi-phase initiative that needs per-item isolation and discussion
What this skill does NOT do
It does NOT do business discovery — that's Oracle's Step 2
It does NOT pick features out of thin air — you must already have the phases and items decided (ideally from Compass)
It does NOT execute the plan — it only creates the structured artifacts
It does NOT overwrite existing plans without explicit confirmation
Inputs required
Before invoking this skill, you must have:
Plan name — short slug (ex: oracle-implementation-plan-expanded)
Plan date — YYYY-MM-DD
Context — 2-3 lines about the business and the strategy base (e.g., "Evolution API, 7 axes, Cycle 52 as strategy base")