@juancr11/sibu 0.17.1 → 0.18.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@juancr11/sibu",
-  "version": "0.17.1",
+  "version": "0.18.0",
   "description": "CLI for setting up a local AI-augmented development workflow.",
   "repository": {
     "type": "git",

package/templates/AGENTS.md

@@ -35,6 +35,14 @@ Keep responses concise by default, but spend the context needed for correctness,
 - Ask focused questions when needed; otherwise make reasonable assumptions and proceed.
 - If the user wants more detail, they can ask follow-up questions.
 
+## Judgment and honesty
+
+- Be direct and respectful. Avoid patronizing praise, performative agreement, and over-reassurance.
+- Do not invent certainty or provide a polished answer when important context is missing; state uncertainty, ask one focused question, or verify first.
+- Make low-risk assumptions only when they are clearly labeled.
+- Challenge the user when there is a clear factual, safety/security, engineering-quality, repo-instruction, product-goal, or context-reliability reason.
+- When challenging, give a short reason and a better alternative. Do not argue preferences or nitpick style; preserve user control after material tradeoffs are acknowledged unless safety or project rules require refusal.
+
 ## Skill routing
 
 For planned product/feature work, use this pipeline: product vision -> business domain model -> capabilities map -> deep module map / feature brief -> technical design -> optional UX -> epics/stories -> AI executor. Business Domain Model work sits after Product Vision and before the Capabilities Map. Deep Module Map and Feature Brief work are sibling downstream artifacts from Product Vision, Business Domain Model, and Capabilities Map. Technical Design remains downstream of both Feature Brief and Deep Module Map, with Scrum planning and AI executor flows after Technical Design. Narrow code fixes and small local changes do not require the full pipeline unless product scope, module ownership, or architecture direction is unclear.

package/templates/manifest.json

@@ -1,12 +1,13 @@
 {
-  "templateVersion": "132",
+  "templateVersion": "133",
   "templates": {
     "AGENTS.md": {
-      "version": "33",
+      "version": "34",
       "description": "Project-level agent instructions and Sibu maintenance guidance.",
       "changes": [
-        "Adds the Capabilities Map as a formal pipeline stage before sibling Deep Module Map and Feature Brief work.",
-        "Routes capability map, capability coverage, missing capability, and capability gap requests to capabilities-map-writer."
+        "Adds judgment and honesty guidance for direct, non-condescending collaboration.",
+        "Clarifies that agents should state uncertainty, ask focused questions, or verify instead of inventing certainty.",
+        "Defines when agents should challenge users for clear factual, safety, quality, instruction, product, or context-reliability reasons."
       ]
     },
     ".codex/config.toml": {