lee-spec-kit 0.1.8 → 0.2.0

package/templates/ko/single/agents/agents.md

@@ -62,7 +62,12 @@ docs/
 │   ├── constitution.md
 │   ├── git-workflow.md
 │   ├── issue-template.md
-│   └── pr-template.md
+│   ├── pr-template.md
+│   └── skills/         # 프로세스별 가이드
+│       ├── create-feature.md
+│       ├── create-issue.md
+│       ├── create-pr.md
+│       └── execute-task.md
 ├── prd/                # 제품 요구사항
 ├── features/           # 기능별 문서
 │   ├── feature-base/   # 템플릿
@@ -83,27 +88,14 @@ docs/
 
 ## 요청 유형별 프로세스
 
-### 1. 새 기능 추가 요청
+> 📖 각 프로세스의 상세 가이드는 `skills/` 폴더를 참조하세요.
 
-1. 새 기능 폴더 생성: `npx lee-spec-kit feature <name>`
-2. `spec.md` 작성 - 무엇을, 왜 만드는지
-3. 사용자에게 스펙 초안 확인 요청
-4. GitHub Issue 생성
-
-### 2. 태스크 실행 및 관리
-
-1. `tasks.md`에 태스크 작성
-2. 사용자 승인 후 실행
-3. 상태 전환: `[TODO]` → `[DOING]` → `[DONE]`
-4. 태스크 완료 직후 커밋
-
-### 3. 태스크 외 요청 처리
-
-> 사용자가 **tasks.md에 없는 작업**을 요청하면:
-
-1. 해당 작업을 **tasks.md에 반영할지** 사용자에게 확인
-2. 승인 시: tasks.md에 추가 후 실행
-3. 거부 시: 임시 작업으로 진행 (커밋에는 포함)
+| 프로세스          | 가이드                     |
+| ----------------- | -------------------------- |
+| 새 기능 추가      | `skills/create-feature.md` |
+| GitHub Issue 생성 | `skills/create-issue.md`   |
+| Pull Request 생성 | `skills/create-pr.md`      |
+| 태스크 실행       | `skills/execute-task.md`   |
 
 ---
 

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

@@ -1,80 +0,0 @@
-# {{projectName}} Constitution
-
-Core principles and technical decision guidelines for the project.
-All development decisions should be based on this document.
-
-> **📌 Document Scope**
->
-> - **This document**: Tech stack, architecture principles, code quality, security principles
-> - **PRD**: Product requirements, business logic, user stories → `prd/*.md`
-
----
-
-## Project Mission
-
-> (Write your project mission here)
-
----
-
-## Tech Stack
-
-### Backend
-
-| Technology     | Version   | Reason   |
-| -------------- | --------- | -------- |
-| (e.g., NestJS) | (version) | (reason) |
-
-### Frontend
-
-| Technology    | Version   | Reason   |
-| ------------- | --------- | -------- |
-| (e.g., React) | (version) | (reason) |
-
-### Common
-
-| Technology        | Version | Reason             |
-| ----------------- | ------- | ------------------ |
-| TypeScript        | strict  | Type safety        |
-| ESLint + Prettier | -       | Code quality       |
-| pnpm              | -       | Package management |
-
----
-
-## Architecture Principles
-
-### 1. Feature-Centric Management
-
-- New features managed in `docs/features/F00X/` structure
-- Develop by **feature unit** with FE/BE separation
-- Workflow: spec → plan → tasks → decisions
-
-### 2. (Additional Principles)
-
-(Write project-specific architecture principles)
-
----
-
-## Code Quality Standards
-
-- TypeScript strict mode required
-- ESLint + Prettier required
-- Test coverage **80%+** for core business logic
-- Components follow **single responsibility principle**
-- Minimize code duplication
-
----
-
-## Security Principles
-
-- Manage secrets via environment variables (no repo commits)
-- **Minimal** user data collection
-- CORS configured for allowed origins only
-
----
-
-## Language/Code Rules
-
-- **AI Responses**: English
-- **Code/Filenames**: English
-- **Comments/Commits**: English
-- **Date/Time**: User's PC system time (e.g., `{{date}}`)

package/templates/en/fullstack/agents/issue-template.md

@@ -1,110 +0,0 @@
-# GitHub Issue Template Guide
-
-Template for AI agents to create GitHub Issues.
-
----
-
-## Issue Creation Rules
-
-### Title Format
-
-```text
-F{number}: {feature-name} ({short description})
-```
-
-Example: `F001: user-auth (User authentication feature)`
-
-### Link Format (Important!)
-
-In GitHub Issues, use different link formats **based on file location**:
-
-1. **Files within project repo**: Use full URL (clickable)
-   - **Merged documents/code**: Use `main` branch
-     ```markdown
-     [filename](https://github.com/{owner}/{repo}/blob/main/path/to/file)
-     ```
-   - **In-progress documents** (not merged yet): Use **Feature branch**
-     ```markdown
-     [filename](https://github.com/{owner}/{repo}/blob/{feat-branch}/path/to/file)
-     ```
-
-2. **External documents (with public URL)**: Use **absolute URL**
-
-   ```markdown
-   [react-i18next](https://react.i18next.com/)
-   ```
-
-3. **External/local documents** (no URL available): Use **relative path as text only**
-   ```text
-   ../docs/features/F001-feature-name/spec.md
-   ```
-
-> ⚠️ Local documents are not clickable on GitHub, so provide path text only.
-
-## Issue Body Template
-
-```markdown
-## Overview
-
-{Brief description of the feature}
-
-## Goals
-
-- {Goal 1}
-- {Goal 2}
-
-## Completion Criteria
-
-- [ ] {Criterion 1}
-- [ ] {Criterion 2}
-
-## Related Documents
-
-- Spec: `docs/features/{be|fe}/F{number}-{feature-name}/spec.md`
-
-## Labels
-
-- `enhancement` (New feature)
-- `bug` (Bug fix)
-- `documentation` (Documentation)
-```
-
----
-
-## Label Rules
-
-| Label           | Usage         |
-| --------------- | ------------- |
-| `enhancement`   | New feature   |
-| `bug`           | Bug fix       |
-| `documentation` | Documentation |
-| `backend`       | BE related    |
-| `frontend`      | FE related    |
-| `priority:high` | High priority |
-
-> ⚠️ If a label does not exist, create it first:
->
-> ```bash
-> gh label create "label-name" --description "description" --color "color-code"
-> ```
-
----
-
-## Assignee Rules
-
-- Default: Self-assign (`--assignee @me`)
-- When assigning others, **confirm with user** first
-- Examples:
-  ```bash
-  gh issue create --assignee @me ...
-  gh issue create --assignee username ...
-  ```
-
----
-
-## Body Input Rules (Shell Execution Prevention)
-
-- Issue body should use **`--body-file` by default**.
-- If the body contains backticks (`) or `$()`and is placed directly in`"..."`, it may be **interpreted by the shell**.
-- For multi-line bodies, use **single-quoted heredoc** like `cat <<'EOF'`,
-  and handle variables via **placeholder → sed substitution**.

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

@@ -1,96 +0,0 @@
-# GitHub PR Template Guide
-
-Template for AI agents to create Pull Requests.
-
----
-
-## PR Creation Rules
-
-### Title Format
-
-```text
-feat(#{issue-number}): {feature-name}
-```
-
-Example: `feat(#1): Implement user authentication`
-
-### Link Format (Important!)
-
-For file links within the repo in PR body, **always use current branch name**:
-
-```markdown
-[filename](https://github.com/{owner}/{repo}/blob/{branch-name}/docs/path/to/file.md)
-```
-
-> ⚠️ `main` branch links will return 404 until merged!
-> Always use the **current feature branch name** (e.g., `feat/5-feature-name`).
-
-## PR Body Template
-
-```markdown
-## Overview
-
-{Brief description of changes}
-
-## Changes
-
-- {Change 1}
-- {Change 2}
-- {Change 3}
-
-## Tests
-
-- [ ] Unit tests passed
-- [ ] Integration tests completed
-
-## Screenshots (for UI changes)
-
-{Attach if applicable}
-
-## Related Documents
-
-- Spec: `docs/features/{be|fe}/F{number}-{feature-name}/spec.md`
-- Tasks: `docs/features/{be|fe}/F{number}-{feature-name}/tasks.md`
-
-Closes #{issue-number}
-```
-
----
-
-## Merge Rules
-
-| Situation      | Merge Method     |
-| -------------- | ---------------- |
-| Normal Feature | Squash and Merge |
-| Urgent Hotfix  | Merge or Rebase  |
-| Documentation  | Squash and Merge |
-
----
-
-## Label Rules
-
-- Specify appropriate labels when creating PR (`--label`)
-- If a label does not exist, create it first:
-  ```bash
-  gh label create "label-name" --description "description" --color "color-code"
-  ```
-
----
-
-## Assignee Rules
-
-- Default: Self-assign (`--assignee @me`)
-- Use `--reviewer` option to specify reviewers
-- Examples:
-  ```bash
-  gh pr create --assignee @me --reviewer reviewer-username ...
-  ```
-
----
-
-## Body Input Rules (Shell Execution Prevention)
-
-- PR body should use **`--body-file` by default**.
-- If the body contains backticks (`) or `$()`and is placed directly in`"..."`, it may be **interpreted by the shell**.
-- For multi-line bodies, use **single-quoted heredoc** like `cat <<'EOF'`,
-  and handle variables via **placeholder → sed substitution**.

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

@@ -1,29 +0,0 @@
-# Custom Rules
-
-> ⚠️ This document contains **user-defined rules**.
-> It is NOT affected by `npx lee-spec-kit update`.
-> **Rules in this document take precedence over all other agent rules.**
-
----
-
-## Project-Specific Rules
-
-(Write your project-specific rules here)
-
----
-
-## Additional Language/Code Rules
-
-(Override default rules or add additional rules here)
-
----
-
-## Custom Workflows
-
-(Write project-specific workflows here)
-
----
-
-## Other
-
-(Write other rules here)

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

@@ -1,170 +0,0 @@
-# Git Workflow Guide
-
-Rules for AI agents to automate Git/GitHub operations.
-
----
-
-## Core Concepts
-
-| Concept          | GitHub Mapping | Description                     |
-| ---------------- | -------------- | ------------------------------- |
-| Feature          | GitHub Issue   | Feature-level work unit         |
-| Task             | Commit         | Individual implementation unit  |
-| Feature Complete | Pull Request   | Create PR on feature completion |
-
----
-
-## Branch Strategy
-
-```
-main
- └── feat/123-feature-name    # Branch based on Issue #123
-      ├── commit 1: feat(#123): implement feature
-      ├── commit 2: test(#123): add tests
-      └── commit 3: docs(#123): update docs
-```
-
-### Branch Naming
-
-```
-{type}/{issue-number}-{feature-name}
-```
-
-| Type       | Description   |
-| ---------- | ------------- |
-| `feat`     | New feature   |
-| `fix`      | Bug fix       |
-| `refactor` | Refactoring   |
-| `docs`     | Documentation |
-
-**Examples:**
-
-- `feat/123-user-auth`
-- `fix/456-login-error`
-
----
-
-## Commit Convention
-
-> 📖 Type and Description follow [Udacity Git Commit Message Style Guide](https://udacity.github.io/git-styleguide/).
-
-### Format
-
-```
-{type}(#{issue}): {description}
-```
-
-### Type List
-
-| Type       | Description   | Example                               |
-| ---------- | ------------- | ------------------------------------- |
-| `feat`     | New feature   | `feat(#123): implement user auth`     |
-| `fix`      | Bug fix       | `fix(#123): fix login error`          |
-| `refactor` | Refactoring   | `refactor(#123): separate auth logic` |
-| `test`     | Tests         | `test(#123): add auth unit tests`     |
-| `docs`     | Documentation | `docs(#123): clarify spec`            |
-| `style`    | Code style    | `style(#123): fix lint errors`        |
-| `chore`    | Other         | `chore(#123): update dependencies`    |
-
----
-
-## Automation Workflow
-
-### 1. Feature Start
-
-```bash
-# 1. Create GitHub Issue (Feature = Issue)
-# 2. Create branch
-git checkout -b feat/{issue-number}-{feature-name}
-```
-
-> When creating/modifying issues/PRs with `gh`, share the title/body/labels first and **wait for user confirmation (OK)** before proceeding.
-
-### 2. Document Commit (docs repo)
-
-> 📌 The docs folder is managed as a separate git, so a separate commit strategy is used.
-
-| #   | Commit Timing                                            | Included Documents              | Commit Message Example          |
-| --- | -------------------------------------------------------- | ------------------------------- | ------------------------------- |
-| 1   | **When planning is complete** (spec+plan+tasks approved) | spec.md, plan.md, tasks.md      | `docs(#123): spec, plan, tasks` |
-| 2   | **When Feature is complete** (all tasks done)            | tasks.md (status), decisions.md | `docs(#123): Feature complete`  |
-
-> ⚠️ **Do not commit when creating Feature folder.**
-
-### 3. Auto Commit on Task Completion
-
-When a task is completed:
-
-```bash
-git add .
-git commit -m "{type}(#{issue}): {task-description}"
-```
-
-> Before running `git commit`, share the commit message and file list first and **wait for user confirmation (OK)** before proceeding.
-
-### 4. Create PR on Feature Completion
-
-When all tasks are completed:
-
-```bash
-git push origin feat/{issue-number}-{feature-name}
-gh pr create --title "feat(#{issue}): {feature-title}" \
-  --body "Closes #{issue}" \
-  --base main
-```
-
-### 5. Merge
-
-When all reviews are resolved:
-
-```bash
-# Update main before merge
-git checkout main
-git pull
-
-# Squash and Merge
-gh pr merge --squash --delete-branch
-
-# Update main after merge
-git pull
-```
-
----
-
-## Agent Automation Rules
-
-### On Task Completion
-
-```
-1. Complete code changes
-2. Update tasks.md status [DOING] → [DONE] (docs)
-3. git add .
-4. git commit -m "{type}(#{issue}): {description}"
-5. Proceed to next task
-```
-
-### On Feature Completion
-
-```
-1. Verify all tasks [DONE]
-2. git push origin {branch}
-3. gh pr create
-4. Wait for review
-5. Address review comments
-6. gh pr merge --squash
-```
-
----
-
-## GitHub Setup Requirements
-
-### Required
-
-- [ ] GitHub CLI (`gh`) installed and authenticated
-- [ ] Branch protection rules (main)
-  - Require PR before merging
-
-### Recommended
-
-- [ ] Auto-delete head branches
-- [ ] Squash merging only

package/templates/ko/single/agents/constitution.md

@@ -1,80 +0,0 @@
-# {{projectName}} Constitution
-
-프로젝트의 핵심 원칙과 기술 결정 가이드라인입니다.
-모든 개발 결정은 이 문서를 기준으로 합니다.
-
-> **📌 문서 범위**
->
-> - **이 문서**: 기술 스택, 아키텍처 원칙, 코드 품질, 보안 원칙
-> - **PRD**: 제품 요구사항, 비즈니스 로직, 사용자 스토리 → `prd/*.md`
-
----
-
-## 프로젝트 미션
-
-> (프로젝트의 미션을 작성하세요)
-
----
-
-## 기술 스택
-
-### Backend
-
-| 기술         | 버전   | 이유        |
-| ------------ | ------ | ----------- |
-| (예: NestJS) | (버전) | (선택 이유) |
-
-### Frontend
-
-| 기술        | 버전   | 이유        |
-| ----------- | ------ | ----------- |
-| (예: React) | (버전) | (선택 이유) |
-
-### 공통
-
-| 기술              | 버전   | 이유        |
-| ----------------- | ------ | ----------- |
-| TypeScript        | strict | 타입 안전성 |
-| ESLint + Prettier | -      | 코드 품질   |
-| pnpm              | -      | 패키지 관리 |
-
----
-
-## 아키텍처 원칙
-
-### 1. Feature 중심 관리
-
-- 새 기능은 `docs/features/F00X/` 구조로 관리
-- FE/BE 분리하여 **기능 단위**로 개발
-- spec → plan → tasks → decisions 워크플로우
-
-### 2. (추가 원칙)
-
-(프로젝트별 아키텍처 원칙을 작성하세요)
-
----
-
-## 코드 품질 기준
-
-- TypeScript strict mode 필수
-- ESLint + Prettier 필수
-- 주요 비즈니스 로직 테스트 커버리지 **80%+**
-- 컴포넌트는 **단일 책임 원칙**
-- 중복 코드 최소화
-
----
-
-## 보안 원칙
-
-- 환경 변수로 시크릿 관리 (저장소 커밋 금지)
-- 사용자 데이터 **최소 수집**
-- CORS는 허용 오리진만 설정
-
----
-
-## 언어/코드 규칙
-
-- **답변**: 한국어
-- **코드/파일명**: 영어
-- **주석/커밋**: 한국어
-- **날짜/시간**: 사용자 PC 시스템 시간 기준 (예: `{{date}}`)

package/templates/ko/single/agents/custom.md

@@ -1,29 +0,0 @@
-# Custom Rules
-
-> ⚠️ 이 문서는 **사용자 정의 규칙**입니다.
-> `npx lee-spec-kit update`의 영향을 받지 않습니다.
-> **이 문서의 규칙은 다른 모든 agents 규칙보다 우선합니다.**
-
----
-
-## 프로젝트 특화 규칙
-
-(여기에 프로젝트만의 규칙을 작성하세요)
-
----
-
-## 추가 언어/코드 규칙
-
-(기본 규칙을 오버라이드하거나 추가 규칙을 작성하세요)
-
----
-
-## 커스텀 워크플로우
-
-(프로젝트만의 워크플로우가 있다면 작성하세요)
-
----
-
-## 기타
-
-(기타 규칙을 작성하세요)