lee-spec-kit 0.6.1 → 0.6.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lee-spec-kit",
-  "version": "0.6.1",
+  "version": "0.6.3",
   "description": "Project documentation structure generator for AI-assisted development",
   "type": "module",
   "bin": {

package/templates/en/common/agents/git-workflow.md

@@ -70,14 +70,14 @@ main
 
 ## Automation Workflow
 
-> 📖 Refer to `skills/` folder for step-by-step guides.
-
-| Workflow       | Guide                      |
-| -------------- | -------------------------- |
-| Feature Start  | `skills/create-feature.md` |
-| Issue Creation | `skills/create-issue.md`   |
-| Task Execution | `skills/execute-task.md`   |
-| PR Creation    | `skills/create-pr.md`      |
+> 📖 Read each step guide first with `docs get`.
+
+| Workflow       | Guide                                              |
+| -------------- | -------------------------------------------------- |
+| Feature Start  | `npx lee-spec-kit docs get create-feature --json` |
+| Issue Creation | `npx lee-spec-kit docs get create-issue --json`   |
+| Task Execution | `npx lee-spec-kit docs get execute-task --json`   |
+| PR Creation    | `npx lee-spec-kit docs get create-pr --json`      |
 
 ### Branch Creation
 

package/templates/en/common/agents/pr-template.md

@@ -65,7 +65,7 @@ For file links within the repo in PR body, **always use current branch name**:
 ## Screenshots (Frontend / UI changes)
 
 <!-- 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. -->
-> If you follow the Release assets upload flow in `skills/create-pr.md`, you can include images in the PR body without committing files to your branch.
+> 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.
 
 {Screenshot markdown (e.g. ![](URL))}
 

package/templates/en/common/agents/skills/create-issue.md

@@ -13,9 +13,22 @@ Guide for creating GitHub Issues.
 
 ## Steps
 
-### 1. Prepare Issue Content
+### 1. Prepare Issue Draft
 
-> 📖 **Always refer to `issue-template.md`**
+> 📖 **Read procedure/template via `docs get` first, then generate a draft and treat it as the source of truth.**
+
+```bash
+# 1) Read procedure + template policy
+npx lee-spec-kit docs get create-issue --json
+npx lee-spec-kit docs get issue-template --json
+
+# 2) Generate draft body (no remote action)
+npx lee-spec-kit github issue F001 --json
+```
+
+Use `docs get issue-template --json` output as the section policy,
+and `github issue --json` output `body` as the first draft to review/share.
+If needed, use `bodyFile` as the filesystem source.
 
 | Item     | Format                                      |
 | -------- | ------------------------------------------- |
@@ -28,12 +41,14 @@ Guide for creating GitHub Issues.
 
 > 🚨 **User Approval Required**
 
-Before creating issue, share and wait for approval:
+Before creating issue, share and wait for explicit approval (OK):
 
 - Title
-- Body
+- Full body draft (from `body`)
 - Labels
 
+Also fill all `TODO` items in Goals/Completion Criteria before creating.
+
 ### 3. Create Issue
 
 ```bash
@@ -42,11 +57,14 @@ gh issue create \
   --body-file /tmp/issue-body.md \
   --assignee @me \
   --label enhancement
+
+# Or via lee-spec-kit helper (requires explicit confirmation)
+npx lee-spec-kit github issue F001 --create --confirm OK --labels enhancement
 ```
 
 ---
 
 ## Reference Documents
 
-- **Issue Template**: `issue-template.md`
-- **Link Format Rules**: `issue-template.md` > "Link Format" section
+- **Draft generator**: `npx lee-spec-kit github issue <feature-name>`
+- **Approval rule**: share title/body/labels first, then run `--create --confirm OK`

package/templates/en/common/agents/skills/create-pr.md

@@ -15,9 +15,22 @@ Guide for creating Pull Requests.
 
 ## Steps
 
-### 1. Prepare PR Content
+### 1. Prepare PR Draft
 
-> 📖 **Always refer to `pr-template.md`**
+> 📖 **Read procedure/template via `docs get` first, then generate a draft and treat it as the source of truth.**
+
+```bash
+# 1) Read procedure + template policy
+npx lee-spec-kit docs get create-pr --json
+npx lee-spec-kit docs get pr-template --json
+
+# 2) Generate draft body (no remote action)
+npx lee-spec-kit github pr F001 --json
+```
+
+Use `docs get pr-template --json` output as the section policy,
+and `github pr --json` output `body` as the first PR draft body.
+If needed, use `bodyFile` as the filesystem source.
 
 | Item     | Format                             |
 | -------- | ---------------------------------- |
@@ -34,7 +47,7 @@ Guide for creating Pull Requests.
 
 1. Run relevant test commands (e.g., `npm test`, `pnpm test`); if no tests exist, request them from the user
 2. Check results (PASS/FAIL)
-3. In the PR body "Tests" section, follow `pr-template.md` rules as-is. (add/check only what you actually ran)
+3. In the PR body "Tests" section, keep only what you actually ran in the generated draft body
 4. If you didn’t run any tests, request/confirm with the user before creating the PR
 
 ### 3. Prepare Screenshots / Diagrams (Include in PR Body)
@@ -106,7 +119,7 @@ echo \"![](https://github.com/${REPO}/releases/download/${TAG}/ui-1.png)\"
 
 #### Logic/structure changes (Backend PR)
 
-- Write a Mermaid **`sequenceDiagram`** in the PR body (follow the "Architecture Diagram" rules in `pr-template.md` as-is).
+- Write a Mermaid **`sequenceDiagram`** in the PR body and keep it aligned with the generated draft format.
 
 ### 4. Request User Approval
 
@@ -115,9 +128,11 @@ echo \"![](https://github.com/${REPO}/releases/download/${TAG}/ui-1.png)\"
 Before creating PR, share the following **in a code block** and wait for **explicit approval (OK)**:
 
 - Title
-- Full body (`pr-template.md` format)
+- Full body draft (from `body`)
 - Labels (at least 1; cannot be empty)
 
+Before approval/create, fill all `TODO` items in the generated draft.
+
 ### 5. Create PR
 
 ```bash
@@ -127,6 +142,9 @@ gh pr create \
   --label "{label1,label2}" \
   --assignee @me \
   --base main
+
+# Or via lee-spec-kit helper (requires explicit confirmation)
+npx lee-spec-kit github pr F001 --create --confirm OK --labels enhancement
 ```
 
 ---
@@ -168,5 +186,5 @@ Use **current branch name** for file links in PR body:
 
 ## Reference Documents
 
-- **PR Template**: `pr-template.md`
-- **Git Workflow**: `git-workflow.md`
+- **Draft generator**: `npx lee-spec-kit github pr <feature-name>`
+- **Approval rule**: share title/body/labels first, then run `--create --confirm OK`

package/templates/en/fullstack/README.md

@@ -6,7 +6,7 @@ This documentation is organized by feature to help agents quickly understand the
 
 | Path                | Purpose               | Key Documents                                                 |
 | ------------------- | --------------------- | ------------------------------------------------------------- |
-| `docs/agents/`      | Agent operating rules | `agents.md`, `constitution.md`, `git-workflow.md`             |
+| `docs/agents/`      | Agent operating rules | `custom.md`, `constitution.md` (engine-managed guides are fetched via `npx lee-spec-kit docs get <doc-id> --json`) |
 | `docs/prd/`         | Product requirements  | Project-specific                                              |
 | `docs/designs/`     | Design references     | `README.md` (links/guidelines/references)                     |
 | `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
 When you run `lee-spec-kit init`, it creates `.lee-spec-kit.json` in the docs root (default: `docs/`).
 
 - Used by `lee-spec-kit feature`, `status`, and `update` to detect docs location / project type / language.
-- `docsRepo`, `pushDocs`, `docsRemote` are metadata for the **Docs Push rules** in `/docs/agents/git-workflow.md` (the CLI does not auto-push).
+- `docsRepo`, `pushDocs`, `docsRemote` are metadata for the CLI-managed **Docs Push policy** (the CLI does not auto-push).
 
 ### Fields
 

package/templates/en/fullstack/agents/agents.md

@@ -40,9 +40,10 @@ Operating rules for AI code assistants to perform consistent code generation and
 
 - **🔴 Custom Rules (Highest Priority)**: `/docs/agents/custom.md`
 - **Project Principles**: `/docs/agents/constitution.md`
-- **Git Workflow**: `/docs/agents/git-workflow.md`
-- **Issue Template**: `/docs/agents/issue-template.md`
-- **PR Template**: `/docs/agents/pr-template.md`
+- **Agent Root Guide**: `npx lee-spec-kit docs get agents --json`
+- **Git Workflow**: `npx lee-spec-kit docs get git-workflow --json`
+- **Issue Procedure/Template**: `npx lee-spec-kit docs get create-issue --json` → `npx lee-spec-kit docs get issue-template --json`
+- **PR Procedure/Template**: `npx lee-spec-kit docs get create-pr --json` → `npx lee-spec-kit docs get pr-template --json`
 
 ### PRD
 
@@ -52,7 +53,7 @@ Operating rules for AI code assistants to perform consistent code generation and
 
 - **BE Features**: `/docs/features/be/{feature-id}/`
 - **FE Features**: `/docs/features/fe/{feature-id}/`
-- **Template (SSOT)**: `/docs/features/feature-base/`
+- **Template (SSOT)**: docs generated via `npx lee-spec-kit feature <name>`
 
 ---
 
@@ -62,16 +63,12 @@ Operating rules for AI code assistants to perform consistent code generation and
 docs/
 ├── README.md           # Documentation guide
 ├── agents/             # Agent operating rules
-│   ├── agents.md       # Main rules (this file)
-│   ├── constitution.md # Project principles
-│   ├── git-workflow.md # Git automation
-│   ├── issue-template.md
-│   ├── pr-template.md
-│   └── skills/         # Step-by-step guides
-│       ├── create-feature.md
-│       ├── create-issue.md
-│       ├── create-pr.md
-│       └── execute-task.md
+│   ├── custom.md       # Project-specific custom rules
+│   └── constitution.md # Project principles
+│
+│   # Engine-managed policy guides are not synced into project docs.
+│   # - list: npx lee-spec-kit docs list --json
+│   # - example: npx lee-spec-kit docs get git-workflow --json
 ├── prd/                # Product requirements
 ├── designs/            # Design references
 ├── ideas/              # Pre-feature ideas / to-dos
@@ -85,14 +82,14 @@ docs/
 
 ## Request Type Processes
 
-> 📖 Refer to `skills/` folder for detailed process guides.
+> 📖 Read each process guide first with `docs get`.
 
-| Process        | Guide                      |
-| -------------- | -------------------------- |
-| New Feature    | `skills/create-feature.md` |
-| GitHub Issue   | `skills/create-issue.md`   |
-| Pull Request   | `skills/create-pr.md`      |
-| Task Execution | `skills/execute-task.md`   |
+| Process        | Guide                                 |
+| -------------- | ------------------------------------- |
+| New Feature    | `npx lee-spec-kit docs get create-feature --json` |
+| GitHub Issue   | `npx lee-spec-kit docs get create-issue --json`   |
+| Pull Request   | `npx lee-spec-kit docs get create-pr --json`      |
+| Task Execution | `npx lee-spec-kit docs get execute-task --json`   |
 
 ### Additional Rules (Fullstack)
 

package/templates/en/fullstack/features/feature-base/plan.md

@@ -8,7 +8,7 @@
 
 - **Feature ID**: F{number}
 - **Target Repo**: {{projectName}}-{be|fe}
-- **Created**: YYYY-MM-DD
+- **Created**: {YYYY-MM-DD}
 - **Status**: Review | Approved
 
 ---

package/templates/en/fullstack/features/feature-base/spec.md

@@ -10,7 +10,7 @@
 - **Feature Name**: {feature-name}
 - **Target Repo**: {{projectName}}-{be|fe}
 - **Issue Number**: #{issue-number}
-- **Created**: YYYY-MM-DD
+- **Created**: {YYYY-MM-DD}
 - **Status**: Review | Approved
 
 ---

package/templates/en/single/README.md

@@ -6,7 +6,7 @@ This documentation is organized by feature to help agents quickly understand the
 
 | Path             | Purpose               | Key Documents                                                 |
 | ---------------- | --------------------- | ------------------------------------------------------------- |
-| `docs/agents/`   | Agent operating rules | `agents.md`, `constitution.md`, `git-workflow.md`             |
+| `docs/agents/`   | Agent operating rules | `custom.md`, `constitution.md` (engine-managed guides are fetched via `npx lee-spec-kit docs get <doc-id> --json`) |
 | `docs/prd/`      | Product requirements  | Project-specific                                              |
 | `docs/designs/`  | Design references     | `README.md` (links/guidelines/references)                     |
 | `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
 When you run `lee-spec-kit init`, it creates `.lee-spec-kit.json` in the docs root (default: `docs/`).
 
 - Used by `lee-spec-kit feature`, `status`, and `update` to detect docs location / project type / language.
-- `docsRepo`, `pushDocs`, `docsRemote` are metadata for the **Docs Push rules** in `/docs/agents/git-workflow.md` (the CLI does not auto-push).
+- `docsRepo`, `pushDocs`, `docsRemote` are metadata for the CLI-managed **Docs Push policy** (the CLI does not auto-push).
 
 ### Fields
 

package/templates/en/single/agents/agents.md

@@ -40,14 +40,15 @@ Operating rules for AI code assistants to perform consistent code generation and
 
 - **🔴 Custom Rules (Highest Priority)**: `/docs/agents/custom.md`
 - **Project Principles**: `/docs/agents/constitution.md`
-- **Git Workflow**: `/docs/agents/git-workflow.md`
-- **Issue Template**: `/docs/agents/issue-template.md`
-- **PR Template**: `/docs/agents/pr-template.md`
+- **Agent Root Guide**: `npx lee-spec-kit docs get agents --json`
+- **Git Workflow**: `npx lee-spec-kit docs get git-workflow --json`
+- **Issue Procedure/Template**: `npx lee-spec-kit docs get create-issue --json` → `npx lee-spec-kit docs get issue-template --json`
+- **PR Procedure/Template**: `npx lee-spec-kit docs get create-pr --json` → `npx lee-spec-kit docs get pr-template --json`
 
 ### Features
 
 - **Feature Docs**: `/docs/features/{feature-id}/`
-- **Template (SSOT)**: `/docs/features/feature-base/`
+- **Template (SSOT)**: docs generated via `npx lee-spec-kit feature <name>`
 
 ---
 
@@ -57,21 +58,16 @@ Operating rules for AI code assistants to perform consistent code generation and
 docs/
 ├── README.md           # Documentation guide
 ├── agents/             # Agent operating rules
-│   ├── agents.md       # Main rules (this file)
-│   ├── constitution.md # Project principles
-│   ├── git-workflow.md # Git automation
-│   ├── issue-template.md
-│   ├── pr-template.md
-│   └── skills/         # Step-by-step guides
-│       ├── create-feature.md
-│       ├── create-issue.md
-│       ├── create-pr.md
-│       └── execute-task.md
+│   ├── custom.md       # Project-specific custom rules
+│   └── constitution.md # Project principles
+│
+│   # Engine-managed policy guides are not synced into project docs.
+│   # - list: npx lee-spec-kit docs list --json
+│   # - example: npx lee-spec-kit docs get git-workflow --json
 ├── prd/                # Product requirements
 ├── designs/            # Design references
 ├── ideas/              # Pre-feature ideas / to-dos
 ├── features/           # Feature documentation
-│   ├── feature-base/   # Template
 │   └── F00X-{name}/
 └── scripts/            # Utilities
 ```
@@ -80,14 +76,14 @@ docs/
 
 ## Request Type Processes
 
-> 📖 Refer to `skills/` folder for detailed process guides.
+> 📖 Read each process guide first with `docs get`.
 
-| Process        | Guide                      |
-| -------------- | -------------------------- |
-| New Feature    | `skills/create-feature.md` |
-| GitHub Issue   | `skills/create-issue.md`   |
-| Pull Request   | `skills/create-pr.md`      |
-| Task Execution | `skills/execute-task.md`   |
+| Process        | Guide                                 |
+| -------------- | ------------------------------------- |
+| New Feature    | `npx lee-spec-kit docs get create-feature --json` |
+| GitHub Issue   | `npx lee-spec-kit docs get create-issue --json`   |
+| Pull Request   | `npx lee-spec-kit docs get create-pr --json`      |
+| Task Execution | `npx lee-spec-kit docs get execute-task --json`   |
 
 ---
 

package/templates/en/single/features/feature-base/plan.md

@@ -8,7 +8,7 @@
 
 - **Feature ID**: F{number}
 - **Target Repo**: {{projectName}}
-- **Created**: YYYY-MM-DD
+- **Created**: {YYYY-MM-DD}
 - **Status**: Review | Approved
 
 ---

package/templates/en/single/features/feature-base/spec.md

@@ -10,7 +10,7 @@
 - **Feature Name**: {feature-name}
 - **Target Repo**: {{projectName}}
 - **Issue Number**: #{issue-number}
-- **Created**: YYYY-MM-DD
+- **Created**: {YYYY-MM-DD}
 - **Status**: Review | Approved
 
 ---

package/templates/ko/common/agents/git-workflow.md

@@ -70,14 +70,14 @@ main
 
 ## 자동화 워크플로우
 
-> 📖 단계별 상세 가이드는 `skills/` 폴더를 참조하세요.
-
-| 워크플로우   | 가이드                     |
-| ------------ | -------------------------- |
-| Feature 시작 | `skills/create-feature.md` |
-| Issue 생성   | `skills/create-issue.md`   |
-| 태스크 실행  | `skills/execute-task.md`   |
-| PR 생성      | `skills/create-pr.md`      |
+> 📖 단계별 상세 가이드는 `docs get` 명령으로 먼저 확인하세요.
+
+| 워크플로우   | 가이드                                             |
+| ------------ | -------------------------------------------------- |
+| Feature 시작 | `npx lee-spec-kit docs get create-feature --json` |
+| Issue 생성   | `npx lee-spec-kit docs get create-issue --json`   |
+| 태스크 실행  | `npx lee-spec-kit docs get execute-task --json`   |
+| PR 생성      | `npx lee-spec-kit docs get create-pr --json`      |
 
 ### 브랜치 생성
 

package/templates/ko/common/agents/pr-template.md

@@ -63,7 +63,7 @@ PR 본문에서 레포 내 파일 링크는 **반드시 현재 브랜치명을
 ## 스크린샷 (프론트엔드 / UI 변경 시)
 
 <!-- UI 변경이 아니거나, 스크린샷을 업로드하지 않았다면(예: `.lee-spec-kit.json`의 `pr.screenshots.upload: false`) 이 섹션은 제거하세요. -->
-> `skills/create-pr.md`의 Release assets 업로드 절차를 사용하면 브랜치에 파일을 커밋하지 않고도 이미지를 본문에 포함할 수 있습니다.
+> `npx lee-spec-kit docs get create-pr --json`의 Release assets 업로드 절차를 사용하면 브랜치에 파일을 커밋하지 않고도 이미지를 본문에 포함할 수 있습니다.
 
 {스크린샷 마크다운 (예: ![](URL))}
 

package/templates/ko/common/agents/skills/create-issue.md

@@ -13,9 +13,22 @@ GitHub Issue를 생성할 때 따르는 가이드입니다.
 
 ## 단계
 
-### 1. 이슈 내용 작성
+### 1. 이슈 초안 작성
 
-> 📖 **`issue-template.md`를 반드시 참조하세요.**
+> 📖 **먼저 `docs get`으로 절차/템플릿을 읽고, 초안을 생성해 기준으로 사용하세요.**
+
+```bash
+# 1) 절차/템플릿 정책 확인
+npx lee-spec-kit docs get create-issue --json
+npx lee-spec-kit docs get issue-template --json
+
+# 2) 초안 본문 생성 (원격 작업 아님)
+npx lee-spec-kit github issue F001 --json
+```
+
+`docs get issue-template --json` 출력은 섹션 정책으로 보고,
+`github issue --json`의 `body`를 우선 본문 초안으로 사용하세요.
+필요하면 `bodyFile` 경로 파일을 함께 참고하세요.
 
 | 항목   | 형식                                     |
 | ------ | ---------------------------------------- |
@@ -28,12 +41,14 @@ GitHub Issue를 생성할 때 따르는 가이드입니다.
 
 > 🚨 **사용자 확인 필수**
 
-이슈 생성 전 다음 내용을 공유하고 승인 대기:
+이슈 생성 전 다음 내용을 공유하고 명시적 승인(OK) 대기:
 
 - 제목
-- 본문
+- 본문 전체 초안 (`body` 기준)
 - 라벨
 
+생성 전 목표/완료 기준 섹션의 `TODO` 항목을 모두 채우세요.
+
 ### 3. 이슈 생성
 
 ```bash
@@ -42,11 +57,14 @@ gh issue create \
   --body-file /tmp/issue-body.md \
   --assignee @me \
   --label enhancement
+
+# 또는 lee-spec-kit helper 사용 (명시적 승인 필요)
+npx lee-spec-kit github issue F001 --create --confirm OK --labels enhancement
 ```
 
 ---
 
 ## 참조 문서
 
-- **이슈 템플릿**: `issue-template.md`
-- **링크 형식 규칙**: `issue-template.md` > "링크 형식" 섹션
+- **초안 생성기**: `npx lee-spec-kit github issue <feature-name>`
+- **승인 규칙**: 제목/본문/라벨 공유 후 `--create --confirm OK` 실행

package/templates/ko/common/agents/skills/create-pr.md

@@ -15,9 +15,22 @@ Pull Request를 생성할 때 따르는 가이드입니다.
 
 ## 단계
 
-### 1. PR 내용 작성
+### 1. PR 초안 작성
 
-> 📖 **`pr-template.md`를 반드시 참조하세요.**
+> 📖 **먼저 `docs get`으로 절차/템플릿을 읽고, 초안을 생성해 기준으로 사용하세요.**
+
+```bash
+# 1) 절차/템플릿 정책 확인
+npx lee-spec-kit docs get create-pr --json
+npx lee-spec-kit docs get pr-template --json
+
+# 2) 초안 본문 생성 (원격 작업 아님)
+npx lee-spec-kit github pr F001 --json
+```
+
+`docs get pr-template --json` 출력은 섹션 정책으로 보고,
+`github pr --json`의 `body`를 우선 PR 초안 본문으로 사용하세요.
+필요하면 `bodyFile` 경로 파일을 함께 참고하세요.
 
 | 항목   | 형식                               |
 | ------ | ---------------------------------- |
@@ -34,7 +47,7 @@ Pull Request를 생성할 때 따르는 가이드입니다.
 
 1. 작업과 관련된 테스트 명령어 실행 (예: `npm test`, `pnpm test`), 테스트가 없는 경우 사용자에게 요청
 2. 결과 확인 (PASS/FAIL)
-3. PR 본문 "테스트" 섹션은 `pr-template.md`의 규칙을 그대로 따릅니다. (실행한 테스트만 추가/체크)
+3. PR 본문 "테스트" 섹션은 생성된 초안 기준으로, 실제 실행한 테스트만 반영합니다.
 4. 테스트를 실행하지 않았다면, PR 생성 전에 사용자에게 요청/확인합니다.
 
 ### 3. 스크린샷/다이어그램 작성 (PR 본문에 포함)
@@ -106,7 +119,7 @@ echo \"![](https://github.com/${REPO}/releases/download/${TAG}/ui-1.png)\"
 
 #### 로직/구조 변경 (백엔드 PR)
 
-- PR 본문에 Mermaid **`sequenceDiagram`**을 작성합니다. (`pr-template.md`의 "아키텍처 다이어그램" 섹션 규칙을 그대로 따르세요)
+- PR 본문에 Mermaid **`sequenceDiagram`**을 작성하고, 생성된 초안 형식과 일치하게 유지합니다.
 
 ### 4. 사용자 확인 요청
 
@@ -115,9 +128,11 @@ echo \"![](https://github.com/${REPO}/releases/download/${TAG}/ui-1.png)\"
 PR 생성 전 다음 내용을 **코드블록으로** 사용자에게 공유하고 **명시적 승인(OK)** 대기:
 
 - 제목
-- 본문 전체 (`pr-template.md` 형식)
+- 본문 전체 초안 (`body` 기준)
 - 라벨(최소 1개, 비워둘 수 없음)
 
+승인/생성 전에 생성된 초안의 `TODO` 항목을 모두 채우세요.
+
 ### 5. PR 생성
 
 ```bash
@@ -127,6 +142,9 @@ gh pr create \
   --label "{라벨1,라벨2}" \
   --assignee @me \
   --base main
+
+# 또는 lee-spec-kit helper 사용 (명시적 승인 필요)
+npx lee-spec-kit github pr F001 --create --confirm OK --labels enhancement
 ```
 
 ---
@@ -168,5 +186,5 @@ PR 본문의 파일 링크는 **현재 브랜치명**을 사용:
 
 ## 참조 문서
 
-- **PR 템플릿**: `pr-template.md`
-- **Git 워크플로우**: `git-workflow.md`
+- **초안 생성기**: `npx lee-spec-kit github pr <feature-name>`
+- **승인 규칙**: 제목/본문/라벨 공유 후 `--create --confirm OK` 실행

package/templates/ko/fullstack/README.md

@@ -6,7 +6,7 @@
 
 | 경로                | 목적                 | 핵심 문서/역할                                                |
 | ------------------- | -------------------- | ------------------------------------------------------------- |
-| `docs/agents/`      | 에이전트 운영 규칙   | `agents.md`, `constitution.md`, `git-workflow.md`             |
+| `docs/agents/`      | 에이전트 운영 규칙   | `custom.md`, `constitution.md` (엔진 종속 가이드는 `npx lee-spec-kit docs get <doc-id> --json`으로 조회) |
 | `docs/prd/`         | 제품 요구사항        | 프로젝트별 작성                                               |
 | `docs/designs/`     | 디자인 참고 자료     | `README.md` (링크/가이드/레퍼런스)                            |
 | `docs/ideas/`       | 아이디어/To-do        | `README.md` (Idea → Feature 승격 규칙)                        |
@@ -20,7 +20,7 @@
 `lee-spec-kit init`을 실행하면 문서 루트(기본: `docs/`)에 `.lee-spec-kit.json`이 생성됩니다.
 
 - `lee-spec-kit feature`, `status`, `update`에서 문서 위치/프로젝트 타입/언어를 감지하는 용도로 사용됩니다.
-- `docsRepo`, `pushDocs`, `docsRemote`는 `/docs/agents/git-workflow.md`의 **Docs Push 규칙**을 위한 메타데이터입니다. (자동 push는 하지 않습니다)
+- `docsRepo`, `pushDocs`, `docsRemote`는 CLI 관리 **Docs Push 정책**을 위한 메타데이터입니다. (자동 push는 하지 않습니다)
 
 ### 필드
 

package/templates/ko/fullstack/agents/agents.md

@@ -40,9 +40,10 @@
 
 - **🔴 커스텀 규칙 (최우선)**: `/docs/agents/custom.md`
 - **프로젝트 원칙**: `/docs/agents/constitution.md`
-- **Git 워크플로우**: `/docs/agents/git-workflow.md`
-- **이슈 템플릿**: `/docs/agents/issue-template.md`
-- **PR 템플릿**: `/docs/agents/pr-template.md`
+- **에이전트 루트 가이드**: `npx lee-spec-kit docs get agents --json`
+- **Git 워크플로우**: `npx lee-spec-kit docs get git-workflow --json`
+- **이슈 절차/템플릿**: `npx lee-spec-kit docs get create-issue --json` → `npx lee-spec-kit docs get issue-template --json`
+- **PR 절차/템플릿**: `npx lee-spec-kit docs get create-pr --json` → `npx lee-spec-kit docs get pr-template --json`
 
 ### PRD
 
@@ -52,7 +53,7 @@
 
 - **BE 기능**: `/docs/features/be/{feature-id}/`
 - **FE 기능**: `/docs/features/fe/{feature-id}/`
-- **템플릿 (SSOT)**: `/docs/features/feature-base/` (spec, plan, tasks, decisions)
+- **템플릿 (SSOT)**: `npx lee-spec-kit feature <name>`로 생성된 문서 구조 (spec, plan, tasks, decisions)
 
 ---
 
@@ -62,16 +63,12 @@
 docs/
 ├── README.md           # 문서 안내
 ├── agents/             # 에이전트 운영 규칙
-│   ├── agents.md       # 메인 규칙 (이 파일)
-│   ├── constitution.md # 프로젝트 원칙
-│   ├── git-workflow.md # Git 자동화
-│   ├── issue-template.md
-│   ├── pr-template.md
-│   └── skills/         # 단계별 가이드
-│       ├── create-feature.md
-│       ├── create-issue.md
-│       ├── create-pr.md
-│       └── execute-task.md
+│   ├── custom.md       # 프로젝트별 커스텀 규칙
+│   └── constitution.md # 프로젝트 원칙
+│
+│   # 엔진 종속 가이드는 프로젝트 docs에 동기화되지 않습니다.
+│   # - 조회: npx lee-spec-kit docs list --json
+│   # - 예시: npx lee-spec-kit docs get git-workflow --json
 ├── prd/                # 제품 요구사항
 ├── designs/            # 디자인 참고 자료
 ├── ideas/              # 아이디어/To-do (Feature 승격 전)
@@ -101,14 +98,14 @@ docs/
 
 ## 요청 유형별 프로세스
 
-> 📖 각 프로세스의 상세 가이드는 `skills/` 폴더를 참조하세요.
+> 📖 각 프로세스의 상세 가이드는 `docs get` 명령으로 먼저 조회하세요.
 
-| 프로세스          | 가이드                     |
-| ----------------- | -------------------------- |
-| 새 기능 추가      | `skills/create-feature.md` |
-| GitHub Issue 생성 | `skills/create-issue.md`   |
-| Pull Request 생성 | `skills/create-pr.md`      |
-| 태스크 실행       | `skills/execute-task.md`   |
+| 프로세스          | 가이드                            |
+| ----------------- | --------------------------------- |
+| 새 기능 추가      | `npx lee-spec-kit docs get create-feature --json` |
+| GitHub Issue 생성 | `npx lee-spec-kit docs get create-issue --json`   |
+| Pull Request 생성 | `npx lee-spec-kit docs get create-pr --json`      |
+| 태스크 실행       | `npx lee-spec-kit docs get execute-task --json`   |
 
 ### 추가 규칙 (Fullstack)