create-sdd-project 0.8.2 → 0.8.3

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.
Files changed (5) hide show
  1. package/package.json +1 -1
  2. package/template/.claude/agents/qa-engineer.md +3 -3
  3. package/template/.claude/skills/development-workflow/SKILL.md +12 -4
  4. package/template/.gemini/agents/qa-engineer.md +1 -1
  5. package/template/.gemini/skills/development-workflow/SKILL.md +12 -4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-sdd-project",
3
- "version": "0.8.2",
3
+ "version": "0.8.3",
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"
package/template/.claude/agents/qa-engineer.md CHANGED
@@ -39,9 +39,9 @@ Verify the implementation's robustness and strict adherence to `docs/specs/`.
39
39
  - **Backend**: Write tests for error paths, validation boundaries, concurrent access
40
40
  - **Frontend**: Write tests for error states, loading interruptions, accessibility
41
41
 
42
- ### 5. Bug Documentation
43
- - If bugs are found: record each one in `docs/project_notes/bugs.md` with root cause, solution, and prevention notes
44
- - This ensures institutional memory — future sessions can avoid the same issues
42
+ ### 5. Bug Documentation (only if bugs were found)
43
+ - Record each bug in `docs/project_notes/bugs.md` with root cause, solution, and prevention notes
44
+ - Do NOT add an entry if no bugs were found — bugs.md is for bugs only, not QA pass reports
45
45
 
46
46
  ### 6. Report
47
47
  - If tests fail (regressions or new bugs): report them clearly with reproduction steps
package/template/.claude/skills/development-workflow/SKILL.md CHANGED
@@ -71,7 +71,7 @@ Ask user to classify complexity before starting. See `references/complexity-guid
71
71
  2. Agent updates global spec files (`api-spec.yaml`, `ui-components.md`) and Zod schemas in `shared/src/schemas/` if applicable
72
72
  3. Agent writes spec summary into the ticket's `## Spec` section
73
73
 
74
- **→ CHECKPOINT: Spec Approval** — Update tracker: step `0/6 (Spec)`
74
+ **→ CHECKPOINT: Spec Approval** — Update tracker (Active Session + Features table): step `0/6 (Spec)`
75
75
 
76
76
  ---
77
77
 
@@ -122,7 +122,7 @@ See `references/branching-strategy.md` for details.
122
122
 
123
123
  **Commits:** Commit freely during implementation (one per logical unit is fine). Final history cleanup happens via squash merge in Step 5.
124
124
 
125
- Update tracker: step `3/6 (Implement)`, context summary (Active Session + Features table).
125
+ Update tracker (Active Session + Features table): step `3/6 (Implement)`, context summary. Mark ticket Workflow Checklist `[x]` for Step 3.
126
126
 
127
127
  ---
128
128
 
@@ -137,7 +137,7 @@ Update tracker: step `3/6 (Implement)`, context summary (Active Session + Featur
137
137
 
138
138
  **Commit format:** `<type>(<scope>): <description>` + `Co-Authored-By: Claude <noreply@anthropic.com>`
139
139
 
140
- Update tracker: step `4/6 (Finalize)` (Active Session + Features table)
140
+ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ticket Workflow Checklist `[x]` for Step 4.
141
141
 
142
142
  ---
143
143
 
@@ -153,7 +153,15 @@ Update tracker: step `4/6 (Finalize)` (Active Session + Features table)
153
153
 
154
154
  **→ CHECKPOINT: Merge Approval**
155
155
 
156
- Update tracker: step `5/6 (Review)`, update Features table status
156
+ Before requesting merge approval, verify and complete this checklist:
157
+ - [ ] Ticket: Workflow Checklist — all completed steps marked `[x]` (through Step 5)
158
+ - [ ] Ticket: Completion Log — entry for each completed step (dates, actions, test counts)
159
+ - [ ] Ticket: Acceptance Criteria — mark `[x]` where met
160
+ - [ ] Tracker: Active Session — reflects step `5/6 (Review)`, current context, next actions
161
+ - [ ] Tracker: Features table — status and step updated to match Active Session
162
+ - [ ] `key_facts.md` — updated if new models, schemas, migrations, or reusable components were added
163
+ - [ ] `decisions.md` — ADR created if Definition of Done requires it
164
+ - [ ] All fixes committed — no unstaged files remaining from review/QA fixes
157
165
 
158
166
  ---
159
167
 
package/template/.gemini/agents/qa-engineer.md CHANGED
@@ -15,7 +15,7 @@ You assume the happy path works (checked by Developer). Hunt for edge cases, sec
15
15
  2. Identify missing test cases and spec deviations
16
16
  3. Run full test suite for regressions
17
17
  4. Create new edge-case tests (e.g., `*.edge-cases.test.ts`)
18
- 5. If bugs are found: record each one in `docs/project_notes/bugs.md` with root cause, solution, and prevention notes
18
+ 5. If bugs are found (and ONLY if bugs are found): record each one in `docs/project_notes/bugs.md` with root cause, solution, and prevention notes. Do NOT add an entry if no bugs were found.
19
19
  6. Report findings (QA Verified or Issues Found)
20
20
 
21
21
  ## Rules
package/template/.gemini/skills/development-workflow/SKILL.md CHANGED
@@ -71,7 +71,7 @@ Ask user to classify complexity before starting. See `references/complexity-guid
71
71
  2. Update global spec files (`api-spec.yaml`, `ui-components.md`) and Zod schemas in `shared/src/schemas/` if applicable
72
72
  3. Write spec summary into the ticket's `## Spec` section
73
73
 
74
- **→ CHECKPOINT: Spec Approval** — Update tracker: step `0/6 (Spec)`
74
+ **→ CHECKPOINT: Spec Approval** — Update tracker (Active Session + Features table): step `0/6 (Spec)`
75
75
 
76
76
  ---
77
77
 
@@ -122,7 +122,7 @@ See `references/branching-strategy.md` for details.
122
122
 
123
123
  **Commits:** Commit freely during implementation (one per logical unit is fine). Final history cleanup happens via squash merge in Step 5.
124
124
 
125
- Update tracker: step `3/6 (Implement)`, context summary (Active Session + Features table).
125
+ Update tracker (Active Session + Features table): step `3/6 (Implement)`, context summary. Mark ticket Workflow Checklist `[x]` for Step 3.
126
126
 
127
127
  ---
128
128
 
@@ -137,7 +137,7 @@ Update tracker: step `3/6 (Implement)`, context summary (Active Session + Featur
137
137
 
138
138
  **Commit format:** `<type>(<scope>): <description>`
139
139
 
140
- Update tracker: step `4/6 (Finalize)` (Active Session + Features table)
140
+ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ticket Workflow Checklist `[x]` for Step 4.
141
141
 
142
142
  ---
143
143
 
@@ -153,7 +153,15 @@ Update tracker: step `4/6 (Finalize)` (Active Session + Features table)
153
153
 
154
154
  **→ CHECKPOINT: Merge Approval**
155
155
 
156
- Update tracker: step `5/6 (Review)`, update Features table status
156
+ Before requesting merge approval, verify and complete this checklist:
157
+ - [ ] Ticket: Workflow Checklist — all completed steps marked `[x]` (through Step 5)
158
+ - [ ] Ticket: Completion Log — entry for each completed step (dates, actions, test counts)
159
+ - [ ] Ticket: Acceptance Criteria — mark `[x]` where met
160
+ - [ ] Tracker: Active Session — reflects step `5/6 (Review)`, current context, next actions
161
+ - [ ] Tracker: Features table — status and step updated to match Active Session
162
+ - [ ] `key_facts.md` — updated if new models, schemas, migrations, or reusable components were added
163
+ - [ ] `decisions.md` — ADR created if Definition of Done requires it
164
+ - [ ] All fixes committed — no unstaged files remaining from review/QA fixes
157
165
 
158
166
  ---
159
167