Individual skill
user-story-writer
撰寫結構良好、帶驗收標準和邊界情況的使用者故事。當被要求寫使用者故事、根據功能說明建任務、把 PRD 轉成故事,或寫驗收標準時使用。產出可以直接估算的標準格式故事,附清楚的驗收標準、邊界情況和完成定義。
skills-i18n/zh-TW/user-story-writer/SKILL.md
Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,537
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- product-management Repository topic
- productivity Repository topic
- skills Repository topic
- claude-skills Repository topic
- agent-skills Repository topic
- chatgpt Repository topic
- claude-code Repository topic
- cursor Repository topic
- gemini Repository topic
- prompt-engineering Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,755 bytes
Read excerpt
> [user-story-writer](../../../skills/user-story-writer/SKILL.md) 的繁體中文翻譯,英文版本為規範版本。
# 使用者故事撰寫
這個技能根據功能說明、PRD 的某一部分或口頭描述,產出可以直接使用的使用者故事。每個故事都遵循標準格式:清楚的誰 / 做什麼 / 為什麼,按 Given / When / Then(假如 / 當 / 那麼)格式寫的行為驗收標準、邊界情況和完成定義。產出可以直接貼上到 Jira、Linear 或你的規劃工具中。
## 所需輸入
如未提供,請向使用者詢問:
- **要拆成故事的功能或改動**:貼上說明、PRD 部分,或描述功能
- **涉及的使用者型別 / 角色**(例如管理員、終端使用者、訪客、API 呼叫方)
- **範圍**:寫一個故事,還是把一個史詩拆成完整的一組故事?
- **驗收標準格式偏好**:Given / When / Then、要點清單,還是兩者都要?
- **技術約束或說明**:工程團隊提出的、應當影響故事的任何事項