create-sdd-project 0.13.0 → 0.13.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-sdd-project",
-  "version": "0.13.0",
+  "version": "0.13.2",
   "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

@@ -50,6 +50,7 @@ Read the **Autonomy Level** from `CLAUDE.md` section 2.
 - **Auto** = proceed without asking; log in product tracker → "Auto-Approved Decisions" table
 - **Required** = ask user explicitly; do NOT continue without approval
 - **Quality gates always run** regardless of level (tests, lint, build, validators)
+- **Steps are strictly sequential.** Do NOT start a later step before the current checkpoint is approved — even when the checkpoint is Auto (auto-approval still happens in order, not in parallel). In particular, do NOT generate the Implementation Plan (Step 2) while Spec Approval (Step 0) is still pending. Reason: if the spec review finds issues, any plan built on the flawed spec must be discarded and redone — parallelizing wastes work and risks shipping a plan that doesn't match the final spec.
 
 ---
 
@@ -171,7 +172,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 
 ## Step 6: Complete
 
-1. **Update ticket with final state:** correct test count in acceptance criteria, mark all checkboxes, update Completion Log with all commits and key events
+1. **Update ticket with final state:** update Status to `Done`, correct test count in acceptance criteria, mark all checkboxes, update Completion Log with all commits and key events
 2. Delete feature branch (local + remote)
 3. Update product tracker: Features table status → `done`, add to Completion Log, clear Active Session → "No active work"
 4. Record any bugs found during the feature in `bugs.md`, decisions in `decisions.md`

package/template/.claude/skills/development-workflow/references/merge-checklist.md

@@ -13,15 +13,16 @@ Verify it contains ALL required sections: **Acceptance Criteria**, **Definition
 
 **Simple (lite ticket):** Verify same sections exist. Spec and Implementation Plan may be minimal (one-liner / N/A).
 
-## Action 1: Mark all items
+## Action 1: Mark all items and update Status
 
-In the ticket file, mark ALL items `[x]` in:
+In the ticket file:
 
-- **Workflow Checklist** — all steps that apply to this complexity tier (Simple: 1, 3, 4, 5. Standard: 0–5. Complex: 0–5)
-- **Acceptance Criteria** — every item
-- **Definition of Done** — every item
-
-Add missing **Completion Log** entries: one row per step with date, action, and notes.
+1. Update the **Status** field in the ticket header from `In Progress` to `Ready for Merge`
+2. Mark ALL items `[x]` in:
+   - **Workflow Checklist** — all steps that apply to this complexity tier (Simple: 1, 3, 4, 5. Standard: 0–5. Complex: 0–5)
+   - **Acceptance Criteria** — every item
+   - **Definition of Done** — every item
+3. Add missing **Completion Log** entries: one row per step with date, action, and notes.
 
 ## Action 2: Verify product tracker
 

package/template/.claude/skills/development-workflow/references/ticket-template.md

@@ -2,6 +2,7 @@
 
 **Feature:** [ID] | **Type:** [Backend/Frontend/Fullstack]-[Feature/Bugfix/Refactor] | **Priority:** [High/Medium/Low]
 **Status:** In Progress | **Branch:** feature/[FEATURE-ID]-[short-description]
+<!-- Valid Status values: In Progress | Ready for Merge | Done -->
 **Created:** [YYYY-MM-DD] | **Dependencies:** [List or "None"]
 
 ---

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

@@ -50,6 +50,7 @@ Read the **Autonomy Level** from `GEMINI.md`.
 - **Auto** = proceed without asking; log in product tracker → "Auto-Approved Decisions" table
 - **Required** = ask user explicitly; do NOT continue without approval
 - **Quality gates always run** regardless of level (tests, lint, build, validators)
+- **Steps are strictly sequential.** Do NOT start a later step before the current checkpoint is approved — even when the checkpoint is Auto (auto-approval still happens in order, not in parallel). In particular, do NOT generate the Implementation Plan (Step 2) while Spec Approval (Step 0) is still pending. Reason: if the spec review finds issues, any plan built on the flawed spec must be discarded and redone — parallelizing wastes work and risks shipping a plan that doesn't match the final spec.
 
 ---
 
@@ -171,7 +172,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 
 ## Step 6: Complete
 
-1. **Update ticket with final state:** correct test count in acceptance criteria, mark all checkboxes, update Completion Log with all commits and key events
+1. **Update ticket with final state:** update Status to `Done`, correct test count in acceptance criteria, mark all checkboxes, update Completion Log with all commits and key events
 2. Delete feature branch (local + remote)
 3. Update product tracker: Features table status → `done`, add to Completion Log, clear Active Session → "No active work"
 4. Record any bugs found during the feature in `bugs.md`, decisions in `decisions.md`

package/template/.gemini/skills/development-workflow/references/merge-checklist.md

@@ -13,15 +13,16 @@ Verify it contains ALL required sections: **Acceptance Criteria**, **Definition
 
 **Simple (lite ticket):** Verify same sections exist. Spec and Implementation Plan may be minimal (one-liner / N/A).
 
-## Action 1: Mark all items
+## Action 1: Mark all items and update Status
 
-In the ticket file, mark ALL items `[x]` in:
+In the ticket file:
 
-- **Workflow Checklist** — all steps that apply to this complexity tier (Simple: 1, 3, 4, 5. Standard: 0–5. Complex: 0–5)
-- **Acceptance Criteria** — every item
-- **Definition of Done** — every item
-
-Add missing **Completion Log** entries: one row per step with date, action, and notes.
+1. Update the **Status** field in the ticket header from `In Progress` to `Ready for Merge`
+2. Mark ALL items `[x]` in:
+   - **Workflow Checklist** — all steps that apply to this complexity tier (Simple: 1, 3, 4, 5. Standard: 0–5. Complex: 0–5)
+   - **Acceptance Criteria** — every item
+   - **Definition of Done** — every item
+3. Add missing **Completion Log** entries: one row per step with date, action, and notes.
 
 ## Action 2: Verify product tracker
 

package/template/.gemini/skills/development-workflow/references/ticket-template.md

@@ -2,6 +2,7 @@
 
 **Feature:** [ID] | **Type:** [Backend/Frontend/Fullstack]-[Feature/Bugfix/Refactor] | **Priority:** [High/Medium/Low]
 **Status:** In Progress | **Branch:** feature/[FEATURE-ID]-[short-description]
+<!-- Valid Status values: In Progress | Ready for Merge | Done -->
 **Created:** [YYYY-MM-DD] | **Dependencies:** [List or "None"]
 
 ---