@starlein/paperclip-plugin-company-wizard 0.4.5 → 0.4.7

package/templates/roles/game-designer/role.meta.json

@@ -10,5 +10,8 @@
     "Takes over game-design from Engineer/CEO (they become fallback)",
     "Takes over user-testing with playtesting focus (engagement, fun, difficulty)",
     "Adds gameplay review pass when pr-review module is active"
-  ]
+  ],
+  "adapter": {
+    "thinkingLevel": "auto"
+  }
 }

package/templates/roles/level-designer/role.meta.json

@@ -9,5 +9,8 @@
   "enhances": [
     "Takes over level-specific design from Game Designer/Engineer",
     "Contributes difficulty curve and pacing data to game balancing"
-  ]
+  ],
+  "adapter": {
+    "thinkingLevel": "auto"
+  }
 }

package/templates/roles/product-owner/AGENTS.md

@@ -9,6 +9,7 @@ You own product intent, backlog health, acceptance criteria, prioritization, and
 ## Working Rules
 
 - Work only on issues assigned to you or explicitly handed to you in comments.
+- If an issue is assigned to you in `in_review` and no formal executionPolicy participant is waiting, review it immediately against the acceptance criteria, branch/commit/PR evidence, and recorded verification. If it passes, comment with the acceptance decision and set it `done`; if it does not pass, set it back to `in_progress`, assign it to the Engineer, and list the exact required changes.
 - Start actionable work in the same heartbeat; do not stop at a plan unless planning was requested. Leave durable progress with a clear next action. Use child issues for long or parallel delegated work instead of polling. Mark blocked work with owner and action. Respect budget, pause/cancel, approval gates, and company boundaries.
 - Keep issues small, acceptance-driven, project-scoped, and linked to goals when available.
 - Use first-class blockers (`blockedByIssueIds`) for dependencies instead of free-text "blocked by" notes.
@@ -18,7 +19,7 @@ You own product intent, backlog health, acceptance criteria, prioritization, and
 ## Collaboration and Handoffs
 
 - Product ambiguity -> clarify options and recommend one.
-- Engineering implementation -> assign the Engineer with acceptance criteria and project/goal context.
+- Engineering implementation -> assign the Engineer directly with acceptance criteria and project/goal context. Do not leave ready engineering work unassigned for a later sweep.
 - UX-visible scope -> involve the UI/UX designer.
 - Security-sensitive scope -> involve the Security Engineer.
 - Browser/user-facing verification -> involve QA.

package/templates/roles/product-owner/HEARTBEAT.md

@@ -35,7 +35,7 @@ Run this checklist on every heartbeat. The Paperclip skill is the source of trut
 - Upload or attach user-inspectable outputs as work products/artifacts/documents; local filesystem paths alone are not enough.
 - Use issue documents for long plans, specs, QA reports, security reviews, or hiring drafts; comments should summarize and link.
 - Handoffs should use assignment/status/executionPolicy and a concrete next action. Do not rely on generic @-mentions.
-- If work awaits review, move the issue to `in_review` and follow its executionPolicy.
+- If an issue is assigned to you in `in_review` and no formal executionPolicy participant is waiting, review it immediately against the acceptance criteria. If it passes, comment with the acceptance decision and set it `done`; if it does not pass, set it back to `in_progress`, assign it to the Engineer, and list the exact required changes.
 
 ## 6. Exit
 

package/templates/roles/product-owner/role.meta.json

@@ -10,5 +10,8 @@
     "Takes over backlog health from CEO (CEO becomes fallback)",
     "Takes over auto-assign from CEO (CEO becomes fallback)",
     "Adds product-alignment review pass when pr-review module is active"
-  ]
+  ],
+  "adapter": {
+    "thinkingLevel": "auto"
+  }
 }

package/templates/roles/qa/role.meta.json

@@ -12,6 +12,7 @@
     "Contributes test coverage requirements to architecture-plan"
   ],
   "adapter": {
-    "model": "claude-sonnet-4-6"
+    "model": "claude-sonnet-4-6",
+    "thinkingLevel": "auto"
   }
 }

package/templates/roles/security-engineer/role.meta.json

@@ -12,6 +12,7 @@
     "Contributes threat model to architecture-plan"
   ],
   "adapter": {
-    "model": "claude-sonnet-4-6"
+    "model": "claude-sonnet-4-6",
+    "thinkingLevel": "auto"
   }
 }

package/templates/roles/technical-writer/role.meta.json

@@ -11,6 +11,7 @@
     "Adds documentation review pass when pr-review module is active"
   ],
   "adapter": {
-    "model": "claude-sonnet-4-6"
+    "model": "claude-sonnet-4-6",
+    "thinkingLevel": "auto"
   }
 }

package/templates/roles/ui-designer/role.meta.json

@@ -7,7 +7,8 @@
   "description": "Owns visual identity, UI design systems, and brand consistency. Creates design specs that engineers implement.",
   "reportsTo": "ceo",
   "adapter": {
-    "chrome": true
+    "chrome": true,
+    "thinkingLevel": "auto"
   },
   "enhances": [
     "Takes over architecture-plan visual/UI layer from Engineer (Engineer becomes fallback for UI architecture)",

package/templates/roles/ux-researcher/role.meta.json

@@ -10,5 +10,8 @@
     "Takes over market-analysis user research section from Product Owner/CEO",
     "Takes over vision-workshop success metrics validation from CEO",
     "Adds UX review pass when pr-review module is active"
-  ]
+  ],
+  "adapter": {
+    "thinkingLevel": "auto"
+  }
 }