You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**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
129
135
130
136
Invoke **@compass-planner** with a self-contained brief:
131
137
- Business profile (from Step 2)
132
138
- Prioritized pain points (after user alignment in Step 5)
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).
142
162
143
-
Each phase must have: objetivo, ações concretas, checklist de configuração, critérios de sucesso, riscos.
163
+
#### Step 6c — Handle plan expansions
144
164
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.
146
166
147
167
### Step 7 — Deliver the plan + offer autonomy paths
0 commit comments