@warpgogol/forge 5.3.2 → 5.3.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@warpgogol/forge",
-  "version": "5.3.2",
+  "version": "5.3.3",
   "private": false,
   "type": "module",
   "license": "Apache-2.0",

package/skills/fo/fo-design-summit/SKILL.md

@@ -34,7 +34,7 @@ See `_shared/fo-pipeline-conventions.md` §Language policy.
 
 A multi-persona design review for complex RFCs. The summit simulates five professional perspectives — Architect, Security Engineer, QA Engineer, Product Manager, and Developer Advocate — to surface issues that a single-perspective review misses. Each persona reviews the RFC from its professional lens and raises concerns. The operator sees all perspectives and makes the final decision.
 
-The summit is **optional** — invoked manually by the operator or suggested by `fo-idea-plan` for RFCs that meet complexity criteria. It is not part of the default pipeline.
+The summit is **optional** — invoked manually by the operator or auto-invoked by `fo-idea-plan` (step 5b) when the planning agent judges multi-perspective review genuinely useful. It is not part of the default pipeline.
 
 The summit is `concern: document-only` — it writes a summit report to `docs/summits/` and does not modify the RFC or any source code.
 
@@ -229,7 +229,7 @@ Do not modify the RFC or any other file. Do not run `/fo-idea-enhance` or `/fo-i
 
 ## Invocation criteria
 
-`fo-design-summit` is invoked explicitly by the operator or suggested by `fo-idea-plan` when the RFC meets **any** of these criteria:
+`fo-design-summit` is invoked explicitly by the operator or auto-invoked by `fo-idea-plan` (step 5b). The criteria below are eligibility gates, not triggers — `fo-idea-plan` runs the summit only when it also judges multi-perspective review genuinely useful, without asking the operator:
 
 - `kind: architecture` AND `scope: workspace`
 - `satisfies[]` includes 2+ DNA invariants
@@ -241,7 +241,7 @@ Do not modify the RFC or any other file. Do not run `/fo-idea-enhance` or `/fo-i
 
 - **RFC not found:** The skill errors if the target RFC does not exist.
 - **Audit not run yet:** The skill proceeds without the audit report — persona findings may overlap with future audit findings. The skill notes this in the report.
-- **RFC is too small for a summit:** If the RFC body is less than 500 words, the skill warns that a summit may be overkill and proceeds only if the operator confirms.
+- **RFC is too small for a summit:** If the RFC body is less than 500 words, the skill warns that a summit may be overkill. When invoked explicitly by the operator, it proceeds only on operator confirmation. When auto-invoked by `fo-idea-plan`, it stops without running — the caller proceeds to its next step.
 - **Persona findings overlap:** Multiple personas may raise the same concern. The synthesis step deduplicates and marks consensus findings.
 
 ## Constraints

package/skills/fo/fo-idea-plan/SKILL.md

@@ -182,15 +182,26 @@ The grilling checks:
 
 Address every concern the grilling raises by revising the draft. Do not persist until the grilling is satisfied.
 
-### 5b. Summit suggestion
+### 5b. Summit decision (autonomous)
 
-If the RFC meets summit criteria (any of: `kind: architecture` AND `scope: workspace`, `satisfies[]` includes 2+ DNA invariants, introduces a new package/command/lifecycle, supersedes an implemented RFC), suggest using `fo-design-summit` before acceptance. Use `ask_user_question`:
+Decide yourself whether to run `fo-design-summit` before persisting the plan. **Do not ask the operator** — the planning agent holds the full context and is best placed to judge. The operator can always request a summit explicitly.
 
-> "This RFC is complex (architecture, workspace scope, 2+ DNA invariants). Should I run a multi-persona design summit before acceptance?"
+Eligibility — the RFC meets **any** of:
 
-Recommended option: "Run summit" — because complex RFCs benefit from multi-perspective review.
+- `kind: architecture` AND `scope: workspace`
+- `satisfies[]` includes 2+ DNA invariants
+- Introduces a new package, command family, or lifecycle
+- Supersedes an implemented RFC
 
-If the operator declines, proceed to step 6. If the operator accepts, invoke `fo-design-summit` via the `skill` tool, wait for it to complete, then proceed to step 6.
+Eligibility alone is not sufficient — most RFCs meet at least one criterion mechanically. Run the summit only when multi-perspective review is likely to surface findings that the audit, enhance, and grilling steps did not:
+
+- The design holds genuinely contested trade-offs or more than one viable architecture.
+- There is cross-cutting risk a single-perspective pass misses (security or privacy surface, migration of already-implemented behavior, multi-workspace blast radius).
+- Step 3 or the grilling left material questions unresolved.
+
+Skip the summit when the change is additive, follows an established pattern, or the plan converged cleanly — meeting a criterion only technically (e.g. listing 2 DNA invariants on a routine change) is a skip. When in doubt, skip: a missed summit is recoverable, operator attention is not.
+
+If you run it, announce in one line (`Running design summit — <reason>`), invoke `fo-design-summit` via the `skill` tool, wait for it to complete, then proceed to step 6. If you skip, emit one line (`Design summit skipped — <reason>`) and proceed directly to step 6.
 
 ### 6. Persist the plan