@juancr11/sibu 0.5.1 → 0.5.3

package/package.json

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

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "templateVersion": "52",
+  "templateVersion": "55",
   "templates": {
     "AGENTS.md": {
       "version": "22",
@@ -38,24 +38,24 @@
       ]
     },
     "skills/product-vision-writer/SKILL.md": {
-      "version": "4",
+      "version": "5",
       "description": "Mandatory product vision writer skill installed once at the shared .agents/skills workspace path.",
       "changes": [
-        "Compresses discovery and drafting guidance while preserving one-question-at-a-time discovery, output location, incomplete-input handling, and product-vision quality expectations."
+        "Strengthens final response rules so saved product visions report only the path unless inline review is explicitly requested."
       ]
     },
     "skills/feature-brief-writer/SKILL.md": {
-      "version": "3",
+      "version": "4",
       "description": "Mandatory feature brief writer skill installed once at the shared .agents/skills workspace path.",
       "changes": [
-        "Compresses feature-brief guidance while preserving product-vision grounding, vague-request stop behavior, minimum context requirements, and feature brief output location."
+        "Strengthens final response rules so saved feature briefs report only the path unless inline review is explicitly requested."
       ]
     },
     "skills/technical-design-writer/SKILL.md": {
-      "version": "11",
+      "version": "12",
       "description": "Mandatory technical design writer skill installed once at the shared .agents/skills workspace path.",
       "changes": [
-        "Tightens final responses so technical design updates report only the output path unless inline review is requested."
+        "Strengthens final response rules so saved technical designs report only the path and never include excerpts unless inline review is explicitly requested."
       ]
     },
     "skills/typescript/SKILL.md": {
@@ -101,24 +101,24 @@
       ]
     },
     "skills/scrum-master-planner/SKILL.md": {
-      "version": "4",
+      "version": "5",
       "description": "Mandatory Scrum planner skill for creating pragmatic Epics and User Stories from approved feature and technical design docs.",
       "changes": [
-        "Compresses Scrum planning guidance while preserving required inputs, pragmatic story splitting, output paths, sequencing rules, and UX mockup binding."
+        "Strengthens final response rules so generated Epics and Stories are summarized by paths and counts, not pasted inline unless explicitly requested."
       ]
     },
     "skills/ai-implementation-planner/SKILL.md": {
-      "version": "6",
+      "version": "7",
       "description": "Mandatory AI implementation planner skill for turning one approved User Story into small, story-local implementation step files.",
       "changes": [
-        "Compresses implementation-planning guidance while preserving exact story input requirements, source context, output path conventions, step-file format, and plan-quality checks."
+        "Strengthens final response rules so generated implementation step files are listed by path, not pasted inline unless explicitly requested."
       ]
     },
     "skills/ai-implementation-plan-executor/SKILL.md": {
-      "version": "10",
+      "version": "12",
       "description": "Mandatory AI implementation plan executor skill for implementing existing story implementation plans one reviewed step at a time.",
       "changes": [
-        "Clarifies step-completion reports so agents say the step finished and identify the next step before waiting for approval."
+        "Clarifies focused approved-step commits and validation-only step reporting."
       ]
     },
     "skills/ai-prompt-engineer-master/SKILL.md": {
@@ -129,10 +129,10 @@
       ]
     },
     "skills/ux-expert/SKILL.md": {
-      "version": "3",
+      "version": "4",
       "description": "Selectable UX expert skill for UI-changing features, responsive design, flows, states, accessibility, and binding mockups.",
       "changes": [
-        "Tightens final responses so UX spec updates report only the output path unless inline review is requested."
+        "Strengthens final response rules so saved UX specs report only the path and never include mockups or excerpts unless inline review is explicitly requested."
       ]
     }
   }

package/templates/skills/ai-implementation-plan-executor/SKILL.md

@@ -119,7 +119,11 @@ When the user explicitly approves the current step, update that step file by add
 - Approved at: <ISO-8601 timestamp>
 ```
 
-Before writing the approval marker, identify the current Git user with `git config user.name`; if it is unavailable, use `git config user.email`. Use that value for `Approved by`. After writing the approval marker, commit all changes for the approved step before continuing. Use a Conventional Commits 1.0.0 message that describes the completed step. If the commit fails, stop and report the failure instead of continuing.
+Before writing the approval marker, identify the current Git user with `git config user.name`; if it is unavailable, use `git config user.email`. Use that value for `Approved by`.
+
+After writing the approval marker, commit only the changes produced by the approved step before continuing. The commit must include the step file approval marker and files intentionally changed while implementing that step. It must not include unrelated local edits, pre-existing worktree changes, or changes from other steps. Use the files tracked during step execution and a focused `git status --short` check to stage the correct paths. Do not run broad `git diff` investigations or other "what changed?" archaeology unless it is required to avoid committing unrelated changes and the user has approved that extra inspection.
+
+Use a Conventional Commits 1.0.0 message that describes the completed step. If the commit fails, stop and report the failure instead of continuing.
 
 Then continue with the next unapproved step immediately, without asking for another pre-implementation confirmation, only after the approval marker is written and the approved step changes are committed.
 
@@ -162,6 +166,7 @@ Do not:
 After implementing one step, briefly report:
 
 - that the step finished
+- if the step was validation-only and produced no code changes, say that it was just a validation step and all validations passed
 - current step file path
 - the next step file path, or that no next step remains
 - that you are waiting for user approval before marking the step approved, committing it, and continuing to the next step

package/templates/skills/ai-implementation-planner/SKILL.md

@@ -204,11 +204,11 @@ Before finishing, verify:
 
 ## Final response behavior
 
-After writing the files, briefly report:
+After writing the files, final-answer with only:
 
 - the implementation plan folder path
 - the step file paths created
 - the source User Story path
 - any risks or stop conditions captured in the step files
 
-Do not paste the full step files unless the user asks to review them inline.
+Do not paste step-file bodies, excerpts, outlines, task text, done conditions, or section summaries. Only include generated step files when the user explicitly asks for inline review in the current request.

package/templates/skills/feature-brief-writer/SKILL.md

@@ -210,6 +210,6 @@ When shaping a feature brief, prefer:
 
 ## Final response behavior
 
-After writing the file, briefly report the path that was created or updated. Include the full feature brief in the response only if the user asks to review it inline.
+After writing the file, final-answer with only the path created or updated. Do not paste the feature brief body, excerpt, outline, or section summaries.
 
-If file writes are unavailable, provide the Markdown content and state that it is intended for `docs/features/<feature-slug>/feature_brief.md`.
+Only include the full feature brief when the user explicitly asks for inline review in the current request. If file writes are unavailable, provide the Markdown content and state that it is intended for `docs/features/<feature-slug>/feature_brief.md`.

package/templates/skills/product-vision-writer/SKILL.md

@@ -111,6 +111,6 @@ If the user explicitly requests a different path, use that path instead.
 
 ### 7. Final response behavior
 
-After writing the file, briefly report the path that was created or updated. Include the full document in the response only if the user asks to review it inline.
+After writing the file, final-answer with only the path created or updated. Do not paste the document body, excerpt, outline, or section summaries.
 
-If file writes are unavailable, provide the Markdown content and state that it is intended for `docs/product-vision.md`.
+Only include the full document when the user explicitly asks for inline review in the current request. If file writes are unavailable, provide the Markdown content and state that it is intended for `docs/product-vision.md`.

package/templates/skills/scrum-master-planner/SKILL.md

@@ -183,10 +183,10 @@ Before finishing, verify:
 
 ## Final response behavior
 
-After writing files, briefly report:
+After writing files, final-answer with only:
 
 - the Epic directories created or updated
 - the number of Epics and User Stories
 - any source-scope items intentionally left unresolved or captured as risks
 
-Do not paste all generated artifacts unless the user asks to review them inline.
+Do not paste artifact bodies, excerpts, outlines, story text, acceptance criteria, or section summaries. Only include generated artifacts when the user explicitly asks for inline review in the current request.

package/templates/skills/technical-design-writer/SKILL.md

@@ -113,4 +113,6 @@ A good technical design is short, specific, and useful. It should not try to be
 
 ## Final response behavior
 
-After writing the file, report only the path. Do not paste the full technical design unless the user asks to review it inline.
+After writing the file, final-answer with only the path created or updated. Do not paste the technical design body, excerpt, outline, or section summaries.
+
+Only include the full technical design when the user explicitly asks for inline review in the current request.

package/templates/skills/ux-expert/SKILL.md

@@ -92,4 +92,6 @@ The Binding Mockups section is authoritative for downstream work unless this UX
 
 ## Final response behavior
 
-After writing the file, report only the path. Do not paste the full UX spec unless the user asks to review it inline.
+After writing the file, final-answer with only the path created or updated. Do not paste the UX spec body, excerpt, outline, mockups, or section summaries.
+
+Only include the full UX spec when the user explicitly asks for inline review in the current request.