lee-spec-kit 0.1.0

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

@@ -0,0 +1,88 @@
+# Agents Guide
+
+Operating rules for AI code assistants to perform consistent code generation and refactoring.
+
+---
+
+## Reference Documents
+
+### Core Documents
+
+- **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`
+
+### PRD
+
+- **Product Requirements**: `/docs/prd/`
+
+### Features
+
+- **BE Features**: `/docs/features/be/{feature-id}/`
+- **FE Features**: `/docs/features/fe/{feature-id}/`
+- **Template (SSOT)**: `/docs/features/feature-base/`
+
+---
+
+## 📁 Standard docs Structure
+
+```
+docs/
+├── README.md           # Documentation guide
+├── agents/             # Agent operating rules
+│   ├── agents.md
+│   ├── constitution.md
+│   ├── git-workflow.md
+│   ├── issue-template.md
+│   └── pr-template.md
+├── prd/                # Product requirements
+├── features/           # Feature documentation
+│   ├── be/             # Backend Features
+│   └── fe/             # Frontend Features
+└── scripts/            # Utilities
+```
+
+---
+
+## Request Type Processes
+
+### 1. New Feature Request
+
+1. Identify target repo (BE or FE)
+2. Create feature folder: `lee-spec-kit feature <name>`
+3. Write `spec.md` - what and why (no tech stack)
+4. Request spec review from user
+5. Create GitHub Issue
+
+### 2. Spec to Plan
+
+1. Verify spec is clear
+2. Write `plan.md` - tech stack, architecture, file structure
+3. **Record key decisions in `decisions.md`** (required)
+4. Decompose into tasks after user approval
+
+### 3. Task Execution
+
+1. Write tasks in `tasks.md`
+2. Execute after user approval
+3. Transition status: `[TODO]` → `[DOING]` → `[DONE]`
+4. Commit immediately after task completion
+
+---
+
+## 📋 ADR (Architecture Decision Records)
+
+> `decisions.md` is a **required** document for recording technical decisions.
+
+### Format
+
+```markdown
+## D{number}: {Decision Title} ({YYYY-MM-DD})
+
+- **Context**: Problem situation or background
+- **Options**: Alternatives considered
+- **Decision**: Final choice
+- **Rationale**: Reason for choice
+- **Consequences**: Results and impact (optional)
+```

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

@@ -0,0 +1,75 @@
+# {{projectName}} Constitution
+
+Core principles and technical decision guidelines for the project.
+All development decisions should be based on this document.
+
+---
+
+## 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/git-workflow.md

@@ -0,0 +1,112 @@
+# 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 |
+
+---
+
+## Commit Convention
+
+### 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}
+```
+
+### 2. Auto Commit on Task Completion
+
+```bash
+git add .
+git commit -m "{type}(#{issue}): {task-description}"
+```
+
+### 3. Create PR on Feature Completion
+
+```bash
+git push origin feat/{issue-number}-{feature-name}
+gh pr create --title "feat(#{issue}): {feature-title}" \
+  --body "Closes #{issue}" \
+  --base main
+```
+
+### 4. Merge
+
+```bash
+git checkout main
+git pull
+gh pr merge --squash --delete-branch
+git pull
+```
+
+---
+
+## 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/en/fullstack/agents/issue-template.md

@@ -0,0 +1,58 @@
+# 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)`
+
+---
+
+## 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 |

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

@@ -0,0 +1,57 @@
+# 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`
+
+---
+
+## 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 |

package/templates/en/fullstack/features/README.md

@@ -0,0 +1,76 @@
+# Features Guide
+
+Folder for managing feature specs, plans, and tasks.
+**FE/BE repos are separated, so Features are also managed separately.**
+
+---
+
+## Folder Structure
+
+```
+features/
+├── README.md           # This file
+├── feature-base/       # Shared template (edit in one place)
+│   ├── spec.md
+│   ├── plan.md
+│   ├── tasks.md
+│   └── decisions.md
+├── be/                 # Backend Features
+│   └── F00X-{name}/
+└── fe/                 # Frontend Features
+    └── F00X-{name}/
+```
+
+---
+
+## Creating New Features
+
+### Using CLI (Recommended)
+
+```bash
+# Backend Feature
+lee-spec-kit feature --repo be user-auth
+
+# Frontend Feature
+lee-spec-kit feature --repo fe user-profile
+```
+
+> 💡 CLI copies templates from `feature-base/` and auto-assigns IDs.
+
+---
+
+## Feature ID Rules
+
+- `F{number}-{feature-name}` (e.g., F001-user-auth)
+- Minimum **3-digit padding** for numbers (001, 002, ...)
+- Expands to **4+ digits** beyond 999 (F1000, F1001, ...)
+- Feature names in kebab-case
+- **IDs are globally unique** across BE/FE (no duplicates)
+- **Feature = Issue**: Each Feature corresponds to one GitHub Issue
+
+---
+
+## Status Check
+
+Check feature progress with CLI:
+
+```bash
+lee-spec-kit status
+```
+
+Save to file:
+
+```bash
+lee-spec-kit status --write
+```
+
+---
+
+## File Roles
+
+| File           | Role                      | When to Write       |
+| -------------- | ------------------------- | ------------------- |
+| `spec.md`      | **What and Why**          | Feature definition  |
+| `plan.md`      | **How** (technical)       | After spec approval |
+| `tasks.md`     | Specific work items       | After plan approval |
+| `decisions.md` | Technical decisions (ADR) | During development  |

package/templates/en/fullstack/features/be/README.md

@@ -0,0 +1,5 @@
+# Backend Features
+
+Backend Features will be created in this folder.
+
+Use `lee-spec-kit feature --repo be <name>` to create a new Feature.

package/templates/en/fullstack/features/fe/README.md

@@ -0,0 +1,5 @@
+# Frontend Features
+
+Frontend Features will be created in this folder.
+
+Use `lee-spec-kit feature --repo fe <name>` to create a new Feature.

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

@@ -0,0 +1,15 @@
+# Decisions Log
+
+Record technical decisions and their rationale.
+
+> Format: `D{number}: {Decision Title} ({YYYY-MM-DD})`
+
+---
+
+## D001: {Decision Title} ({YYYY-MM-DD})
+
+- **Context**: Problem situation or background
+- **Options**: Alternatives considered
+- **Decision**: Final choice
+- **Rationale**: Reason for choice
+- **Consequences**: Results and impact (optional)

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

@@ -0,0 +1,49 @@
+# Implementation Plan: {기능명}
+
+> Write after spec is approved.
+
+---
+
+## Overview
+
+- **Feature ID**: F{번호}
+- **Target Repo**: {{projectName}}-{be|fe}
+- **Created**: YYYY-MM-DD
+- **Status**: Draft | Review | Approved
+
+---
+
+## Tech Stack
+
+| Category | Choice | Reason |
+| -------- | ------ | ------ |
+
+---
+
+## Architecture
+
+(Component structure, data flow)
+
+---
+
+## File Structure
+
+```
+src/
+├── ...
+```
+
+---
+
+## Test Strategy
+
+- **Unit Tests**:
+- **Integration Tests**:
+- **E2E Tests**:
+
+---
+
+## Related Documents
+
+- Spec: [spec.md](./spec.md)
+- Decisions: [decisions.md](./decisions.md)

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

@@ -0,0 +1,55 @@
+# Feature Spec: {기능명}
+
+> Tech stack is covered in plan.md.
+
+---
+
+## Overview
+
+- **Feature ID**: F{번호}
+- **Feature Name**: {기능명}
+- **Target Repo**: {{projectName}}-{be|fe}
+- **Issue Number**: #{이슈번호}
+- **Created**: YYYY-MM-DD
+- **Status**: Draft | Review | Approved
+
+---
+
+## Purpose
+
+(Why is this feature needed? What problem does it solve?)
+
+---
+
+## User Stories
+
+### US-1: {Story Title}
+
+**As a** {user type}
+**I want** {desired action}
+**So that** {reason/value}
+
+**Acceptance Criteria:**
+
+- [ ] (verification condition)
+
+---
+
+## Functional Requirements
+
+### FR-1: {Requirement Title}
+
+(Detailed description)
+
+---
+
+## Non-Functional Requirements
+
+- **Performance**:
+- **Security**:
+
+---
+
+## Related Documents
+
+- PRD: `../../prd/`

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

@@ -0,0 +1,33 @@
+# Tasks: {기능명}
+
+## Task Rules
+
+- **Status**: `[TODO]` → `[DOING]` → `[DONE]`
+- **Priority**: P0(urgent) > P1(high) > P2(medium) > P3(low)
+
+---
+
+## GitHub Issue
+
+- **Repo**: {{projectName}}-{be|fe}
+- **Issue**: #{이슈번호}
+- **Branch**: `feat/{이슈번호}-{기능명}`
+
+---
+
+## Task List
+
+### Phase 1: {Phase Name}
+
+- [TODO][P1] T-F{번호}-01 {Task Title}
+  - Acceptance:
+    - (verification condition)
+  - Checklist:
+    - [ ] (subtask)
+
+---
+
+## Completion Criteria
+
+- [ ] All tasks [DONE]
+- [ ] All tests passing

package/templates/en/fullstack/prd/README.md

@@ -0,0 +1,15 @@
+# PRD (Product Requirements Document)
+
+This folder contains product requirements documentation.
+
+## Writing Guide
+
+1. Define project overview and goals
+2. Write main features and user stories
+3. Include technical architecture overview
+
+## Example Files
+
+- `{project-name}-prd.md` - Main PRD document
+- `backend-overview.md` - Backend architecture (optional)
+- `frontend-overview.md` - Frontend architecture (optional)

package/templates/en/single/README.md

@@ -0,0 +1,11 @@
+# {{projectName}} Documentation Guide
+
+This documentation is organized by feature to help agents quickly understand the project.
+
+## Directory Structure
+
+| Path             | Purpose               | Key Documents                                                 |
+| ---------------- | --------------------- | ------------------------------------------------------------- |
+| `docs/agents/`   | Agent operating rules | `agents.md`, `constitution.md`, `git-workflow.md`             |
+| `docs/prd/`      | Product requirements  | Project-specific                                              |
+| `docs/features/` | Feature documentation | `{feature-id}/spec.md`, `plan.md`, `tasks.md`, `decisions.md` |