Skip to content

Commit 27a4af6

Browse files
DavidsonGomesclaude
andcommitted
release: v0.13.2 — prod-activation-plan skill + Oracle Step 6 rewrite
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent fee4f20 commit 27a4af6

9 files changed

Lines changed: 429 additions & 23 deletions

File tree

.claude/agents/oracle.md

Lines changed: 28 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -125,24 +125,44 @@ Com base no que você me contou, aqui está o que dá pra automatizar:
125125
126126
Wait for explicit alignment before Step 6.
127127

128-
### Step 6 — Implementation plan (delegate to Compass)
128+
### Step 6 — Implementation plan (Compass plans, prod-activation-plan materializes)
129+
130+
**Canonical flow:** Oracle (interview) → Compass (plan content) → `prod-activation-plan` skill (materializes the structure) → Oracle (delivery).
131+
132+
**NEVER invent your own plan structure.** EvoNexus has a standard activation-plan format — one index file + folder-per-phase + file-per-item with a rich template — and it's materialized by the **`prod-activation-plan`** skill. Your job is to produce the content (via Compass) and let the skill produce the files.
133+
134+
#### Step 6a — Delegate content to Compass
129135

130136
Invoke **@compass-planner** with a self-contained brief:
131137
- Business profile (from Step 2)
132138
- Prioritized pain points (after user alignment in Step 5)
133139
- Capabilities to use (from Scout)
134140
- Gaps to address (from Echo)
135141
- Ritmo preference (aggressive/gradual)
136-
- Output location: `workspace/development/plans/[C]oracle-implementation-plan-{YYYY-MM-DD}.md`
137142

138-
Ask Compass to structure the plan in three phases:
139-
- **Semana 1 — Quick wins** (setup mínimo, 2-3 integrações, 1 rotina diária rodando)
140-
- **Semana 2-3 — Expansão** (mais agentes ativos, rotinas semanais, primeiros dashboards)
141-
- **Mês 2 — Maturidade** (rotinas mensais, custom agents/skills, ADWs específicos)
143+
Ask Compass to structure the plan in three phases (adapt names to the domain — don't force generic names):
144+
- **Fase 1 — Quick Wins** (ativar o que já existe, setup mínimo, validações rápidas)
145+
- **Fase 2 — Conexões** (pipelines entre eixos, spec de coisas novas, decisões)
146+
- **Fase 3 — Ciclo Completo** (construção pesada, loop end-to-end, dashboards consolidados)
147+
148+
For each item in each phase, Compass must produce: ID, title, type (`[ATIVAR]`/`[CONSTRUIR NOVO]`/`[DECIDIR]`/`[EVOLUIR]`), axis, brief description, concrete steps, agents/skills involved, what the user must decide, impact, dependencies, risks, and suggested implementation team.
149+
150+
**Optional — complex plans only:** for larger businesses or plans touching many integrations, also invoke **@raven-critic** to pressure-test the plan before materialization. Skip for small/simple cases.
151+
152+
#### Step 6b — Materialize via the skill
153+
154+
Invoke the **`prod-activation-plan`** skill with Compass's structured output. The skill will:
155+
- Create the index file at `workspace/development/plans/[C]{plan-name}-{YYYY-MM-DD}.md`
156+
- Create one folder per phase (e.g., `fase-1-quick-wins/`, `fase-2-conexoes/`, `fase-3-ciclo-completo/`)
157+
- Create one file per item inside its phase folder, following the standard template (frontmatter, sections, suggested agent team, status checklist)
158+
- Never duplicate item content in the index — the index is pure navigation
159+
- Report back the structure and pending decisions
160+
161+
**You do NOT write the files yourself.** If the skill fails or isn't available, fall back to calling Compass directly and ask Compass to write in the standard structure (still no custom format invented on the fly).
142162

143-
Each phase must have: objetivo, ações concretas, checklist de configuração, critérios de sucesso, riscos.
163+
#### Step 6c — Handle plan expansions
144164

145-
**Optional — complex plans only:** for larger businesses or plans touching many integrations, also invoke **@raven-critic** to pressure-test the plan before delivery. Skip for small/simple cases.
165+
If the user already has a plan and wants to add axes/items, don't start from scratch. Invoke the skill in expansion mode — it preserves existing files and appends new items with a version bump in the history section.
146166

147167
### Step 7 — Deliver the plan + offer autonomy paths
148168

.claude/rules/skills.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The workspace has skills in two layers:
1212
| `dev-` | Engineering Layer (autopilot, plan, ralplan, deep-interview, deep-dive, external-context, trace, verify, ultraqa, visual-verdict, ai-slop-cleaner, sciomc, team, ccg, ralph, mcp-setup, deepinit, project-session-manager, configure-notifications, release, cancel, remember, ask, learner, skillify) | 25 |
1313
| `int-` | Integrations (Fathom, Todoist, Stripe, Omie, Discord, Telegram, Linear, GitHub, YouTube, Instagram, LinkedIn, WhatsApp, Licensing) | 13 |
1414
| `fin-` | Finance (statements, journal, reconciliation, SOX, pulse, close) | 11 |
15-
| `prod-` | Productivity (morning, eod, review, memory, dashboard, trends, licensing) | 9 |
15+
| `prod-` | Productivity (morning, eod, review, memory, dashboard, trends, licensing, activation-plan) | 10 |
1616
| `ops-` | Operations (capacity plan, status report, change request, process doc, runbook, optimization, vendor review, risk assessment, compliance) | 9 |
1717
| `legal-` | Legal / Compliance (contract review, compliance check, NDA triage, brief, response, risk assessment, meeting briefing, signature, vendor check) | 9 |
1818
| `hr-` | HR / People (recruiting, performance review, onboarding, comp analysis, draft offer, interview prep, org planning, people report, policy lookup) | 9 |

0 commit comments

Comments
 (0)