create-sdd-project 0.14.0 → 0.15.0

package/README.md

@@ -354,7 +354,7 @@ Quality gates (tests, lint, build, validators) **always run** regardless of leve
 Every ticket includes a `## Merge Checklist Evidence` table that the agent must fill before requesting merge approval. This mechanism:
 
 - **Survives context compaction** — the ticket is always re-read via product tracker, so the empty evidence table acts as a persistent reminder
-- **Forces sequential execution** — agent must read `references/merge-checklist.md`, execute 10 actions (0–9), and record evidence
+- **Forces sequential execution** — agent must read `references/merge-checklist.md`, execute 11 actions (0–10), and record evidence
 - **Works at all tiers** — Simple tasks get a lite ticket with the same evidence table
 
 Validated across 16+ features with 87% first-attempt pass rate (failures led to iterative improvements in v0.8.7–v0.9.8).

package/lib/config.js

@@ -110,6 +110,7 @@ const TEMPLATE_COMMANDS = [
   'review-spec.md',
   'context-prompt.md',
   'review-project.md',
+  'audit-merge.md',
 ];
 
 module.exports = {

package/package.json

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

package/template/.claude/commands/audit-merge.md

@@ -0,0 +1,90 @@
+Run an automated compliance audit on the current feature before requesting merge approval.
+
+## Prerequisites
+
+- An active feature at Step 5 (Review) with Merge Checklist Evidence filled
+- All quality gates passed (tests, lint, build)
+
+## What to do
+
+Read `docs/project_notes/product-tracker.md` → Active Session to identify the current feature, branch, and ticket path. Then run ALL checks below and report results in a table.
+
+### Checks
+
+**1. Ticket Status** — Read the ticket file. The `**Status:**` field in the header must be `Ready for Merge`. Flag if it shows any other value (In Progress, Spec, Planning, Review, Done).
+
+**2. Acceptance Criteria** — Count `[x]` vs `[ ]` in the `## Acceptance Criteria` section. ALL must be `[x]`. Report ratio (e.g., "14/14").
+
+**3. Definition of Done** — Count `[x]` vs `[ ]` in the `## Definition of Done` section. ALL must be `[x]`. Report ratio.
+
+**4. Workflow Checklist** — Count `[x]` vs `[ ]` in the `## Workflow Checklist` section. All steps except Step 6 must be `[x]`. Step 6 should be `[ ]` (pending merge).
+
+**5. Merge Checklist Evidence** — Verify the `## Merge Checklist Evidence` table has ALL rows marked `[x]` with real evidence (not placeholder text like "Sections verified: (list)").
+
+**6. Completion Log** — Verify the `## Completion Log` table has at least one entry per executed workflow step. If bugs are mentioned in any entry, verify they are documented in `docs/project_notes/bugs.md`.
+
+**7. Product Tracker Sync** — Read `docs/project_notes/product-tracker.md`:
+  - Active Session must show step `5/6` with correct feature ID and branch
+  - Features table must show the feature as `in-progress` at step `5/6`
+  - Flag if stale or mismatched with ticket
+
+**8. key_facts.md** — If the ticket's changes include new models, migrations, endpoints, modules, or shared utilities, verify they are documented in `docs/project_notes/key_facts.md`. If no new infrastructure, this is N/A.
+
+**9. Merge Base** — Run these commands and report result:
+```bash
+TARGET_BRANCH="develop"  # or "main" — check key_facts.md branching-strategy
+git fetch origin "$TARGET_BRANCH"
+git merge-base --is-ancestor "origin/$TARGET_BRANCH" HEAD && echo "UP TO DATE" || echo "DIVERGED"
+```
+If DIVERGED, flag as FAIL with instruction to merge target branch first.
+
+**10. Working Tree** — Run `git status`. Must show "nothing to commit, working tree clean".
+
+**11. Data File Integrity** (if JSON/seed files are in the diff) — Check:
+  - String arrays (aliases, tags): all values same casing convention
+  - ID fields: no duplicates
+  - Numeric fields: no negatives where unexpected
+  - Object arrays: consistent shape (no missing keys)
+
+Run only if `git diff origin/<target-branch>..HEAD --name-only` shows `.json` files in seed-data or fixtures directories.
+
+### Output Format
+
+Report as a compliance table:
+
+```
+## Merge Compliance Audit — [FEATURE-ID]
+
+| # | Check | Status | Detail |
+|---|-------|:------:|--------|
+| 1 | Ticket Status | PASS | "Ready for Merge" |
+| 2 | Acceptance Criteria | PASS | 14/14 |
+| 3 | Definition of Done | PASS | 7/7 |
+| 4 | Workflow Checklist | PASS | 7/8 (Step 6 pending) |
+| 5 | Merge Checklist Evidence | PASS | 8/8 with evidence |
+| 6 | Completion Log | PASS | 5 entries, bugs documented |
+| 7 | Tracker Sync | PASS | Active Session + Features table correct |
+| 8 | key_facts.md | PASS | N/A — no new infrastructure |
+| 9 | Merge Base | PASS | Up to date with develop |
+| 10 | Working Tree | PASS | Clean |
+| 11 | Data Files | PASS | N/A — no JSON seed files |
+
+**Verdict: READY FOR MERGE** (or **NEEDS FIX — N issues**)
+```
+
+### If issues are found
+
+Fix them directly:
+- Status wrong → update the ticket header
+- AC/DoD unchecked → mark `[x]`
+- Tracker stale → update Active Session and Features table
+- Merge base diverged → `git merge origin/<target-branch>` and resolve conflicts
+- Data file issues → fix the data
+
+After fixing, re-run the audit to confirm all checks pass.
+
+## Notes
+
+- This command automates the compliance portion of the merge review — it does NOT replace code review, QA, or human architectural review
+- Run this AFTER completing Action 8 (Fill Merge Checklist Evidence) and BEFORE Action 9 (Request merge approval)
+- The output should be included in the merge approval request message so the reviewer can skip compliance checks and focus on code quality

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

@@ -72,8 +72,14 @@ In the ticket, fill the `## Merge Checklist Evidence` table. For each action (0
 | 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 9: Request merge approval
+## Action 9: Run compliance audit
 
-Verify the Merge Checklist Evidence table is fully filled (all rows `[x]` with real evidence).
+Run `/audit-merge` to verify all compliance checks pass automatically. If any check fails, fix it and re-run until all pass.
+
+Include the audit output in the merge approval request message so the reviewer can skip compliance checks and focus on code/architecture review.
+
+## Action 10: Request merge approval
+
+Verify the compliance audit passed and the Merge Checklist Evidence table is fully filled.
 
 THEN — and only then — request merge approval from the user.

package/template/.gemini/commands/audit-merge-instructions.md

@@ -0,0 +1,90 @@
+Run an automated compliance audit on the current feature before requesting merge approval.
+
+## Prerequisites
+
+- An active feature at Step 5 (Review) with Merge Checklist Evidence filled
+- All quality gates passed (tests, lint, build)
+
+## What to do
+
+Read `docs/project_notes/product-tracker.md` → Active Session to identify the current feature, branch, and ticket path. Then run ALL checks below and report results in a table.
+
+### Checks
+
+**1. Ticket Status** — Read the ticket file. The `**Status:**` field in the header must be `Ready for Merge`. Flag if it shows any other value (In Progress, Spec, Planning, Review, Done).
+
+**2. Acceptance Criteria** — Count `[x]` vs `[ ]` in the `## Acceptance Criteria` section. ALL must be `[x]`. Report ratio (e.g., "14/14").
+
+**3. Definition of Done** — Count `[x]` vs `[ ]` in the `## Definition of Done` section. ALL must be `[x]`. Report ratio.
+
+**4. Workflow Checklist** — Count `[x]` vs `[ ]` in the `## Workflow Checklist` section. All steps except Step 6 must be `[x]`. Step 6 should be `[ ]` (pending merge).
+
+**5. Merge Checklist Evidence** — Verify the `## Merge Checklist Evidence` table has ALL rows marked `[x]` with real evidence (not placeholder text like "Sections verified: (list)").
+
+**6. Completion Log** — Verify the `## Completion Log` table has at least one entry per executed workflow step. If bugs are mentioned in any entry, verify they are documented in `docs/project_notes/bugs.md`.
+
+**7. Product Tracker Sync** — Read `docs/project_notes/product-tracker.md`:
+  - Active Session must show step `5/6` with correct feature ID and branch
+  - Features table must show the feature as `in-progress` at step `5/6`
+  - Flag if stale or mismatched with ticket
+
+**8. key_facts.md** — If the ticket's changes include new models, migrations, endpoints, modules, or shared utilities, verify they are documented in `docs/project_notes/key_facts.md`. If no new infrastructure, this is N/A.
+
+**9. Merge Base** — Run these commands and report result:
+```bash
+TARGET_BRANCH="develop"  # or "main" — check key_facts.md branching-strategy
+git fetch origin "$TARGET_BRANCH"
+git merge-base --is-ancestor "origin/$TARGET_BRANCH" HEAD && echo "UP TO DATE" || echo "DIVERGED"
+```
+If DIVERGED, flag as FAIL with instruction to merge target branch first.
+
+**10. Working Tree** — Run `git status`. Must show "nothing to commit, working tree clean".
+
+**11. Data File Integrity** (if JSON/seed files are in the diff) — Check:
+  - String arrays (aliases, tags): all values same casing convention
+  - ID fields: no duplicates
+  - Numeric fields: no negatives where unexpected
+  - Object arrays: consistent shape (no missing keys)
+
+Run only if `git diff origin/<target-branch>..HEAD --name-only` shows `.json` files in seed-data or fixtures directories.
+
+### Output Format
+
+Report as a compliance table:
+
+```
+## Merge Compliance Audit — [FEATURE-ID]
+
+| # | Check | Status | Detail |
+|---|-------|:------:|--------|
+| 1 | Ticket Status | PASS | "Ready for Merge" |
+| 2 | Acceptance Criteria | PASS | 14/14 |
+| 3 | Definition of Done | PASS | 7/7 |
+| 4 | Workflow Checklist | PASS | 7/8 (Step 6 pending) |
+| 5 | Merge Checklist Evidence | PASS | 8/8 with evidence |
+| 6 | Completion Log | PASS | 5 entries, bugs documented |
+| 7 | Tracker Sync | PASS | Active Session + Features table correct |
+| 8 | key_facts.md | PASS | N/A — no new infrastructure |
+| 9 | Merge Base | PASS | Up to date with develop |
+| 10 | Working Tree | PASS | Clean |
+| 11 | Data Files | PASS | N/A — no JSON seed files |
+
+**Verdict: READY FOR MERGE** (or **NEEDS FIX — N issues**)
+```
+
+### If issues are found
+
+Fix them directly:
+- Status wrong → update the ticket header
+- AC/DoD unchecked → mark `[x]`
+- Tracker stale → update Active Session and Features table
+- Merge base diverged → `git merge origin/<target-branch>` and resolve conflicts
+- Data file issues → fix the data
+
+After fixing, re-run the audit to confirm all checks pass.
+
+## Notes
+
+- This command automates the compliance portion of the merge review — it does NOT replace code review, QA, or human architectural review
+- Run this AFTER completing Action 8 (Fill Merge Checklist Evidence) and BEFORE Action 9 (Request merge approval)
+- The output should be included in the merge approval request message so the reviewer can skip compliance checks and focus on code quality

package/template/.gemini/commands/audit-merge.toml

@@ -0,0 +1,2 @@
+description = "Run automated compliance audit on the current feature before requesting merge approval"
+prompt = "Read the file .gemini/commands/audit-merge-instructions.md and follow the instructions to audit the current feature for merge readiness."

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

@@ -72,8 +72,14 @@ In the ticket, fill the `## Merge Checklist Evidence` table. For each action (0
 | 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 9: Request merge approval
+## Action 9: Run compliance audit
 
-Verify the Merge Checklist Evidence table is fully filled (all rows `[x]` with real evidence).
+Run `/audit-merge` to verify all compliance checks pass automatically. If any check fails, fix it and re-run until all pass.
+
+Include the audit output in the merge approval request message so the reviewer can skip compliance checks and focus on code/architecture review.
+
+## Action 10: Request merge approval
+
+Verify the compliance audit passed and the Merge Checklist Evidence table is fully filled.
 
 THEN — and only then — request merge approval from the user.