Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat(specify): generate spec in Korean#1341

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
young-hwang wants to merge7 commits intogithub:main
base:main
Choose a base branch
Loading
fromyoung-hwang:main
Open
Changes from1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
PrevPrevious commit
NextNext commit
Updated language requirement guidelines in templates/commands/specify.md
  • Loading branch information
@young-hwang
young-hwang committedDec 15, 2025
commit8a9ca9247f6880250fe5d64a1c49531b84a2da70
12 changes: 9 additions & 3 deletionstemplates/commands/specify.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -13,8 +13,6 @@ scripts:
ps: scripts/powershell/create-new-feature.ps1 -Json "{ARGS}"
---

**IMPORTANT: The entire specification document MUST be written entirely in Korean.**

## User Input

```text
Expand DownExpand Up@@ -201,13 +199,21 @@ Given that feature description, do this:

## General Guidelines

### Language Requirements

**ALL specification content MUST be written in Korean (한글)**
- Section headings should remain in English for template compatibility
- All descriptions, requirements, scenarios, and criteria must be in Korean
- Technical terms can be kept in English when appropriate (e.g., API, OAuth, JWT)

## Quick Guidelines

- Focus on **WHAT** users need and **WHY**.
- Avoid HOW to implement (no tech stack, APIs, code structure).
- Written for business stakeholders, not developers.
- DO NOT create any checklists that are embedded in the spec. That will be a separate command.

- **Write all content in Korean (한글)** - only section headings remain in English

### Section Requirements

- **Mandatory sections**: Must be completed for every feature
Expand Down

[8]ページ先頭

©2009-2025 Movatter.jp