create-sdd-project 0.8.9 → 0.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-sdd-project",
3
- "version": "0.8.9",
3
+ "version": "0.9.0",
4
4
  "description": "Create a new SDD DevFlow project with AI-assisted development workflow",
5
5
  "bin": {
6
6
  "create-sdd-project": "bin/cli.js"
@@ -85,7 +85,7 @@ See `references/branching-strategy.md` for details.
85
85
 
86
86
  1. Verify product tracker exists, no active feature, dependencies met
87
87
  2. Create feature branch: `feature/<feature-id>-<short-description>`
88
- 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.**
88
+ 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.**
89
89
  4. **Complex:** Also review `decisions.md` for related ADRs
90
90
  5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity. Update Features table: status `in-progress`, step `1/6`
91
91
 
@@ -153,7 +153,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
153
153
 
154
154
  **→ CHECKPOINT: Merge Approval**
155
155
 
156
- **STOP.** Read `references/merge-checklist.md` and execute ALL actions in order. Do NOT request merge approval until every action is done.
156
+ **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.
157
157
 
158
158
  ---
159
159
 
@@ -7,7 +7,7 @@
7
7
 
8
8
  Re-read the ticket file (`docs/tickets/<feature-id>.md`).
9
9
 
10
- Verify it contains ALL required sections: **Acceptance Criteria**, **Definition of Done**, **Workflow Checklist**, **Completion Log**.
10
+ Verify it contains ALL required sections: **Acceptance Criteria**, **Definition of Done**, **Workflow Checklist**, **Completion Log**, **Merge Checklist Evidence**.
11
11
 
12
12
  **If ANY section is missing**, add it from `references/ticket-template.md` before continuing.
13
13
 
@@ -46,6 +46,17 @@ Commit ALL documentation updates from actions 0–4. Use commit message: `docs:
46
46
 
47
47
  Run `git status`. **No unstaged or untracked files allowed.** If any remain, stage and commit them.
48
48
 
49
- ## Action 7: Request merge approval
49
+ ## Action 7: Fill Merge Checklist Evidence
50
+
51
+ In the ticket, fill the `## Merge Checklist Evidence` table. For each action (0–6), mark `[x]` and write the actual evidence (not placeholders). Example:
52
+
53
+ | Action | Done | Evidence |
54
+ |--------|:----:|----------|
55
+ | 0. Validate ticket structure | [x] | Sections verified: Spec, Plan, AC, DoD, Workflow, Log, Evidence |
56
+ | 1. Mark all items | [x] | AC: 12/12, DoD: 7/7, Workflow: 0-5/6 |
57
+
58
+ ## Action 8: Request merge approval
59
+
60
+ Verify the Merge Checklist Evidence table is fully filled (all rows `[x]` with real evidence).
50
61
 
51
62
  THEN — and only then — request merge approval from the user.
@@ -87,4 +87,20 @@ This creates a feedback loop for improving future reviews. -->
87
87
 
88
88
  ---
89
89
 
90
+ ## Merge Checklist Evidence
91
+
92
+ > **MANDATORY before requesting merge approval.** Read `references/merge-checklist.md` and execute ALL actions. Record evidence below.
93
+
94
+ | Action | Done | Evidence |
95
+ |--------|:----:|----------|
96
+ | 0. Validate ticket structure | [ ] | Sections verified: (list) |
97
+ | 1. Mark all items | [ ] | AC: _/_, DoD: _/_, Workflow: _/_ |
98
+ | 2. Verify product tracker | [ ] | Active Session: step _/6, Features table: _/6 |
99
+ | 3. Update key_facts.md | [ ] | Updated: (list) / N/A |
100
+ | 4. Update decisions.md | [ ] | ADR-XXX added / N/A |
101
+ | 5. Commit documentation | [ ] | Commit: (hash) |
102
+ | 6. Verify clean working tree | [ ] | `git status`: clean |
103
+
104
+ ---
105
+
90
106
  *Ticket created: [YYYY-MM-DD]*
@@ -85,7 +85,7 @@ See `references/branching-strategy.md` for details.
85
85
 
86
86
  1. Verify product tracker exists, no active feature, dependencies met
87
87
  2. Create feature branch: `feature/<feature-id>-<short-description>`
88
- 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.**
88
+ 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.**
89
89
  4. **Complex:** Also review `decisions.md` for related ADRs
90
90
  5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity. Update Features table: status `in-progress`, step `1/6`
91
91
 
@@ -153,7 +153,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
153
153
 
154
154
  **→ CHECKPOINT: Merge Approval**
155
155
 
156
- **STOP.** Read `references/merge-checklist.md` and execute ALL actions in order. Do NOT request merge approval until every action is done.
156
+ **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.
157
157
 
158
158
  ---
159
159
 
@@ -7,7 +7,7 @@
7
7
 
8
8
  Re-read the ticket file (`docs/tickets/<feature-id>.md`).
9
9
 
10
- Verify it contains ALL required sections: **Acceptance Criteria**, **Definition of Done**, **Workflow Checklist**, **Completion Log**.
10
+ Verify it contains ALL required sections: **Acceptance Criteria**, **Definition of Done**, **Workflow Checklist**, **Completion Log**, **Merge Checklist Evidence**.
11
11
 
12
12
  **If ANY section is missing**, add it from `references/ticket-template.md` before continuing.
13
13
 
@@ -46,6 +46,17 @@ Commit ALL documentation updates from actions 0–4. Use commit message: `docs:
46
46
 
47
47
  Run `git status`. **No unstaged or untracked files allowed.** If any remain, stage and commit them.
48
48
 
49
- ## Action 7: Request merge approval
49
+ ## Action 7: Fill Merge Checklist Evidence
50
+
51
+ In the ticket, fill the `## Merge Checklist Evidence` table. For each action (0–6), mark `[x]` and write the actual evidence (not placeholders). Example:
52
+
53
+ | Action | Done | Evidence |
54
+ |--------|:----:|----------|
55
+ | 0. Validate ticket structure | [x] | Sections verified: Spec, Plan, AC, DoD, Workflow, Log, Evidence |
56
+ | 1. Mark all items | [x] | AC: 12/12, DoD: 7/7, Workflow: 0-5/6 |
57
+
58
+ ## Action 8: Request merge approval
59
+
60
+ Verify the Merge Checklist Evidence table is fully filled (all rows `[x]` with real evidence).
50
61
 
51
62
  THEN — and only then — request merge approval from the user.
@@ -87,4 +87,20 @@ This creates a feedback loop for improving future reviews. -->
87
87
 
88
88
  ---
89
89
 
90
+ ## Merge Checklist Evidence
91
+
92
+ > **MANDATORY before requesting merge approval.** Read `references/merge-checklist.md` and execute ALL actions. Record evidence below.
93
+
94
+ | Action | Done | Evidence |
95
+ |--------|:----:|----------|
96
+ | 0. Validate ticket structure | [ ] | Sections verified: (list) |
97
+ | 1. Mark all items | [ ] | AC: _/_, DoD: _/_, Workflow: _/_ |
98
+ | 2. Verify product tracker | [ ] | Active Session: step _/6, Features table: _/6 |
99
+ | 3. Update key_facts.md | [ ] | Updated: (list) / N/A |
100
+ | 4. Update decisions.md | [ ] | ADR-XXX added / N/A |
101
+ | 5. Commit documentation | [ ] | Commit: (hash) |
102
+ | 6. Verify clean working tree | [ ] | `git status`: clean |
103
+
104
+ ---
105
+
90
106
  *Ticket created: [YYYY-MM-DD]*