create-sdd-project 0.8.3 → 0.8.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-sdd-project",
-  "version": "0.8.3",
+  "version": "0.8.5",
   "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:** Generate ticket from `references/ticket-template.md` → fill `## Spec` section
+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
 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`
 
@@ -154,9 +154,9 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 **→ CHECKPOINT: Merge Approval**
 
 Before requesting merge approval, verify and complete this checklist:
-- [ ] Ticket: Workflow Checklist — all completed steps marked `[x]` (through Step 5)
-- [ ] Ticket: Completion Log — entry for each completed step (dates, actions, test counts)
-- [ ] Ticket: Acceptance Criteria — mark `[x]` where met
+- [ ] **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

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:** Generate ticket from `references/ticket-template.md` → fill `## Spec` section
+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
 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`
 
@@ -154,9 +154,9 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 **→ CHECKPOINT: Merge Approval**
 
 Before requesting merge approval, verify and complete this checklist:
-- [ ] Ticket: Workflow Checklist — all completed steps marked `[x]` (through Step 5)
-- [ ] Ticket: Completion Log — entry for each completed step (dates, actions, test counts)
-- [ ] Ticket: Acceptance Criteria — mark `[x]` where met
+- [ ] **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