Individual skill
user-story-writer
撰写结构良好、带验收标准和边界情况的用户故事。当被要求写用户故事、根据功能说明建任务、把 PRD 转成故事,或写验收标准时使用。产出可以直接估算的标准格式故事,附清楚的验收标准、边界情况和完成定义。
skills-i18n/zh/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,539
- Repository last updated
- Nov 10, 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,632 bytes
Read excerpt
> [user-story-writer](../../../skills/user-story-writer/SKILL.md) 的简体中文翻译,英文版本为规范版本。
# 用户故事撰写
这个技能根据功能说明、PRD 的某一部分或口头描述,产出可以直接使用的用户故事。每个故事都遵循标准格式:清楚的谁 / 做什么 / 为什么,按 Given / When / Then(假如 / 当 / 那么)格式写的行为验收标准、边界情况和完成定义。产出可以直接粘贴到 Jira、Linear 或你的规划工具中。
## 所需输入
如未提供,请向用户询问:
- **要拆成故事的功能或改动**:粘贴说明、PRD 部分,或描述功能
- **涉及的用户类型 / 角色**(例如管理员、最终用户、访客、API 调用方)
- **范围**:写一个故事,还是把一个史诗拆成完整的一组故事?
- **验收标准格式偏好**:Given / When / Then、要点清单,还是两者都要?
- **技术约束或说明**:工程团队提出的、应当影响故事的任何事项