create-sdd-project 0.8.9 → 0.9.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-sdd-project",
-  "version": "0.8.9",
+  "version": "0.9.1",
   "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

@@ -59,9 +59,9 @@ Ask user to classify complexity before starting. See `references/complexity-guid
 
 | Tier | Spec | Ticket | Plan | QA |
 |------|:----:|:------:|:----:|:--:|
-| Simple | Skip | Skip | Skip | Skip |
-| Standard | Yes | Yes | Yes | Yes |
-| Complex | Yes | Yes + ADR | Yes | Yes |
+| Simple | Skip | Lite | Skip | Skip |
+| Standard | Yes | Full | Yes | Yes |
+| Complex | Yes | Full + ADR | Yes | Yes |
 
 ---
 
@@ -85,9 +85,10 @@ 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.**
-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`
+3. **Simple:** Generate a **lite ticket** at `docs/tickets/<feature-id>-<short-desc>.md` using `references/ticket-template.md`. Fill the header and a one-line `## Spec > Description`. Set `## Implementation Plan` to `N/A — Simple task`. Fill lightweight Acceptance Criteria and Definition of Done. Set Workflow Checklist to Steps 1, 3, 4, 5 only. Leave Completion Log and Merge Checklist Evidence empty (filled in later steps). **Verify the ticket contains ALL 7 sections.**
+4. **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.**
+5. **Complex:** Also review `decisions.md` for related ADRs
+6. 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)
 
@@ -153,7 +154,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 
 **→ CHECKPOINT: Merge Approval**
 
-**STOP.** Read `references/merge-checklist.md` and execute ALL actions in order. Do NOT request merge approval until every action is done.
+**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.
 
 ---
 

package/template/.claude/skills/development-workflow/references/complexity-guide.md

@@ -71,7 +71,7 @@ Complexity and Autonomy Level combine to determine the effective workflow overhe
 
 | Combination | Effect |
 |-------------|--------|
-| Simple + Any Level | Minimal overhead (branch → TDD → commit → PR) |
+| Simple + Any Level | Lite ticket, no spec/plan/QA (branch → lite ticket → TDD → commit → PR + merge checklist) |
 | Standard + L1 | Maximum oversight (5 checkpoints) |
 | Standard + L2 | Balanced (Plan + Merge checkpoints only) |
 | Standard + L3-4 | Fast execution, quality gates + QA still enforced |

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

@@ -3,19 +3,21 @@
 > 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)
+## Action 0: Validate ticket structure
 
 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**.
+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)
+**Simple (lite ticket):** Verify same sections exist. Spec and Implementation Plan may be minimal (one-liner / N/A).
+
+## Action 1: Mark all items
 
 In the ticket file, mark ALL items `[x]` in:
 
-- **Workflow Checklist** — Steps 0 through 5 (all that apply to this complexity tier)
+- **Workflow Checklist** — all steps that apply to this complexity tier (Simple: 1, 3, 4, 5. Standard: 0–5. Complex: 0–5)
 - **Acceptance Criteria** — every item
 - **Definition of Done** — every item
 
@@ -46,6 +48,17 @@ Commit ALL documentation updates from actions 0–4. Use commit message: `docs:
 
 Run `git status`. **No unstaged or untracked files allowed.** If any remain, stage and commit them.
 
-## Action 7: Request merge approval
+## 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

@@ -59,9 +59,9 @@ Ask user to classify complexity before starting. See `references/complexity-guid
 
 | Tier | Spec | Ticket | Plan | QA |
 |------|:----:|:------:|:----:|:--:|
-| Simple | Skip | Skip | Skip | Skip |
-| Standard | Yes | Yes | Yes | Yes |
-| Complex | Yes | Yes + ADR | Yes | Yes |
+| Simple | Skip | Lite | Skip | Skip |
+| Standard | Yes | Full | Yes | Yes |
+| Complex | Yes | Full + ADR | Yes | Yes |
 
 ---
 
@@ -85,9 +85,10 @@ 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.**
-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`
+3. **Simple:** Generate a **lite ticket** at `docs/tickets/<feature-id>-<short-desc>.md` using `references/ticket-template.md`. Fill the header and a one-line `## Spec > Description`. Set `## Implementation Plan` to `N/A — Simple task`. Fill lightweight Acceptance Criteria and Definition of Done. Set Workflow Checklist to Steps 1, 3, 4, 5 only. Leave Completion Log and Merge Checklist Evidence empty (filled in later steps). **Verify the ticket contains ALL 7 sections.**
+4. **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.**
+5. **Complex:** Also review `decisions.md` for related ADRs
+6. 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)
 
@@ -153,7 +154,7 @@ Update tracker (Active Session + Features table): step `4/6 (Finalize)`. Mark ti
 
 **→ CHECKPOINT: Merge Approval**
 
-**STOP.** Read `references/merge-checklist.md` and execute ALL actions in order. Do NOT request merge approval until every action is done.
+**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.
 
 ---
 

package/template/.gemini/skills/development-workflow/references/complexity-guide.md

@@ -71,7 +71,7 @@ Complexity and Autonomy Level combine to determine the effective workflow overhe
 
 | Combination | Effect |
 |-------------|--------|
-| Simple + Any Level | Minimal overhead (branch → TDD → commit → PR) |
+| Simple + Any Level | Lite ticket, no spec/plan/QA (branch → lite ticket → TDD → commit → PR + merge checklist) |
 | Standard + L1 | Maximum oversight (5 checkpoints) |
 | Standard + L2 | Balanced (Plan + Merge checkpoints only) |
 | Standard + L3-4 | Fast execution, quality gates + QA still enforced |

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

@@ -3,19 +3,21 @@
 > 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)
+## Action 0: Validate ticket structure
 
 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**.
+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)
+**Simple (lite ticket):** Verify same sections exist. Spec and Implementation Plan may be minimal (one-liner / N/A).
+
+## Action 1: Mark all items
 
 In the ticket file, mark ALL items `[x]` in:
 
-- **Workflow Checklist** — Steps 0 through 5 (all that apply to this complexity tier)
+- **Workflow Checklist** — all steps that apply to this complexity tier (Simple: 1, 3, 4, 5. Standard: 0–5. Complex: 0–5)
 - **Acceptance Criteria** — every item
 - **Definition of Done** — every item
 
@@ -46,6 +48,17 @@ Commit ALL documentation updates from actions 0–4. Use commit message: `docs:
 
 Run `git status`. **No unstaged or untracked files allowed.** If any remain, stage and commit them.
 
-## Action 7: Request merge approval
+## 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]*