@simplysm/claude 13.0.0-beta.45 → 13.0.0-beta.46
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.
|
@@ -39,11 +39,33 @@ Start by understanding the current project context, then ask questions one at a
|
|
|
39
39
|
- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
|
|
40
40
|
- Commit the design document to git
|
|
41
41
|
|
|
42
|
-
**
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
42
|
+
**Next Steps Guide:**
|
|
43
|
+
|
|
44
|
+
Present the following two workflow paths so the user can see the full process and choose.
|
|
45
|
+
Display the guide in the **user's configured language** (follow the language settings from CLAUDE.md or system instructions).
|
|
46
|
+
|
|
47
|
+
```
|
|
48
|
+
Design complete! Here's how to proceed:
|
|
49
|
+
|
|
50
|
+
--- Path A: With branch isolation (recommended for features/large changes) ---
|
|
51
|
+
|
|
52
|
+
1. /sd-worktree add <name> — Create a worktree branch
|
|
53
|
+
2. /sd-plan — Break into detailed tasks
|
|
54
|
+
3. /sd-plan-dev — Execute tasks in parallel (includes TDD + review)
|
|
55
|
+
4. /sd-commit — Commit
|
|
56
|
+
5. /sd-worktree merge — Merge back to main
|
|
57
|
+
6. /sd-worktree clean — Remove worktree
|
|
58
|
+
|
|
59
|
+
--- Path B: Direct on current branch (quick fixes/small changes) ---
|
|
60
|
+
|
|
61
|
+
1. /sd-plan — Break into detailed tasks
|
|
62
|
+
2. /sd-plan-dev — Execute tasks in parallel (includes TDD + review)
|
|
63
|
+
3. /sd-commit — Commit
|
|
64
|
+
|
|
65
|
+
You can start from any step or skip steps as needed.
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
- Do NOT auto-proceed to any step. Present the overview and wait for the user's choice.
|
|
47
69
|
|
|
48
70
|
## Key Principles
|
|
49
71
|
|
package/package.json
CHANGED
|
@@ -1,79 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: sd-design-dev
|
|
3
|
-
description: Use when brainstorming is complete and the user wants to proceed with planning and implementation - orchestrates worktree setup, planning, and execution
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Design to Development Pipeline
|
|
7
|
-
|
|
8
|
-
## Overview
|
|
9
|
-
|
|
10
|
-
Orchestrate the full design-to-development pipeline after sd-brainstorm. Asks about branch isolation, then chains the right skills automatically.
|
|
11
|
-
|
|
12
|
-
## The Process
|
|
13
|
-
|
|
14
|
-
```dot
|
|
15
|
-
digraph pipeline {
|
|
16
|
-
rankdir=TB;
|
|
17
|
-
|
|
18
|
-
"Ask: use worktree?" [shape=diamond];
|
|
19
|
-
|
|
20
|
-
subgraph cluster_worktree {
|
|
21
|
-
label="With Worktree";
|
|
22
|
-
"Skill: sd-worktree add" [shape=box];
|
|
23
|
-
}
|
|
24
|
-
|
|
25
|
-
"Skill: sd-plan" [shape=box];
|
|
26
|
-
"Skill: sd-plan-dev" [shape=box];
|
|
27
|
-
"Guide: sd-worktree merge/clean" [shape=box, style=dashed];
|
|
28
|
-
"Done" [shape=ellipse];
|
|
29
|
-
|
|
30
|
-
"Ask: use worktree?" -> "Skill: sd-worktree add" [label="yes"];
|
|
31
|
-
"Ask: use worktree?" -> "Skill: sd-plan" [label="no"];
|
|
32
|
-
"Skill: sd-worktree add" -> "Skill: sd-plan";
|
|
33
|
-
"Skill: sd-plan" -> "Skill: sd-plan-dev";
|
|
34
|
-
"Skill: sd-plan-dev" -> "Guide: sd-worktree merge/clean" [label="if worktree"];
|
|
35
|
-
"Skill: sd-plan-dev" -> "Done" [label="if no worktree"];
|
|
36
|
-
"Guide: sd-worktree merge/clean" -> "Done";
|
|
37
|
-
}
|
|
38
|
-
```
|
|
39
|
-
|
|
40
|
-
### Step 1: Ask about worktree
|
|
41
|
-
|
|
42
|
-
Ask the user (via AskUserQuestion):
|
|
43
|
-
|
|
44
|
-
> "Worktree로 브랜치를 분리할까요?"
|
|
45
|
-
> - Yes (Recommended) — 별도 브랜치에서 작업 후 merge
|
|
46
|
-
> - No — 현재 브랜치에서 직접 작업
|
|
47
|
-
|
|
48
|
-
### Step 2: Worktree setup (if yes)
|
|
49
|
-
|
|
50
|
-
Invoke `/sd-worktree` with `add` and the feature name derived from the brainstorm context.
|
|
51
|
-
|
|
52
|
-
After worktree is created, continue to Step 3 (do NOT stop).
|
|
53
|
-
|
|
54
|
-
### Step 3: Plan
|
|
55
|
-
|
|
56
|
-
Invoke `/sd-plan` — creates the implementation plan from the design.
|
|
57
|
-
|
|
58
|
-
After plan is saved and user approves, continue to Step 4 (do NOT stop).
|
|
59
|
-
|
|
60
|
-
### Step 4: Execute
|
|
61
|
-
|
|
62
|
-
Invoke `/sd-plan-dev` — executes the plan task-by-task with parallel agents and reviews.
|
|
63
|
-
|
|
64
|
-
### Step 5: Post-completion guide (worktree only)
|
|
65
|
-
|
|
66
|
-
If a worktree was created in Step 2, inform the user:
|
|
67
|
-
|
|
68
|
-
> "구현이 완료되었습니다. 다음 명령으로 merge 및 정리를 진행하세요:"
|
|
69
|
-
> 1. `/sd-worktree merge` — worktree 브랜치를 main에 merge
|
|
70
|
-
> 2. `/sd-worktree clean <name>` — worktree 제거 및 브랜치 삭제
|
|
71
|
-
|
|
72
|
-
Do NOT execute merge/clean automatically.
|
|
73
|
-
|
|
74
|
-
## Key Rules
|
|
75
|
-
|
|
76
|
-
- Each skill invocation follows that skill's own process completely
|
|
77
|
-
- Do NOT skip any skill in the chain
|
|
78
|
-
- If any skill asks for user input, wait for the answer before proceeding
|
|
79
|
-
- After sd-plan-dev completes, do NOT auto-merge — guide only
|