create-sdd-project 0.8.1 → 0.8.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-sdd-project",
-  "version": "0.8.1",
+  "version": "0.8.2",
   "description": "Create a new SDD DevFlow project with AI-assisted development workflow",
   "bin": {
     "create-sdd-project": "bin/cli.js"

package/template/.claude/agents/qa-engineer.md

@@ -39,7 +39,11 @@ Verify the implementation's robustness and strict adherence to `docs/specs/`.
 - **Backend**: Write tests for error paths, validation boundaries, concurrent access
 - **Frontend**: Write tests for error states, loading interruptions, accessibility
 
-### 5. Report
+### 5. Bug Documentation
+- If bugs are found: record each one in `docs/project_notes/bugs.md` with root cause, solution, and prevention notes
+- This ensures institutional memory — future sessions can avoid the same issues
+
+### 6. Report
 - If tests fail (regressions or new bugs): report them clearly with reproduction steps
 - If ALL tests pass: certify as "QA Verified"
 

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

@@ -87,7 +87,7 @@ See `references/branching-strategy.md` for details.
 2. Create feature branch: `feature/<feature-id>-<short-description>`
 3. **Std/Cplx:** Generate ticket from `references/ticket-template.md` → fill `## Spec` section
 4. **Complex:** Also review `decisions.md` for related ADRs
-5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity
+5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity. Update Features table: status `in-progress`, step `1/6`
 
 **→ CHECKPOINT: Ticket Approval** (Std/Cplx only — Simple skips to Step 3)
 
@@ -98,7 +98,7 @@ See `references/branching-strategy.md` for details.
 1. Use Task tool with planner agent (`backend-planner` for backend features, `frontend-planner` for frontend features)
 2. **Fullstack features:** Run `backend-planner` first, then `frontend-planner`. Each writes its own section in the Implementation Plan
 3. Agent writes Implementation Plan into ticket's `## Implementation Plan`
-4. Update tracker: step `2/6 (Plan)`
+4. Update tracker: step `2/6 (Plan)` (Active Session + Features table)
 
 **→ CHECKPOINT: Plan Approval**
 
@@ -122,7 +122,7 @@ See `references/branching-strategy.md` for details.
 
 **Commits:** Commit freely during implementation (one per logical unit is fine). Final history cleanup happens via squash merge in Step 5.
 
-Update tracker: step `3/6 (Implement)`, context summary.
+Update tracker: step `3/6 (Implement)`, context summary (Active Session + Features table).
 
 ---
 
@@ -137,7 +137,7 @@ Update tracker: step `3/6 (Implement)`, context summary.
 
 **Commit format:** `<type>(<scope>): <description>` + `Co-Authored-By: Claude <noreply@anthropic.com>`
 
-Update tracker: step `4/6 (Finalize)`
+Update tracker: step `4/6 (Finalize)` (Active Session + Features table)
 
 ---
 
@@ -148,11 +148,12 @@ Update tracker: step `4/6 (Finalize)`
 1. Push branch, create PR (use `references/pr-template.md`)
 2. **Std/Cplx:** Run `code-review-specialist` via Task tool — **do NOT skip**
 3. **Std/Cplx:** Also run `qa-engineer` via Task tool
-4. **Merge strategy:** Features/bugfixes → **squash merge** (clean single commit on target branch); Releases/hotfixes → merge commit
+4. **Fix loop:** If review or QA finds issues → fix them → commit fixes → re-run quality gates (`npm test` / lint / build). Repeat until clean.
+5. **Merge strategy:** Features/bugfixes → **squash merge** (clean single commit on target branch); Releases/hotfixes → merge commit
 
 **→ CHECKPOINT: Merge Approval**
 
-Update tracker: step `5/6 (Review)`
+Update tracker: step `5/6 (Review)`, update Features table status
 
 ---
 
@@ -160,9 +161,8 @@ Update tracker: step `5/6 (Review)`
 
 1. **Update ticket with final state:** 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: feature → done, add to Completion Log, update progress
-4. Record bugs in `bugs.md`, decisions in `decisions.md`
-5. Clear Active Session → "No active work"
+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`
 
 ---
 
@@ -195,6 +195,6 @@ Update tracker: step `5/6 (Review)`
 - **Type safety** — fully typed, no `any`
 - **English only** — all technical artifacts
 - **Memory first** — check `project_notes/` before changes
-- **Product tracker** — keep Active Session updated at every step
+- **Product tracker** — keep Active Session AND Features table updated at every step
 - **Correct agents** — Backend → `backend-planner` + `backend-developer`, Frontend → `frontend-planner` + `frontend-developer`
 - **Correct base branch** — check `key_facts.md` before creating branches

package/template/.gemini/agents/qa-engineer.md

@@ -15,7 +15,8 @@ You assume the happy path works (checked by Developer). Hunt for edge cases, sec
 2. Identify missing test cases and spec deviations
 3. Run full test suite for regressions
 4. Create new edge-case tests (e.g., `*.edge-cases.test.ts`)
-5. Report findings (QA Verified or Issues Found)
+5. If bugs are found: record each one in `docs/project_notes/bugs.md` with root cause, solution, and prevention notes
+6. Report findings (QA Verified or Issues Found)
 
 ## Rules
 

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

@@ -87,7 +87,7 @@ See `references/branching-strategy.md` for details.
 2. Create feature branch: `feature/<feature-id>-<short-description>`
 3. **Std/Cplx:** Generate ticket from `references/ticket-template.md` → fill `## Spec` section
 4. **Complex:** Also review `decisions.md` for related ADRs
-5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity
+5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity. Update Features table: status `in-progress`, step `1/6`
 
 **→ CHECKPOINT: Ticket Approval** (Std/Cplx only — Simple skips to Step 3)
 
@@ -98,7 +98,7 @@ See `references/branching-strategy.md` for details.
 1. Follow the planner agent instructions (`backend-planner` for backend features, `frontend-planner` for frontend features) in `.gemini/agents/`
 2. **Fullstack features:** Run `backend-planner` first, then `frontend-planner`. Each writes its own section in the Implementation Plan
 3. Write Implementation Plan into ticket's `## Implementation Plan`
-4. Update tracker: step `2/6 (Plan)`
+4. Update tracker: step `2/6 (Plan)` (Active Session + Features table)
 
 **→ CHECKPOINT: Plan Approval**
 
@@ -122,7 +122,7 @@ See `references/branching-strategy.md` for details.
 
 **Commits:** Commit freely during implementation (one per logical unit is fine). Final history cleanup happens via squash merge in Step 5.
 
-Update tracker: step `3/6 (Implement)`, context summary.
+Update tracker: step `3/6 (Implement)`, context summary (Active Session + Features table).
 
 ---
 
@@ -137,7 +137,7 @@ Update tracker: step `3/6 (Implement)`, context summary.
 
 **Commit format:** `<type>(<scope>): <description>`
 
-Update tracker: step `4/6 (Finalize)`
+Update tracker: step `4/6 (Finalize)` (Active Session + Features table)
 
 ---
 
@@ -148,11 +148,12 @@ Update tracker: step `4/6 (Finalize)`
 1. Push branch, create PR (use `references/pr-template.md`)
 2. **Std/Cplx:** Follow `code-review-specialist` instructions in `.gemini/agents/` — **do NOT skip**
 3. **Std/Cplx:** Also follow `qa-engineer` instructions in `.gemini/agents/`
-4. **Merge strategy:** Features/bugfixes → **squash merge** (clean single commit on target branch); Releases/hotfixes → merge commit
+4. **Fix loop:** If review or QA finds issues → fix them → commit fixes → re-run quality gates (`npm test` / lint / build). Repeat until clean.
+5. **Merge strategy:** Features/bugfixes → **squash merge** (clean single commit on target branch); Releases/hotfixes → merge commit
 
 **→ CHECKPOINT: Merge Approval**
 
-Update tracker: step `5/6 (Review)`
+Update tracker: step `5/6 (Review)`, update Features table status
 
 ---
 
@@ -160,9 +161,8 @@ Update tracker: step `5/6 (Review)`
 
 1. **Update ticket with final state:** 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: feature → done, add to Completion Log, update progress
-4. Record bugs in `bugs.md`, decisions in `decisions.md`
-5. Clear Active Session → "No active work"
+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`
 
 ---
 
@@ -197,6 +197,6 @@ Agent instructions are in `.gemini/agents/`. Read the relevant agent file when e
 - **Type safety** — fully typed, no `any`
 - **English only** — all technical artifacts
 - **Memory first** — check `project_notes/` before changes
-- **Product tracker** — keep Active Session updated at every step
+- **Product tracker** — keep Active Session AND Features table updated at every step
 - **Correct agents** — Backend → `backend-planner` + `backend-developer`, Frontend → `frontend-planner` + `frontend-developer`
 - **Correct base branch** — check `key_facts.md` before creating branches