create-sdd-project 0.8.8 → 0.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-sdd-project",
-  "version": "0.8.8",
+  "version": "0.9.0",
   "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. **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.**
+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 7 sections in this exact order: Spec → Implementation Plan → Acceptance Criteria → Definition of Done → Workflow Checklist → Completion Log → Merge Checklist Evidence. 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,16 +153,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 
 **→ CHECKPOINT: Merge Approval**
 
-**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.
+**STOP.** Read `references/merge-checklist.md` and execute ALL actions in order (including filling the `## Merge Checklist Evidence` table in the ticket). Do NOT request merge approval until every action is done.
 
 ---
 
@@ -195,6 +186,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 - `references/add-feature-template.md` — Add feature to tracker
 - `references/complexity-guide.md` — Complexity classification
 - `references/workflow-example.md` — Full worked example
+- `references/merge-checklist.md` — Pre-merge approval actions (MANDATORY)
 - `references/failure-handling.md` — Recovery & rollbacks
 
 ## Constraints

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

@@ -0,0 +1,62 @@
+# Merge Approval Checklist
+
+> Execute ALL actions below IN ORDER before requesting merge approval from the user.
+> Do NOT skip any action. Do NOT request merge approval until every action is complete.
+
+## Action 0: Validate ticket structure (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**, **Merge Checklist Evidence**.
+
+**If ANY section is missing**, add it from `references/ticket-template.md` before continuing.
+
+## Action 1: Mark all items (Std/Cplx)
+
+In the ticket file, mark ALL items `[x]` in:
+
+- **Workflow Checklist** — Steps 0 through 5 (all that apply to this complexity tier)
+- **Acceptance Criteria** — every item
+- **Definition of Done** — every item
+
+Add missing **Completion Log** entries: one row per step with date, action, and notes.
+
+## Action 2: Verify product tracker
+
+Re-read `docs/project_notes/product-tracker.md`.
+
+- **Active Session** must show step `5/6 (Review)` with current context.
+- **Features table** must show step `5/6` and status `in-progress`.
+
+Fix if stale.
+
+## Action 3: Update key_facts.md
+
+If this feature added new models, schemas, migrations, endpoints, reusable components, error codes, or shared utilities → update `docs/project_notes/key_facts.md`.
+
+## Action 4: Update decisions.md
+
+If Definition of Done requires an ADR → add it to `docs/project_notes/decisions.md`.
+
+## Action 5: Commit documentation
+
+Commit ALL documentation updates from actions 0–4. Use commit message: `docs: update ticket, tracker, and project docs for <feature-id>`.
+
+## Action 6: Verify clean working tree
+
+Run `git status`. **No unstaged or untracked files allowed.** If any remain, stage and commit them.
+
+## Action 7: Fill Merge Checklist Evidence
+
+In the ticket, fill the `## Merge Checklist Evidence` table. For each action (0–6), mark `[x]` and write the actual evidence (not placeholders). Example:
+
+| Action | Done | Evidence |
+|--------|:----:|----------|
+| 0. Validate ticket structure | [x] | Sections verified: Spec, Plan, AC, DoD, Workflow, Log, Evidence |
+| 1. Mark all items | [x] | AC: 12/12, DoD: 7/7, Workflow: 0-5/6 |
+
+## Action 8: Request merge approval
+
+Verify the Merge Checklist Evidence table is fully filled (all rows `[x]` with real evidence).
+
+THEN — and only then — request merge approval from the user.

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

@@ -87,4 +87,20 @@ This creates a feedback loop for improving future reviews. -->
 
 ---
 
+## Merge Checklist Evidence
+
+> **MANDATORY before requesting merge approval.** Read `references/merge-checklist.md` and execute ALL actions. Record evidence below.
+
+| Action | Done | Evidence |
+|--------|:----:|----------|
+| 0. Validate ticket structure | [ ] | Sections verified: (list) |
+| 1. Mark all items | [ ] | AC: _/_, DoD: _/_, Workflow: _/_ |
+| 2. Verify product tracker | [ ] | Active Session: step _/6, Features table: _/6 |
+| 3. Update key_facts.md | [ ] | Updated: (list) / N/A |
+| 4. Update decisions.md | [ ] | ADR-XXX added / N/A |
+| 5. Commit documentation | [ ] | Commit: (hash) |
+| 6. Verify clean working tree | [ ] | `git status`: clean |
+
+---
+
 *Ticket created: [YYYY-MM-DD]*

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. **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.**
+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 7 sections in this exact order: Spec → Implementation Plan → Acceptance Criteria → Definition of Done → Workflow Checklist → Completion Log → Merge Checklist Evidence. 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,16 +153,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 
 **→ CHECKPOINT: Merge Approval**
 
-**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.
+**STOP.** Read `references/merge-checklist.md` and execute ALL actions in order (including filling the `## Merge Checklist Evidence` table in the ticket). Do NOT request merge approval until every action is done.
 
 ---
 
@@ -197,6 +188,7 @@ Agent instructions are in `.gemini/agents/`. Read the relevant agent file when e
 - `references/add-feature-template.md` — Add feature to tracker
 - `references/complexity-guide.md` — Complexity classification
 - `references/workflow-example.md` — Full worked example
+- `references/merge-checklist.md` — Pre-merge approval actions (MANDATORY)
 - `references/failure-handling.md` — Recovery & rollbacks
 
 ## Constraints

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

@@ -0,0 +1,62 @@
+# Merge Approval Checklist
+
+> Execute ALL actions below IN ORDER before requesting merge approval from the user.
+> Do NOT skip any action. Do NOT request merge approval until every action is complete.
+
+## Action 0: Validate ticket structure (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**, **Merge Checklist Evidence**.
+
+**If ANY section is missing**, add it from `references/ticket-template.md` before continuing.
+
+## Action 1: Mark all items (Std/Cplx)
+
+In the ticket file, mark ALL items `[x]` in:
+
+- **Workflow Checklist** — Steps 0 through 5 (all that apply to this complexity tier)
+- **Acceptance Criteria** — every item
+- **Definition of Done** — every item
+
+Add missing **Completion Log** entries: one row per step with date, action, and notes.
+
+## Action 2: Verify product tracker
+
+Re-read `docs/project_notes/product-tracker.md`.
+
+- **Active Session** must show step `5/6 (Review)` with current context.
+- **Features table** must show step `5/6` and status `in-progress`.
+
+Fix if stale.
+
+## Action 3: Update key_facts.md
+
+If this feature added new models, schemas, migrations, endpoints, reusable components, error codes, or shared utilities → update `docs/project_notes/key_facts.md`.
+
+## Action 4: Update decisions.md
+
+If Definition of Done requires an ADR → add it to `docs/project_notes/decisions.md`.
+
+## Action 5: Commit documentation
+
+Commit ALL documentation updates from actions 0–4. Use commit message: `docs: update ticket, tracker, and project docs for <feature-id>`.
+
+## Action 6: Verify clean working tree
+
+Run `git status`. **No unstaged or untracked files allowed.** If any remain, stage and commit them.
+
+## Action 7: Fill Merge Checklist Evidence
+
+In the ticket, fill the `## Merge Checklist Evidence` table. For each action (0–6), mark `[x]` and write the actual evidence (not placeholders). Example:
+
+| Action | Done | Evidence |
+|--------|:----:|----------|
+| 0. Validate ticket structure | [x] | Sections verified: Spec, Plan, AC, DoD, Workflow, Log, Evidence |
+| 1. Mark all items | [x] | AC: 12/12, DoD: 7/7, Workflow: 0-5/6 |
+
+## Action 8: Request merge approval
+
+Verify the Merge Checklist Evidence table is fully filled (all rows `[x]` with real evidence).
+
+THEN — and only then — request merge approval from the user.

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

@@ -87,4 +87,20 @@ This creates a feedback loop for improving future reviews. -->
 
 ---
 
+## Merge Checklist Evidence
+
+> **MANDATORY before requesting merge approval.** Read `references/merge-checklist.md` and execute ALL actions. Record evidence below.
+
+| Action | Done | Evidence |
+|--------|:----:|----------|
+| 0. Validate ticket structure | [ ] | Sections verified: (list) |
+| 1. Mark all items | [ ] | AC: _/_, DoD: _/_, Workflow: _/_ |
+| 2. Verify product tracker | [ ] | Active Session: step _/6, Features table: _/6 |
+| 3. Update key_facts.md | [ ] | Updated: (list) / N/A |
+| 4. Update decisions.md | [ ] | ADR-XXX added / N/A |
+| 5. Commit documentation | [ ] | Commit: (hash) |
+| 6. Verify clean working tree | [ ] | `git status`: clean |
+
+---
+
 *Ticket created: [YYYY-MM-DD]*