create-sdd-project 0.9.0 → 0.9.2
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 +1 -1
- package/template/.claude/settings.json +1 -1
- package/template/.claude/skills/development-workflow/SKILL.md +7 -6
- package/template/.claude/skills/development-workflow/references/complexity-guide.md +1 -1
- package/template/.claude/skills/development-workflow/references/merge-checklist.md +5 -3
- package/template/.gemini/skills/development-workflow/SKILL.md +7 -6
- package/template/.gemini/skills/development-workflow/references/complexity-guide.md +1 -1
- package/template/.gemini/skills/development-workflow/references/merge-checklist.md +5 -3
- package/template/CLAUDE.md +4 -3
package/package.json
CHANGED
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
"hooks": [
|
|
20
20
|
{
|
|
21
21
|
"type": "command",
|
|
22
|
-
"command": "echo '{\"additionalContext\": \"Context was compacted. BEFORE doing anything else:
|
|
22
|
+
"command": "echo '{\"additionalContext\": \"Context was compacted. BEFORE doing anything else: (1) Read the product tracker Active Session (docs/project_notes/product-tracker.md) for context recovery. (2) Re-read the SKILL.md for your current workflow (.claude/skills/development-workflow/SKILL.md) to know what actions are required at your current step. (3) If at Step 5 or later, you MUST read references/merge-checklist.md and fill the Merge Checklist Evidence table in the ticket before requesting merge approval.\"}'",
|
|
23
23
|
"statusMessage": "Injecting recovery context..."
|
|
24
24
|
}
|
|
25
25
|
]
|
|
@@ -59,9 +59,9 @@ Ask user to classify complexity before starting. See `references/complexity-guid
|
|
|
59
59
|
|
|
60
60
|
| Tier | Spec | Ticket | Plan | QA |
|
|
61
61
|
|------|:----:|:------:|:----:|:--:|
|
|
62
|
-
| Simple | Skip |
|
|
63
|
-
| Standard | Yes |
|
|
64
|
-
| Complex | Yes |
|
|
62
|
+
| Simple | Skip | Lite | Skip | Skip |
|
|
63
|
+
| Standard | Yes | Full | Yes | Yes |
|
|
64
|
+
| Complex | Yes | Full + ADR | Yes | Yes |
|
|
65
65
|
|
|
66
66
|
---
|
|
67
67
|
|
|
@@ -85,9 +85,10 @@ 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. **
|
|
89
|
-
4. **
|
|
90
|
-
5.
|
|
88
|
+
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.**
|
|
89
|
+
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.**
|
|
90
|
+
5. **Complex:** Also review `decisions.md` for related ADRs
|
|
91
|
+
6. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity. Update Features table: status `in-progress`, step `1/6`
|
|
91
92
|
|
|
92
93
|
**→ CHECKPOINT: Ticket Approval** (Std/Cplx only — Simple skips to Step 3)
|
|
93
94
|
|
|
@@ -71,7 +71,7 @@ Complexity and Autonomy Level combine to determine the effective workflow overhe
|
|
|
71
71
|
|
|
72
72
|
| Combination | Effect |
|
|
73
73
|
|-------------|--------|
|
|
74
|
-
| Simple + Any Level |
|
|
74
|
+
| Simple + Any Level | Lite ticket, no spec/plan/QA (branch → lite ticket → TDD → commit → PR + merge checklist) |
|
|
75
75
|
| Standard + L1 | Maximum oversight (5 checkpoints) |
|
|
76
76
|
| Standard + L2 | Balanced (Plan + Merge checkpoints only) |
|
|
77
77
|
| Standard + L3-4 | Fast execution, quality gates + QA still enforced |
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
> Execute ALL actions below IN ORDER before requesting merge approval from the user.
|
|
4
4
|
> Do NOT skip any action. Do NOT request merge approval until every action is complete.
|
|
5
5
|
|
|
6
|
-
## Action 0: Validate ticket structure
|
|
6
|
+
## Action 0: Validate ticket structure
|
|
7
7
|
|
|
8
8
|
Re-read the ticket file (`docs/tickets/<feature-id>.md`).
|
|
9
9
|
|
|
@@ -11,11 +11,13 @@ Verify it contains ALL required sections: **Acceptance Criteria**, **Definition
|
|
|
11
11
|
|
|
12
12
|
**If ANY section is missing**, add it from `references/ticket-template.md` before continuing.
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
**Simple (lite ticket):** Verify same sections exist. Spec and Implementation Plan may be minimal (one-liner / N/A).
|
|
15
|
+
|
|
16
|
+
## Action 1: Mark all items
|
|
15
17
|
|
|
16
18
|
In the ticket file, mark ALL items `[x]` in:
|
|
17
19
|
|
|
18
|
-
- **Workflow Checklist** —
|
|
20
|
+
- **Workflow Checklist** — all steps that apply to this complexity tier (Simple: 1, 3, 4, 5. Standard: 0–5. Complex: 0–5)
|
|
19
21
|
- **Acceptance Criteria** — every item
|
|
20
22
|
- **Definition of Done** — every item
|
|
21
23
|
|
|
@@ -59,9 +59,9 @@ Ask user to classify complexity before starting. See `references/complexity-guid
|
|
|
59
59
|
|
|
60
60
|
| Tier | Spec | Ticket | Plan | QA |
|
|
61
61
|
|------|:----:|:------:|:----:|:--:|
|
|
62
|
-
| Simple | Skip |
|
|
63
|
-
| Standard | Yes |
|
|
64
|
-
| Complex | Yes |
|
|
62
|
+
| Simple | Skip | Lite | Skip | Skip |
|
|
63
|
+
| Standard | Yes | Full | Yes | Yes |
|
|
64
|
+
| Complex | Yes | Full + ADR | Yes | Yes |
|
|
65
65
|
|
|
66
66
|
---
|
|
67
67
|
|
|
@@ -85,9 +85,10 @@ 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. **
|
|
89
|
-
4. **
|
|
90
|
-
5.
|
|
88
|
+
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.**
|
|
89
|
+
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.**
|
|
90
|
+
5. **Complex:** Also review `decisions.md` for related ADRs
|
|
91
|
+
6. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity. Update Features table: status `in-progress`, step `1/6`
|
|
91
92
|
|
|
92
93
|
**→ CHECKPOINT: Ticket Approval** (Std/Cplx only — Simple skips to Step 3)
|
|
93
94
|
|
|
@@ -71,7 +71,7 @@ Complexity and Autonomy Level combine to determine the effective workflow overhe
|
|
|
71
71
|
|
|
72
72
|
| Combination | Effect |
|
|
73
73
|
|-------------|--------|
|
|
74
|
-
| Simple + Any Level |
|
|
74
|
+
| Simple + Any Level | Lite ticket, no spec/plan/QA (branch → lite ticket → TDD → commit → PR + merge checklist) |
|
|
75
75
|
| Standard + L1 | Maximum oversight (5 checkpoints) |
|
|
76
76
|
| Standard + L2 | Balanced (Plan + Merge checkpoints only) |
|
|
77
77
|
| Standard + L3-4 | Fast execution, quality gates + QA still enforced |
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
> Execute ALL actions below IN ORDER before requesting merge approval from the user.
|
|
4
4
|
> Do NOT skip any action. Do NOT request merge approval until every action is complete.
|
|
5
5
|
|
|
6
|
-
## Action 0: Validate ticket structure
|
|
6
|
+
## Action 0: Validate ticket structure
|
|
7
7
|
|
|
8
8
|
Re-read the ticket file (`docs/tickets/<feature-id>.md`).
|
|
9
9
|
|
|
@@ -11,11 +11,13 @@ Verify it contains ALL required sections: **Acceptance Criteria**, **Definition
|
|
|
11
11
|
|
|
12
12
|
**If ANY section is missing**, add it from `references/ticket-template.md` before continuing.
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
**Simple (lite ticket):** Verify same sections exist. Spec and Implementation Plan may be minimal (one-liner / N/A).
|
|
15
|
+
|
|
16
|
+
## Action 1: Mark all items
|
|
15
17
|
|
|
16
18
|
In the ticket file, mark ALL items `[x]` in:
|
|
17
19
|
|
|
18
|
-
- **Workflow Checklist** —
|
|
20
|
+
- **Workflow Checklist** — all steps that apply to this complexity tier (Simple: 1, 3, 4, 5. Standard: 0–5. Complex: 0–5)
|
|
19
21
|
- **Acceptance Criteria** — every item
|
|
20
22
|
- **Definition of Done** — every item
|
|
21
23
|
|
package/template/CLAUDE.md
CHANGED
|
@@ -14,6 +14,7 @@ After context compaction or new session — BEFORE continuing work:
|
|
|
14
14
|
|
|
15
15
|
1. Read product tracker (`docs/project_notes/product-tracker.md`) → **Active Session**
|
|
16
16
|
2. If active feature → read referenced ticket in `docs/tickets/`
|
|
17
|
-
3.
|
|
18
|
-
4.
|
|
19
|
-
5.
|
|
17
|
+
3. Re-read the workflow skill (`.claude/skills/development-workflow/SKILL.md`) to know what actions the current step requires
|
|
18
|
+
4. If at Step 5 or later → read `references/merge-checklist.md` and check if the ticket's `## Merge Checklist Evidence` table needs to be filled
|
|
19
|
+
5. Do NOT proceed past any checkpoint without user confirmation (respect autonomy level)
|
|
20
|
+
6. If Active Session shows a pending checkpoint, ask before continuing
|