create-sdd-project 0.8.6 → 0.8.8

package/package.json

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

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

@@ -85,7 +85,7 @@ See `references/branching-strategy.md` for details.
 
 1. Verify product tracker exists, no active feature, dependencies met
 2. Create feature branch: `feature/<feature-id>-<short-description>`
-3. **Std/Cplx:** Copy ALL sections from `references/ticket-template.md` (Spec, Implementation Plan, Acceptance Criteria, Definition of Done, Workflow Checklist, Completion Log) → fill `## Spec` section. Do NOT omit empty sections — they are filled in later steps
+3. **Std/Cplx:** Copy ALL sections from `references/ticket-template.md` (Spec, Implementation Plan, Acceptance Criteria, Definition of Done, Workflow Checklist, Completion Log) → fill `## Spec` section. Do NOT omit empty sections — they are filled in later steps. **After generating the ticket, verify it contains ALL 6 sections in this exact order: Spec → Implementation Plan → Acceptance Criteria → Definition of Done → Workflow Checklist → Completion Log. If any section is missing, add it now.**
 4. **Complex:** Also review `decisions.md` for related ADRs
 5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity. Update Features table: status `in-progress`, step `1/6`
 
@@ -153,15 +153,16 @@ 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:
+
+0. **Std/Cplx:** Re-read the ticket file (`docs/tickets/<feature-id>.md`) — verify it contains ALL required sections: Acceptance Criteria, Definition of Done, Workflow Checklist, Completion Log. **If ANY section is missing, add it from `references/ticket-template.md` before continuing.**
+1. **Std/Cplx:** 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

@@ -85,7 +85,7 @@ See `references/branching-strategy.md` for details.
 
 1. Verify product tracker exists, no active feature, dependencies met
 2. Create feature branch: `feature/<feature-id>-<short-description>`
-3. **Std/Cplx:** Copy ALL sections from `references/ticket-template.md` (Spec, Implementation Plan, Acceptance Criteria, Definition of Done, Workflow Checklist, Completion Log) → fill `## Spec` section. Do NOT omit empty sections — they are filled in later steps
+3. **Std/Cplx:** Copy ALL sections from `references/ticket-template.md` (Spec, Implementation Plan, Acceptance Criteria, Definition of Done, Workflow Checklist, Completion Log) → fill `## Spec` section. Do NOT omit empty sections — they are filled in later steps. **After generating the ticket, verify it contains ALL 6 sections in this exact order: Spec → Implementation Plan → Acceptance Criteria → Definition of Done → Workflow Checklist → Completion Log. If any section is missing, add it now.**
 4. **Complex:** Also review `decisions.md` for related ADRs
 5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity. Update Features table: status `in-progress`, step `1/6`
 
@@ -153,15 +153,16 @@ 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:
+
+0. **Std/Cplx:** Re-read the ticket file (`docs/tickets/<feature-id>.md`) — verify it contains ALL required sections: Acceptance Criteria, Definition of Done, Workflow Checklist, Completion Log. **If ANY section is missing, add it from `references/ticket-template.md` before continuing.**
+1. **Std/Cplx:** 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.
 
 ---