lee-spec-kit 0.6.2 β†’ 0.6.4

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 CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lee-spec-kit",
3
- "version": "0.6.2",
3
+ "version": "0.6.4",
4
4
  "description": "Project documentation structure generator for AI-assisted development",
5
5
  "type": "module",
6
6
  "bin": {
@@ -70,14 +70,14 @@ main
70
70
 
71
71
  ## Automation Workflow
72
72
 
73
- > πŸ“– Refer to CLI built-in step guides.
74
-
75
- | Workflow | Guide |
76
- | -------------- | -------------------------------- |
77
- | Feature Start | CLI built-in `create-feature` |
78
- | Issue Creation | CLI built-in `create-issue` |
79
- | Task Execution | CLI built-in `execute-task` |
80
- | PR Creation | CLI built-in `create-pr` |
73
+ > πŸ“– Read each step guide first with `docs get`.
74
+
75
+ | Workflow | Guide |
76
+ | -------------- | -------------------------------------------------- |
77
+ | Feature Start | `npx lee-spec-kit docs get create-feature --json` |
78
+ | Issue Creation | `npx lee-spec-kit docs get create-issue --json` |
79
+ | Task Execution | `npx lee-spec-kit docs get execute-task --json` |
80
+ | PR Creation | `npx lee-spec-kit docs get create-pr --json` |
81
81
 
82
82
  ### Branch Creation
83
83
 
@@ -65,7 +65,7 @@ For file links within the repo in PR body, **always use current branch name**:
65
65
  ## Screenshots (Frontend / UI changes)
66
66
 
67
67
  <!-- If there are no UI changes, or if screenshot upload is disabled (e.g. `.lee-spec-kit.json` has `pr.screenshots.upload: false`), remove this section. -->
68
- > If you follow the Release assets upload flow in the CLI built-in `create-pr` guide, you can include images in the PR body without committing files to your branch.
68
+ > If you follow the Release assets upload flow in `npx lee-spec-kit docs get create-pr --json`, you can include images in the PR body without committing files to your branch.
69
69
 
70
70
  {Screenshot markdown (e.g. ![](URL))}
71
71
 
@@ -15,14 +15,20 @@ Guide for creating GitHub Issues.
15
15
 
16
16
  ### 1. Prepare Issue Draft
17
17
 
18
- > πŸ“– **Use the CLI built-in issue template policy. Generate a draft first and treat it as the source of truth.**
18
+ > πŸ“– **Read procedure/template via `docs get` first, then generate a draft and treat it as the source of truth.**
19
19
 
20
20
  ```bash
21
- # Generate draft body first (no remote action)
21
+ # 1) Read procedure + template policy
22
+ npx lee-spec-kit docs get create-issue --json
23
+ npx lee-spec-kit docs get issue-template --json
24
+
25
+ # 2) Generate draft body (no remote action)
22
26
  npx lee-spec-kit github issue F001 --json
23
27
  ```
24
28
 
25
- Use the generated `bodyFile` in JSON output as the draft body to review/share.
29
+ Use `docs get issue-template --json` output as the section policy,
30
+ and `github issue --json` output `body` as the first draft to review/share.
31
+ If needed, use `bodyFile` as the filesystem source.
26
32
 
27
33
  | Item | Format |
28
34
  | -------- | ------------------------------------------- |
@@ -38,9 +44,11 @@ Use the generated `bodyFile` in JSON output as the draft body to review/share.
38
44
  Before creating issue, share and wait for explicit approval (OK):
39
45
 
40
46
  - Title
41
- - Full body draft (from `bodyFile`)
47
+ - Full body draft (from `body`)
42
48
  - Labels
43
49
 
50
+ Also refine Goals/Completion Criteria based on spec before creating.
51
+
44
52
  ### 3. Create Issue
45
53
 
46
54
  ```bash
@@ -58,5 +66,5 @@ npx lee-spec-kit github issue F001 --create --confirm OK --labels enhancement
58
66
 
59
67
  ## Reference Documents
60
68
 
61
- - **Draft generator (CLI built-in)**: `npx lee-spec-kit github issue <feature-name>`
69
+ - **Draft generator**: `npx lee-spec-kit github issue <feature-name>`
62
70
  - **Approval rule**: share title/body/labels first, then run `--create --confirm OK`
@@ -17,14 +17,23 @@ Guide for creating Pull Requests.
17
17
 
18
18
  ### 1. Prepare PR Draft
19
19
 
20
- > πŸ“– **Use the CLI built-in PR template policy. Generate a draft first and treat it as the source of truth.**
20
+ > πŸ“– **Read procedure/template via `docs get` first, then generate a draft and treat it as the source of truth.**
21
21
 
22
22
  ```bash
23
- # Generate draft body first (no remote action)
23
+ # 1) Read procedure + template policy
24
+ npx lee-spec-kit docs get create-pr --json
25
+ npx lee-spec-kit docs get pr-template --json
26
+
27
+ # 2) Generate draft body (no remote action)
24
28
  npx lee-spec-kit github pr F001 --json
29
+ # - Force screenshots section: --screenshots on
30
+ # - Force Mermaid section: --mermaid on
31
+ # - Auto policy (default): --screenshots auto --mermaid auto
25
32
  ```
26
33
 
27
- Use the generated `bodyFile` in JSON output as the PR draft body.
34
+ Use `docs get pr-template --json` output as the section policy,
35
+ and `github pr --json` output `body` as the first PR draft body.
36
+ If needed, use `bodyFile` as the filesystem source.
28
37
 
29
38
  | Item | Format |
30
39
  | -------- | ---------------------------------- |
@@ -122,9 +131,11 @@ echo \"![](https://github.com/${REPO}/releases/download/${TAG}/ui-1.png)\"
122
131
  Before creating PR, share the following **in a code block** and wait for **explicit approval (OK)**:
123
132
 
124
133
  - Title
125
- - Full body draft (from `bodyFile`)
134
+ - Full body draft (from `body`)
126
135
  - Labels (at least 1; cannot be empty)
127
136
 
137
+ Before approval/create, refine the generated draft's Changes/Tests sections based on actual work.
138
+
128
139
  ### 5. Create PR
129
140
 
130
141
  ```bash
@@ -178,5 +189,5 @@ Use **current branch name** for file links in PR body:
178
189
 
179
190
  ## Reference Documents
180
191
 
181
- - **Draft generator (CLI built-in)**: `npx lee-spec-kit github pr <feature-name>`
192
+ - **Draft generator**: `npx lee-spec-kit github pr <feature-name>`
182
193
  - **Approval rule**: share title/body/labels first, then run `--create --confirm OK`
@@ -6,7 +6,7 @@ This documentation is organized by feature to help agents quickly understand the
6
6
 
7
7
  | Path | Purpose | Key Documents |
8
8
  | ------------------- | --------------------- | ------------------------------------------------------------- |
9
- | `docs/agents/` | Agent operating rules | `custom.md`, `constitution.md` (engine-managed guides are CLI built-in) |
9
+ | `docs/agents/` | Agent operating rules | `custom.md`, `constitution.md` (engine-managed guides are fetched via `npx lee-spec-kit docs get <doc-id> --json`) |
10
10
  | `docs/prd/` | Product requirements | Project-specific |
11
11
  | `docs/designs/` | Design references | `README.md` (links/guidelines/references) |
12
12
  | `docs/ideas/` | Ideas / to-dos | `README.md` (Idea β†’ Feature promotion rules) |
@@ -20,7 +20,7 @@ This documentation is organized by feature to help agents quickly understand the
20
20
  When you run `lee-spec-kit init`, it creates `.lee-spec-kit.json` in the docs root (default: `docs/`).
21
21
 
22
22
  - Used by `lee-spec-kit feature`, `status`, and `update` to detect docs location / project type / language.
23
- - `docsRepo`, `pushDocs`, `docsRemote` are metadata for the CLI built-in **Docs Push policy** (the CLI does not auto-push).
23
+ - `docsRepo`, `pushDocs`, `docsRemote` are metadata for the CLI-managed **Docs Push policy** (the CLI does not auto-push).
24
24
 
25
25
  ### Fields
26
26
 
@@ -40,9 +40,10 @@ Operating rules for AI code assistants to perform consistent code generation and
40
40
 
41
41
  - **πŸ”΄ Custom Rules (Highest Priority)**: `/docs/agents/custom.md`
42
42
  - **Project Principles**: `/docs/agents/constitution.md`
43
- - **Git Workflow**: CLI built-in policy (`lee-spec-kit context`, `lee-spec-kit github`)
44
- - **Issue Draft Policy**: CLI built-in (`lee-spec-kit github issue --json`)
45
- - **PR Draft Policy**: CLI built-in (`lee-spec-kit github pr --json`)
43
+ - **Agent Root Guide**: `npx lee-spec-kit docs get agents --json`
44
+ - **Git Workflow**: `npx lee-spec-kit docs get git-workflow --json`
45
+ - **Issue Procedure/Template**: `npx lee-spec-kit docs get create-issue --json` β†’ `npx lee-spec-kit docs get issue-template --json`
46
+ - **PR Procedure/Template**: `npx lee-spec-kit docs get create-pr --json` β†’ `npx lee-spec-kit docs get pr-template --json`
46
47
 
47
48
  ### PRD
48
49
 
@@ -52,7 +53,7 @@ Operating rules for AI code assistants to perform consistent code generation and
52
53
 
53
54
  - **BE Features**: `/docs/features/be/{feature-id}/`
54
55
  - **FE Features**: `/docs/features/fe/{feature-id}/`
55
- - **Template (SSOT)**: CLI built-in feature-base template
56
+ - **Template (SSOT)**: docs generated via `npx lee-spec-kit feature <name>`
56
57
 
57
58
  ---
58
59
 
@@ -65,8 +66,9 @@ docs/
65
66
  β”‚ β”œβ”€β”€ custom.md # Project-specific custom rules
66
67
  β”‚ └── constitution.md # Project principles
67
68
  β”‚
68
- β”‚ # Engine-managed policy guides are CLI built-ins (not synced into docs):
69
- β”‚ # - agents.md / skills/* / git-workflow / issue-template / pr-template
69
+ β”‚ # Engine-managed policy guides are not synced into project docs.
70
+ β”‚ # - list: npx lee-spec-kit docs list --json
71
+ β”‚ # - example: npx lee-spec-kit docs get git-workflow --json
70
72
  β”œβ”€β”€ prd/ # Product requirements
71
73
  β”œβ”€β”€ designs/ # Design references
72
74
  β”œβ”€β”€ ideas/ # Pre-feature ideas / to-dos
@@ -80,14 +82,14 @@ docs/
80
82
 
81
83
  ## Request Type Processes
82
84
 
83
- > πŸ“– Refer to CLI built-in skill guides for detailed processes.
85
+ > πŸ“– Read each process guide first with `docs get`.
84
86
 
85
87
  | Process | Guide |
86
88
  | -------------- | ------------------------------------- |
87
- | New Feature | CLI built-in `create-feature` guide |
88
- | GitHub Issue | CLI built-in `create-issue` guide |
89
- | Pull Request | CLI built-in `create-pr` guide |
90
- | Task Execution | CLI built-in `execute-task` guide |
89
+ | New Feature | `npx lee-spec-kit docs get create-feature --json` |
90
+ | GitHub Issue | `npx lee-spec-kit docs get create-issue --json` |
91
+ | Pull Request | `npx lee-spec-kit docs get create-pr --json` |
92
+ | Task Execution | `npx lee-spec-kit docs get execute-task --json` |
91
93
 
92
94
  ### Additional Rules (Fullstack)
93
95
 
@@ -6,7 +6,7 @@ This documentation is organized by feature to help agents quickly understand the
6
6
 
7
7
  | Path | Purpose | Key Documents |
8
8
  | ---------------- | --------------------- | ------------------------------------------------------------- |
9
- | `docs/agents/` | Agent operating rules | `custom.md`, `constitution.md` (engine-managed guides are CLI built-in) |
9
+ | `docs/agents/` | Agent operating rules | `custom.md`, `constitution.md` (engine-managed guides are fetched via `npx lee-spec-kit docs get <doc-id> --json`) |
10
10
  | `docs/prd/` | Product requirements | Project-specific |
11
11
  | `docs/designs/` | Design references | `README.md` (links/guidelines/references) |
12
12
  | `docs/ideas/` | Ideas / to-dos | `README.md` (Idea β†’ Feature promotion rules) |
@@ -19,7 +19,7 @@ This documentation is organized by feature to help agents quickly understand the
19
19
  When you run `lee-spec-kit init`, it creates `.lee-spec-kit.json` in the docs root (default: `docs/`).
20
20
 
21
21
  - Used by `lee-spec-kit feature`, `status`, and `update` to detect docs location / project type / language.
22
- - `docsRepo`, `pushDocs`, `docsRemote` are metadata for the CLI built-in **Docs Push policy** (the CLI does not auto-push).
22
+ - `docsRepo`, `pushDocs`, `docsRemote` are metadata for the CLI-managed **Docs Push policy** (the CLI does not auto-push).
23
23
 
24
24
  ### Fields
25
25
 
@@ -40,14 +40,15 @@ Operating rules for AI code assistants to perform consistent code generation and
40
40
 
41
41
  - **πŸ”΄ Custom Rules (Highest Priority)**: `/docs/agents/custom.md`
42
42
  - **Project Principles**: `/docs/agents/constitution.md`
43
- - **Git Workflow**: CLI built-in policy (`lee-spec-kit context`, `lee-spec-kit github`)
44
- - **Issue Draft Policy**: CLI built-in (`lee-spec-kit github issue --json`)
45
- - **PR Draft Policy**: CLI built-in (`lee-spec-kit github pr --json`)
43
+ - **Agent Root Guide**: `npx lee-spec-kit docs get agents --json`
44
+ - **Git Workflow**: `npx lee-spec-kit docs get git-workflow --json`
45
+ - **Issue Procedure/Template**: `npx lee-spec-kit docs get create-issue --json` β†’ `npx lee-spec-kit docs get issue-template --json`
46
+ - **PR Procedure/Template**: `npx lee-spec-kit docs get create-pr --json` β†’ `npx lee-spec-kit docs get pr-template --json`
46
47
 
47
48
  ### Features
48
49
 
49
50
  - **Feature Docs**: `/docs/features/{feature-id}/`
50
- - **Template (SSOT)**: CLI built-in feature-base template
51
+ - **Template (SSOT)**: docs generated via `npx lee-spec-kit feature <name>`
51
52
 
52
53
  ---
53
54
 
@@ -60,8 +61,9 @@ docs/
60
61
  β”‚ β”œβ”€β”€ custom.md # Project-specific custom rules
61
62
  β”‚ └── constitution.md # Project principles
62
63
  β”‚
63
- β”‚ # Engine-managed policy guides are CLI built-ins (not synced into docs):
64
- β”‚ # - agents.md / skills/* / git-workflow / issue-template / pr-template
64
+ β”‚ # Engine-managed policy guides are not synced into project docs.
65
+ β”‚ # - list: npx lee-spec-kit docs list --json
66
+ β”‚ # - example: npx lee-spec-kit docs get git-workflow --json
65
67
  β”œβ”€β”€ prd/ # Product requirements
66
68
  β”œβ”€β”€ designs/ # Design references
67
69
  β”œβ”€β”€ ideas/ # Pre-feature ideas / to-dos
@@ -74,14 +76,14 @@ docs/
74
76
 
75
77
  ## Request Type Processes
76
78
 
77
- > πŸ“– Refer to CLI built-in skill guides for detailed processes.
79
+ > πŸ“– Read each process guide first with `docs get`.
78
80
 
79
81
  | Process | Guide |
80
82
  | -------------- | ------------------------------------- |
81
- | New Feature | CLI built-in `create-feature` guide |
82
- | GitHub Issue | CLI built-in `create-issue` guide |
83
- | Pull Request | CLI built-in `create-pr` guide |
84
- | Task Execution | CLI built-in `execute-task` guide |
83
+ | New Feature | `npx lee-spec-kit docs get create-feature --json` |
84
+ | GitHub Issue | `npx lee-spec-kit docs get create-issue --json` |
85
+ | Pull Request | `npx lee-spec-kit docs get create-pr --json` |
86
+ | Task Execution | `npx lee-spec-kit docs get execute-task --json` |
85
87
 
86
88
  ---
87
89
 
@@ -70,14 +70,14 @@ main
70
70
 
71
71
  ## μžλ™ν™” μ›Œν¬ν”Œλ‘œμš°
72
72
 
73
- > πŸ“– 단계별 상세 κ°€μ΄λ“œλŠ” CLI λ‚΄μž₯ κ°€μ΄λ“œλ₯Ό μ°Έμ‘°ν•˜μ„Έμš”.
74
-
75
- | μ›Œν¬ν”Œλ‘œμš° | κ°€μ΄λ“œ |
76
- | ------------ | ------------------------------- |
77
- | Feature μ‹œμž‘ | CLI λ‚΄μž₯ `create-feature` |
78
- | Issue 생성 | CLI λ‚΄μž₯ `create-issue` |
79
- | νƒœμŠ€ν¬ μ‹€ν–‰ | CLI λ‚΄μž₯ `execute-task` |
80
- | PR 생성 | CLI λ‚΄μž₯ `create-pr` |
73
+ > πŸ“– 단계별 상세 κ°€μ΄λ“œλŠ” `docs get` λͺ…λ ΉμœΌλ‘œ λ¨Όμ € ν™•μΈν•˜μ„Έμš”.
74
+
75
+ | μ›Œν¬ν”Œλ‘œμš° | κ°€μ΄λ“œ |
76
+ | ------------ | -------------------------------------------------- |
77
+ | Feature μ‹œμž‘ | `npx lee-spec-kit docs get create-feature --json` |
78
+ | Issue 생성 | `npx lee-spec-kit docs get create-issue --json` |
79
+ | νƒœμŠ€ν¬ μ‹€ν–‰ | `npx lee-spec-kit docs get execute-task --json` |
80
+ | PR 생성 | `npx lee-spec-kit docs get create-pr --json` |
81
81
 
82
82
  ### 브랜치 생성
83
83
 
@@ -63,7 +63,7 @@ PR λ³Έλ¬Έμ—μ„œ 레포 λ‚΄ 파일 λ§ν¬λŠ” **λ°˜λ“œμ‹œ ν˜„μž¬ 브랜치λͺ…을
63
63
  ## μŠ€ν¬λ¦°μƒ· (ν”„λ‘ νŠΈμ—”λ“œ / UI λ³€κ²½ μ‹œ)
64
64
 
65
65
  <!-- UI 변경이 μ•„λ‹ˆκ±°λ‚˜, μŠ€ν¬λ¦°μƒ·μ„ μ—…λ‘œλ“œν•˜μ§€ μ•Šμ•˜λ‹€λ©΄(예: `.lee-spec-kit.json`의 `pr.screenshots.upload: false`) 이 μ„Ήμ…˜μ€ μ œκ±°ν•˜μ„Έμš”. -->
66
- > CLI λ‚΄μž₯ `create-pr` κ°€μ΄λ“œμ˜ Release assets μ—…λ‘œλ“œ 절차λ₯Ό μ‚¬μš©ν•˜λ©΄ λΈŒλžœμΉ˜μ— νŒŒμΌμ„ μ»€λ°‹ν•˜μ§€ μ•Šκ³ λ„ 이미지λ₯Ό 본문에 포함할 수 μžˆμŠ΅λ‹ˆλ‹€.
66
+ > `npx lee-spec-kit docs get create-pr --json`의 Release assets μ—…λ‘œλ“œ 절차λ₯Ό μ‚¬μš©ν•˜λ©΄ λΈŒλžœμΉ˜μ— νŒŒμΌμ„ μ»€λ°‹ν•˜μ§€ μ•Šκ³ λ„ 이미지λ₯Ό 본문에 포함할 수 μžˆμŠ΅λ‹ˆλ‹€.
67
67
 
68
68
  {μŠ€ν¬λ¦°μƒ· λ§ˆν¬λ‹€μš΄ (예: ![](URL))}
69
69
 
@@ -15,14 +15,20 @@ GitHub Issueλ₯Ό 생성할 λ•Œ λ”°λ₯΄λŠ” κ°€μ΄λ“œμž…λ‹ˆλ‹€.
15
15
 
16
16
  ### 1. 이슈 μ΄ˆμ•ˆ μž‘μ„±
17
17
 
18
- > πŸ“– **CLI λ‚΄μž₯ 이슈 ν…œν”Œλ¦Ώ 정책을 μ‚¬μš©ν•˜μ„Έμš”. λ¨Όμ € μ΄ˆμ•ˆμ„ μƒμ„±ν•˜κ³  이λ₯Ό κΈ°μ€€μœΌλ‘œ μ‚ΌμŠ΅λ‹ˆλ‹€.**
18
+ > πŸ“– **λ¨Όμ € `docs get`으둜 절차/ν…œν”Œλ¦Ώμ„ 읽고, μ΄ˆμ•ˆμ„ 생성해 κΈ°μ€€μœΌλ‘œ μ‚¬μš©ν•˜μ„Έμš”.**
19
19
 
20
20
  ```bash
21
- # λ¨Όμ € μ΄ˆμ•ˆ λ³Έλ¬Έ 생성 (원격 μž‘μ—… μ•„λ‹˜)
21
+ # 1) 절차/ν…œν”Œλ¦Ώ μ •μ±… 확인
22
+ npx lee-spec-kit docs get create-issue --json
23
+ npx lee-spec-kit docs get issue-template --json
24
+
25
+ # 2) μ΄ˆμ•ˆ λ³Έλ¬Έ 생성 (원격 μž‘μ—… μ•„λ‹˜)
22
26
  npx lee-spec-kit github issue F001 --json
23
27
  ```
24
28
 
25
- JSON 좜λ ₯의 `bodyFile` κ²½λ‘œμ— μƒμ„±λœ λ‚΄μš©μ„ μ΄ˆμ•ˆ 본문으둜 μ‚¬μš©ν•˜μ„Έμš”.
29
+ `docs get issue-template --json` 좜λ ₯은 μ„Ήμ…˜ μ •μ±…μœΌλ‘œ 보고,
30
+ `github issue --json`의 `body`λ₯Ό μš°μ„  λ³Έλ¬Έ μ΄ˆμ•ˆμœΌλ‘œ μ‚¬μš©ν•˜μ„Έμš”.
31
+ ν•„μš”ν•˜λ©΄ `bodyFile` 경둜 νŒŒμΌμ„ ν•¨κ»˜ μ°Έκ³ ν•˜μ„Έμš”.
26
32
 
27
33
  | ν•­λͺ© | ν˜•μ‹ |
28
34
  | ------ | ---------------------------------------- |
@@ -38,9 +44,11 @@ JSON 좜λ ₯의 `bodyFile` κ²½λ‘œμ— μƒμ„±λœ λ‚΄μš©μ„ μ΄ˆμ•ˆ 본문으둜 사
38
44
  이슈 생성 μ „ λ‹€μŒ λ‚΄μš©μ„ κ³΅μœ ν•˜κ³  λͺ…μ‹œμ  승인(OK) λŒ€κΈ°:
39
45
 
40
46
  - 제λͺ©
41
- - λ³Έλ¬Έ 전체 μ΄ˆμ•ˆ (`bodyFile` κΈ°μ€€)
47
+ - λ³Έλ¬Έ 전체 μ΄ˆμ•ˆ (`body` κΈ°μ€€)
42
48
  - 라벨
43
49
 
50
+ 생성 μ „ λͺ©ν‘œ/μ™„λ£Œ 기쀀을 spec κΈ°μ€€μœΌλ‘œ κ΅¬μ²΄ν™”ν•˜κ³  κ²€ν† ν•˜μ„Έμš”.
51
+
44
52
  ### 3. 이슈 생성
45
53
 
46
54
  ```bash
@@ -58,5 +66,5 @@ npx lee-spec-kit github issue F001 --create --confirm OK --labels enhancement
58
66
 
59
67
  ## μ°Έμ‘° λ¬Έμ„œ
60
68
 
61
- - **μ΄ˆμ•ˆ 생성기(CLI λ‚΄μž₯)**: `npx lee-spec-kit github issue <feature-name>`
69
+ - **μ΄ˆμ•ˆ 생성기**: `npx lee-spec-kit github issue <feature-name>`
62
70
  - **승인 κ·œμΉ™**: 제λͺ©/λ³Έλ¬Έ/라벨 곡유 ν›„ `--create --confirm OK` μ‹€ν–‰
@@ -17,14 +17,23 @@ Pull Requestλ₯Ό 생성할 λ•Œ λ”°λ₯΄λŠ” κ°€μ΄λ“œμž…λ‹ˆλ‹€.
17
17
 
18
18
  ### 1. PR μ΄ˆμ•ˆ μž‘μ„±
19
19
 
20
- > πŸ“– **CLI λ‚΄μž₯ PR ν…œν”Œλ¦Ώ 정책을 μ‚¬μš©ν•˜μ„Έμš”. λ¨Όμ € μ΄ˆμ•ˆμ„ μƒμ„±ν•˜κ³  이λ₯Ό κΈ°μ€€μœΌλ‘œ μ‚ΌμŠ΅λ‹ˆλ‹€.**
20
+ > πŸ“– **λ¨Όμ € `docs get`으둜 절차/ν…œν”Œλ¦Ώμ„ 읽고, μ΄ˆμ•ˆμ„ 생성해 κΈ°μ€€μœΌλ‘œ μ‚¬μš©ν•˜μ„Έμš”.**
21
21
 
22
22
  ```bash
23
- # λ¨Όμ € μ΄ˆμ•ˆ λ³Έλ¬Έ 생성 (원격 μž‘μ—… μ•„λ‹˜)
23
+ # 1) 절차/ν…œν”Œλ¦Ώ μ •μ±… 확인
24
+ npx lee-spec-kit docs get create-pr --json
25
+ npx lee-spec-kit docs get pr-template --json
26
+
27
+ # 2) μ΄ˆμ•ˆ λ³Έλ¬Έ 생성 (원격 μž‘μ—… μ•„λ‹˜)
24
28
  npx lee-spec-kit github pr F001 --json
29
+ # - μŠ€ν¬λ¦°μƒ· κ°•μ œ 포함: --screenshots on
30
+ # - Mermaid κ°•μ œ 포함: --mermaid on
31
+ # - μžλ™ μ •μ±…(κΈ°λ³Έ): --screenshots auto --mermaid auto
25
32
  ```
26
33
 
27
- JSON 좜λ ₯의 `bodyFile` κ²½λ‘œμ— μƒμ„±λœ λ‚΄μš©μ„ PR μ΄ˆμ•ˆ 본문으둜 μ‚¬μš©ν•˜μ„Έμš”.
34
+ `docs get pr-template --json` 좜λ ₯은 μ„Ήμ…˜ μ •μ±…μœΌλ‘œ 보고,
35
+ `github pr --json`의 `body`λ₯Ό μš°μ„  PR μ΄ˆμ•ˆ 본문으둜 μ‚¬μš©ν•˜μ„Έμš”.
36
+ ν•„μš”ν•˜λ©΄ `bodyFile` 경둜 νŒŒμΌμ„ ν•¨κ»˜ μ°Έκ³ ν•˜μ„Έμš”.
28
37
 
29
38
  | ν•­λͺ© | ν˜•μ‹ |
30
39
  | ------ | ---------------------------------- |
@@ -122,9 +131,11 @@ echo \"![](https://github.com/${REPO}/releases/download/${TAG}/ui-1.png)\"
122
131
  PR 생성 μ „ λ‹€μŒ λ‚΄μš©μ„ **μ½”λ“œλΈ”λ‘μœΌλ‘œ** μ‚¬μš©μžμ—κ²Œ κ³΅μœ ν•˜κ³  **λͺ…μ‹œμ  승인(OK)** λŒ€κΈ°:
123
132
 
124
133
  - 제λͺ©
125
- - λ³Έλ¬Έ 전체 μ΄ˆμ•ˆ (`bodyFile` κΈ°μ€€)
134
+ - λ³Έλ¬Έ 전체 μ΄ˆμ•ˆ (`body` κΈ°μ€€)
126
135
  - 라벨(μ΅œμ†Œ 1개, λΉ„μ›Œλ‘˜ 수 μ—†μŒ)
127
136
 
137
+ 승인/생성 전에 μƒμ„±λœ μ΄ˆμ•ˆμ˜ λ³€κ²½ 사항/ν…ŒμŠ€νŠΈ μ„Ήμ…˜μ„ μ‹€μ œ μž‘μ—… κΈ°μ€€μœΌλ‘œ λ³΄μ™„ν•˜μ„Έμš”.
138
+
128
139
  ### 5. PR 생성
129
140
 
130
141
  ```bash
@@ -178,5 +189,5 @@ PR 본문의 파일 λ§ν¬λŠ” **ν˜„μž¬ 브랜치λͺ…**을 μ‚¬μš©:
178
189
 
179
190
  ## μ°Έμ‘° λ¬Έμ„œ
180
191
 
181
- - **μ΄ˆμ•ˆ 생성기(CLI λ‚΄μž₯)**: `npx lee-spec-kit github pr <feature-name>`
192
+ - **μ΄ˆμ•ˆ 생성기**: `npx lee-spec-kit github pr <feature-name>`
182
193
  - **승인 κ·œμΉ™**: 제λͺ©/λ³Έλ¬Έ/라벨 곡유 ν›„ `--create --confirm OK` μ‹€ν–‰
@@ -6,7 +6,7 @@
6
6
 
7
7
  | 경둜 | λͺ©μ  | 핡심 λ¬Έμ„œ/μ—­ν•  |
8
8
  | ------------------- | -------------------- | ------------------------------------------------------------- |
9
- | `docs/agents/` | μ—μ΄μ „νŠΈ 운영 κ·œμΉ™ | `custom.md`, `constitution.md` (μ—”μ§„ 쒅속 κ°€μ΄λ“œλŠ” CLI λ‚΄μž₯) |
9
+ | `docs/agents/` | μ—μ΄μ „νŠΈ 운영 κ·œμΉ™ | `custom.md`, `constitution.md` (μ—”μ§„ 쒅속 κ°€μ΄λ“œλŠ” `npx lee-spec-kit docs get <doc-id> --json`으둜 쑰회) |
10
10
  | `docs/prd/` | μ œν’ˆ μš”κ΅¬μ‚¬ν•­ | ν”„λ‘œμ νŠΈλ³„ μž‘μ„± |
11
11
  | `docs/designs/` | λ””μžμΈ μ°Έκ³  자료 | `README.md` (링크/κ°€μ΄λ“œ/레퍼런슀) |
12
12
  | `docs/ideas/` | 아이디어/To-do | `README.md` (Idea β†’ Feature 승격 κ·œμΉ™) |
@@ -20,7 +20,7 @@
20
20
  `lee-spec-kit init`을 μ‹€ν–‰ν•˜λ©΄ λ¬Έμ„œ 루트(κΈ°λ³Έ: `docs/`)에 `.lee-spec-kit.json`이 μƒμ„±λ©λ‹ˆλ‹€.
21
21
 
22
22
  - `lee-spec-kit feature`, `status`, `update`μ—μ„œ λ¬Έμ„œ μœ„μΉ˜/ν”„λ‘œμ νŠΈ νƒ€μž…/μ–Έμ–΄λ₯Ό κ°μ§€ν•˜λŠ” μš©λ„λ‘œ μ‚¬μš©λ©λ‹ˆλ‹€.
23
- - `docsRepo`, `pushDocs`, `docsRemote`λŠ” CLI λ‚΄μž₯ **Docs Push μ •μ±…**을 μœ„ν•œ λ©”νƒ€λ°μ΄ν„°μž…λ‹ˆλ‹€. (μžλ™ pushλŠ” ν•˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€)
23
+ - `docsRepo`, `pushDocs`, `docsRemote`λŠ” CLI 관리 **Docs Push μ •μ±…**을 μœ„ν•œ λ©”νƒ€λ°μ΄ν„°μž…λ‹ˆλ‹€. (μžλ™ pushλŠ” ν•˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€)
24
24
 
25
25
  ### ν•„λ“œ
26
26
 
@@ -40,9 +40,10 @@
40
40
 
41
41
  - **πŸ”΄ μ»€μŠ€ν…€ κ·œμΉ™ (μ΅œμš°μ„ )**: `/docs/agents/custom.md`
42
42
  - **ν”„λ‘œμ νŠΈ 원칙**: `/docs/agents/constitution.md`
43
- - **Git μ›Œν¬ν”Œλ‘œμš°**: CLI λ‚΄μž₯ μ •μ±… (`lee-spec-kit context`, `lee-spec-kit github`)
44
- - **이슈 μ΄ˆμ•ˆ μ •μ±…**: CLI λ‚΄μž₯ (`lee-spec-kit github issue --json`)
45
- - **PR μ΄ˆμ•ˆ μ •μ±…**: CLI λ‚΄μž₯ (`lee-spec-kit github pr --json`)
43
+ - **μ—μ΄μ „νŠΈ 루트 κ°€μ΄λ“œ**: `npx lee-spec-kit docs get agents --json`
44
+ - **Git μ›Œν¬ν”Œλ‘œμš°**: `npx lee-spec-kit docs get git-workflow --json`
45
+ - **이슈 절차/ν…œν”Œλ¦Ώ**: `npx lee-spec-kit docs get create-issue --json` β†’ `npx lee-spec-kit docs get issue-template --json`
46
+ - **PR 절차/ν…œν”Œλ¦Ώ**: `npx lee-spec-kit docs get create-pr --json` β†’ `npx lee-spec-kit docs get pr-template --json`
46
47
 
47
48
  ### PRD
48
49
 
@@ -52,7 +53,7 @@
52
53
 
53
54
  - **BE κΈ°λŠ₯**: `/docs/features/be/{feature-id}/`
54
55
  - **FE κΈ°λŠ₯**: `/docs/features/fe/{feature-id}/`
55
- - **ν…œν”Œλ¦Ώ (SSOT)**: CLI λ‚΄μž₯ feature-base ν…œν”Œλ¦Ώ (spec, plan, tasks, decisions)
56
+ - **ν…œν”Œλ¦Ώ (SSOT)**: `npx lee-spec-kit feature <name>`둜 μƒμ„±λœ λ¬Έμ„œ ꡬ쑰 (spec, plan, tasks, decisions)
56
57
 
57
58
  ---
58
59
 
@@ -65,8 +66,9 @@ docs/
65
66
  β”‚ β”œβ”€β”€ custom.md # ν”„λ‘œμ νŠΈλ³„ μ»€μŠ€ν…€ κ·œμΉ™
66
67
  β”‚ └── constitution.md # ν”„λ‘œμ νŠΈ 원칙
67
68
  β”‚
68
- β”‚ # μ—”μ§„ 쒅속 κ°€μ΄λ“œλŠ” CLI λ‚΄μž₯(ν”„λ‘œμ νŠΈ docs 비동기화)μž…λ‹ˆλ‹€.
69
- β”‚ # - agents.md / skills/* / git-workflow / issue-template / pr-template
69
+ β”‚ # μ—”μ§„ 쒅속 κ°€μ΄λ“œλŠ” ν”„λ‘œμ νŠΈ docs에 λ™κΈ°ν™”λ˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€.
70
+ β”‚ # - 쑰회: npx lee-spec-kit docs list --json
71
+ β”‚ # - μ˜ˆμ‹œ: npx lee-spec-kit docs get git-workflow --json
70
72
  β”œβ”€β”€ prd/ # μ œν’ˆ μš”κ΅¬μ‚¬ν•­
71
73
  β”œβ”€β”€ designs/ # λ””μžμΈ μ°Έκ³  자료
72
74
  β”œβ”€β”€ ideas/ # 아이디어/To-do (Feature 승격 μ „)
@@ -96,14 +98,14 @@ docs/
96
98
 
97
99
  ## μš”μ²­ μœ ν˜•λ³„ ν”„λ‘œμ„ΈμŠ€
98
100
 
99
- > πŸ“– 각 ν”„λ‘œμ„ΈμŠ€μ˜ 상세 κ°€μ΄λ“œλŠ” CLI λ‚΄μž₯ skill κ°€μ΄λ“œλ₯Ό μ°Έμ‘°ν•˜μ„Έμš”.
101
+ > πŸ“– 각 ν”„λ‘œμ„ΈμŠ€μ˜ 상세 κ°€μ΄λ“œλŠ” `docs get` λͺ…λ ΉμœΌλ‘œ λ¨Όμ € μ‘°νšŒν•˜μ„Έμš”.
100
102
 
101
103
  | ν”„λ‘œμ„ΈμŠ€ | κ°€μ΄λ“œ |
102
104
  | ----------------- | --------------------------------- |
103
- | μƒˆ κΈ°λŠ₯ μΆ”κ°€ | CLI λ‚΄μž₯ `create-feature` κ°€μ΄λ“œ |
104
- | GitHub Issue 생성 | CLI λ‚΄μž₯ `create-issue` κ°€μ΄λ“œ |
105
- | Pull Request 생성 | CLI λ‚΄μž₯ `create-pr` κ°€μ΄λ“œ |
106
- | νƒœμŠ€ν¬ μ‹€ν–‰ | CLI λ‚΄μž₯ `execute-task` κ°€μ΄λ“œ |
105
+ | μƒˆ κΈ°λŠ₯ μΆ”κ°€ | `npx lee-spec-kit docs get create-feature --json` |
106
+ | GitHub Issue 생성 | `npx lee-spec-kit docs get create-issue --json` |
107
+ | Pull Request 생성 | `npx lee-spec-kit docs get create-pr --json` |
108
+ | νƒœμŠ€ν¬ μ‹€ν–‰ | `npx lee-spec-kit docs get execute-task --json` |
107
109
 
108
110
  ### μΆ”κ°€ κ·œμΉ™ (Fullstack)
109
111
 
@@ -6,7 +6,7 @@
6
6
 
7
7
  | 경둜 | λͺ©μ  | 핡심 λ¬Έμ„œ/μ—­ν•  |
8
8
  | ---------------- | ------------------ | ------------------------------------------------------------- |
9
- | `docs/agents/` | μ—μ΄μ „νŠΈ 운영 κ·œμΉ™ | `custom.md`, `constitution.md` (μ—”μ§„ 쒅속 κ°€μ΄λ“œλŠ” CLI λ‚΄μž₯) |
9
+ | `docs/agents/` | μ—μ΄μ „νŠΈ 운영 κ·œμΉ™ | `custom.md`, `constitution.md` (μ—”μ§„ 쒅속 κ°€μ΄λ“œλŠ” `npx lee-spec-kit docs get <doc-id> --json`으둜 쑰회) |
10
10
  | `docs/prd/` | μ œν’ˆ μš”κ΅¬μ‚¬ν•­ | ν”„λ‘œμ νŠΈλ³„ μž‘μ„± |
11
11
  | `docs/designs/` | λ””μžμΈ μ°Έκ³  자료 | `README.md` (링크/κ°€μ΄λ“œ/레퍼런슀) |
12
12
  | `docs/ideas/` | 아이디어/To-do | `README.md` (Idea β†’ Feature 승격 κ·œμΉ™) |
@@ -19,7 +19,7 @@
19
19
  `lee-spec-kit init`을 μ‹€ν–‰ν•˜λ©΄ λ¬Έμ„œ 루트(κΈ°λ³Έ: `docs/`)에 `.lee-spec-kit.json`이 μƒμ„±λ©λ‹ˆλ‹€.
20
20
 
21
21
  - `lee-spec-kit feature`, `status`, `update`μ—μ„œ λ¬Έμ„œ μœ„μΉ˜/ν”„λ‘œμ νŠΈ νƒ€μž…/μ–Έμ–΄λ₯Ό κ°μ§€ν•˜λŠ” μš©λ„λ‘œ μ‚¬μš©λ©λ‹ˆλ‹€.
22
- - `docsRepo`, `pushDocs`, `docsRemote`λŠ” CLI λ‚΄μž₯ **Docs Push μ •μ±…**을 μœ„ν•œ λ©”νƒ€λ°μ΄ν„°μž…λ‹ˆλ‹€. (μžλ™ pushλŠ” ν•˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€)
22
+ - `docsRepo`, `pushDocs`, `docsRemote`λŠ” CLI 관리 **Docs Push μ •μ±…**을 μœ„ν•œ λ©”νƒ€λ°μ΄ν„°μž…λ‹ˆλ‹€. (μžλ™ pushλŠ” ν•˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€)
23
23
 
24
24
  ### ν•„λ“œ
25
25
 
@@ -40,9 +40,10 @@
40
40
 
41
41
  - **πŸ”΄ μ»€μŠ€ν…€ κ·œμΉ™ (μ΅œμš°μ„ )**: `/docs/agents/custom.md`
42
42
  - **ν”„λ‘œμ νŠΈ 원칙**: `/docs/agents/constitution.md`
43
- - **Git μ›Œν¬ν”Œλ‘œμš°**: CLI λ‚΄μž₯ μ •μ±… (`lee-spec-kit context`, `lee-spec-kit github`)
44
- - **이슈 μ΄ˆμ•ˆ μ •μ±…**: CLI λ‚΄μž₯ (`lee-spec-kit github issue --json`)
45
- - **PR μ΄ˆμ•ˆ μ •μ±…**: CLI λ‚΄μž₯ (`lee-spec-kit github pr --json`)
43
+ - **μ—μ΄μ „νŠΈ 루트 κ°€μ΄λ“œ**: `npx lee-spec-kit docs get agents --json`
44
+ - **Git μ›Œν¬ν”Œλ‘œμš°**: `npx lee-spec-kit docs get git-workflow --json`
45
+ - **이슈 절차/ν…œν”Œλ¦Ώ**: `npx lee-spec-kit docs get create-issue --json` β†’ `npx lee-spec-kit docs get issue-template --json`
46
+ - **PR 절차/ν…œν”Œλ¦Ώ**: `npx lee-spec-kit docs get create-pr --json` β†’ `npx lee-spec-kit docs get pr-template --json`
46
47
 
47
48
  ### PRD
48
49
 
@@ -51,7 +52,7 @@
51
52
  ### Feature (κΈ°λŠ₯별 λ¬Έμ„œ)
52
53
 
53
54
  - **κΈ°λŠ₯ λ¬Έμ„œ**: `/docs/features/{feature-id}/`
54
- - **ν…œν”Œλ¦Ώ (SSOT)**: CLI λ‚΄μž₯ feature-base ν…œν”Œλ¦Ώ
55
+ - **ν…œν”Œλ¦Ώ (SSOT)**: `npx lee-spec-kit feature <name>`둜 μƒμ„±λœ λ¬Έμ„œ ꡬ쑰
55
56
 
56
57
  ---
57
58
 
@@ -64,8 +65,9 @@ docs/
64
65
  β”‚ β”œβ”€β”€ custom.md # ν”„λ‘œμ νŠΈλ³„ μ»€μŠ€ν…€ κ·œμΉ™
65
66
  β”‚ └── constitution.md # ν”„λ‘œμ νŠΈ 원칙
66
67
  β”‚
67
- β”‚ # μ—”μ§„ 쒅속 κ°€μ΄λ“œλŠ” CLI λ‚΄μž₯(ν”„λ‘œμ νŠΈ docs 비동기화)μž…λ‹ˆλ‹€.
68
- β”‚ # - agents.md / skills/* / git-workflow / issue-template / pr-template
68
+ β”‚ # μ—”μ§„ 쒅속 κ°€μ΄λ“œλŠ” ν”„λ‘œμ νŠΈ docs에 λ™κΈ°ν™”λ˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€.
69
+ β”‚ # - 쑰회: npx lee-spec-kit docs list --json
70
+ β”‚ # - μ˜ˆμ‹œ: npx lee-spec-kit docs get git-workflow --json
69
71
  β”œβ”€β”€ prd/ # μ œν’ˆ μš”κ΅¬μ‚¬ν•­
70
72
  β”œβ”€β”€ designs/ # λ””μžμΈ μ°Έκ³  자료
71
73
  β”œβ”€β”€ ideas/ # 아이디어/To-do (Feature 승격 μ „)
@@ -87,14 +89,14 @@ docs/
87
89
 
88
90
  ## μš”μ²­ μœ ν˜•λ³„ ν”„λ‘œμ„ΈμŠ€
89
91
 
90
- > πŸ“– 각 ν”„λ‘œμ„ΈμŠ€μ˜ 상세 κ°€μ΄λ“œλŠ” CLI λ‚΄μž₯ skill κ°€μ΄λ“œλ₯Ό μ°Έμ‘°ν•˜μ„Έμš”.
92
+ > πŸ“– 각 ν”„λ‘œμ„ΈμŠ€μ˜ 상세 κ°€μ΄λ“œλŠ” `docs get` λͺ…λ ΉμœΌλ‘œ λ¨Όμ € μ‘°νšŒν•˜μ„Έμš”.
91
93
 
92
94
  | ν”„λ‘œμ„ΈμŠ€ | κ°€μ΄λ“œ |
93
95
  | ----------------- | --------------------------------- |
94
- | μƒˆ κΈ°λŠ₯ μΆ”κ°€ | CLI λ‚΄μž₯ `create-feature` κ°€μ΄λ“œ |
95
- | GitHub Issue 생성 | CLI λ‚΄μž₯ `create-issue` κ°€μ΄λ“œ |
96
- | Pull Request 생성 | CLI λ‚΄μž₯ `create-pr` κ°€μ΄λ“œ |
97
- | νƒœμŠ€ν¬ μ‹€ν–‰ | CLI λ‚΄μž₯ `execute-task` κ°€μ΄λ“œ |
96
+ | μƒˆ κΈ°λŠ₯ μΆ”κ°€ | `npx lee-spec-kit docs get create-feature --json` |
97
+ | GitHub Issue 생성 | `npx lee-spec-kit docs get create-issue --json` |
98
+ | Pull Request 생성 | `npx lee-spec-kit docs get create-pr --json` |
99
+ | νƒœμŠ€ν¬ μ‹€ν–‰ | `npx lee-spec-kit docs get execute-task --json` |
98
100
 
99
101
  ---
100
102