create-sdd-project 0.8.5 → 0.8.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-sdd-project",
-  "version": "0.8.5",
+  "version": "0.8.7",
   "description": "Create a new SDD DevFlow project with AI-assisted development workflow",
   "bin": {
     "create-sdd-project": "bin/cli.js"

package/template/.claude/settings.json

@@ -24,6 +24,26 @@
           }
         ]
       }
+    ],
+    "Notification": [
+      {
+        "matcher": "permission_prompt",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "osascript -e 'display notification \"Waiting for approval\" with title \"Claude Code\"' 2>/dev/null || notify-send 'Claude Code' 'Waiting for approval' 2>/dev/null || printf '\\a'"
+          }
+        ]
+      },
+      {
+        "matcher": "idle_prompt",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "osascript -e 'display notification \"Task finished — waiting for input\" with title \"Claude Code\"' 2>/dev/null || notify-send 'Claude Code' 'Task finished — waiting for input' 2>/dev/null || printf '\\a'"
+          }
+        ]
+      }
     ]
   }
 }

package/template/.claude/settings.local.json

@@ -18,38 +18,5 @@
       "Grep"
     ],
     "deny": []
-  },
-  "hooks": {
-    "Notification": [
-      {
-        "matcher": "permission_prompt",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "osascript -e 'display notification \"Permission needed\" with title \"Claude Code\" with subtitle \"Waiting for approval\"'"
-          }
-        ]
-      },
-      {
-        "matcher": "idle_prompt",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "osascript -e 'display notification \"Task finished, waiting for input\" with title \"Claude Code\"'"
-          }
-        ]
-      }
-    ],
-    "Stop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "osascript -e 'display notification \"Response complete\" with title \"Claude Code\"'"
-          }
-        ]
-      }
-    ]
   }
 }

package/template/.claude/skills/development-workflow/SKILL.md

@@ -153,15 +153,15 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 
 **→ CHECKPOINT: Merge Approval**
 
-Before requesting merge approval, verify and complete this checklist:
-- [ ] **Std/Cplx only:** Ticket: Workflow Checklist — all completed steps marked `[x]` (through Step 5)
-- [ ] **Std/Cplx only:** Ticket: Completion Log — entry for each completed step (dates, actions, test counts)
-- [ ] **Std/Cplx only:** Ticket: Acceptance Criteria — mark `[x]` where met
-- [ ] Tracker: Active Session — reflects step `5/6 (Review)`, current context, next actions
-- [ ] Tracker: Features table — status and step updated to match Active Session
-- [ ] `key_facts.md` — updated if new models, schemas, migrations, or reusable components were added
-- [ ] `decisions.md` — ADR created if Definition of Done requires it
-- [ ] All fixes committed — no unstaged files remaining from review/QA fixes
+**STOP.** Before requesting merge approval, complete these actions IN ORDER:
+
+1. **Std/Cplx:** Re-read the ticket file (`docs/tickets/<feature-id>.md`) — mark ALL items `[x]` in: Workflow Checklist (Steps 0–5), Acceptance Criteria, Definition of Done. Add missing Completion Log entries (date, action, notes for each step).
+2. Re-read `docs/project_notes/product-tracker.md` — verify Active Session shows step `5/6 (Review)` and Features table is updated. Fix if stale.
+3. Update `key_facts.md` if new models, schemas, migrations, or reusable components were added.
+4. Update `decisions.md` with ADR if Definition of Done requires it.
+5. Commit ALL documentation updates.
+6. Run `git status` — verify clean working tree. No unstaged files allowed.
+7. THEN request merge approval from the user.
 
 ---
 

package/template/.gemini/skills/development-workflow/SKILL.md

@@ -153,15 +153,15 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 
 **→ CHECKPOINT: Merge Approval**
 
-Before requesting merge approval, verify and complete this checklist:
-- [ ] **Std/Cplx only:** Ticket: Workflow Checklist — all completed steps marked `[x]` (through Step 5)
-- [ ] **Std/Cplx only:** Ticket: Completion Log — entry for each completed step (dates, actions, test counts)
-- [ ] **Std/Cplx only:** Ticket: Acceptance Criteria — mark `[x]` where met
-- [ ] Tracker: Active Session — reflects step `5/6 (Review)`, current context, next actions
-- [ ] Tracker: Features table — status and step updated to match Active Session
-- [ ] `key_facts.md` — updated if new models, schemas, migrations, or reusable components were added
-- [ ] `decisions.md` — ADR created if Definition of Done requires it
-- [ ] All fixes committed — no unstaged files remaining from review/QA fixes
+**STOP.** Before requesting merge approval, complete these actions IN ORDER:
+
+1. **Std/Cplx:** Re-read the ticket file (`docs/tickets/<feature-id>.md`) — mark ALL items `[x]` in: Workflow Checklist (Steps 0–5), Acceptance Criteria, Definition of Done. Add missing Completion Log entries (date, action, notes for each step).
+2. Re-read `docs/project_notes/product-tracker.md` — verify Active Session shows step `5/6 (Review)` and Features table is updated. Fix if stale.
+3. Update `key_facts.md` if new models, schemas, migrations, or reusable components were added.
+4. Update `decisions.md` with ADR if Definition of Done requires it.
+5. Commit ALL documentation updates.
+6. Run `git status` — verify clean working tree. No unstaged files allowed.
+7. THEN request merge approval from the user.
 
 ---