Transform product ideas into INVEST-compliant user stories with automated acceptance criteria. Plan sprints with capacity metrics and prioritize backlog items based on business value and complexity.
下载技能 ZIP
在 Claude 中上传
前往 设置 → 功能 → 技能 → 上传技能
开启并开始使用
测试它
正在使用“agile-product-owner”。 Generate user stories for a payment integration feature
预期结果:
- USER STORY: PAY-001
- Title: Process Payment
- Priority: HIGH | Points: 8
- Story: As a customer, I want to enter my payment details so that I can complete purchases securely
- Acceptance Criteria:
- 1. Given user has cart items, When they enter valid payment, Then payment processes
- 2. Should validate card information before processing
- 3. Must show clear error when payment fails
- 4. Should complete within 5 seconds
正在使用“agile-product-owner”。 Plan a sprint with 30 points capacity
预期结果:
- SPRINT CAPACITY: 30 points
- Committed: 28 points (93.3%)
- Stories: 4 committed + 1 stretch goal
- COMMITTED:
- [H] PAY-001: Process Payment (8pts)
- [H] PAY-002: View Payment History (5pts)
- [M] PAY-003: Download Receipt (3pts)
- [M] PAY-004: Set Default Payment Method (5pts)
- STRETCH:
- [L] PAY-005: Payment Notifications (8pts)
安全审计
安全All 37 static findings are false positives. The scanner incorrectly flagged Python dictionary access (`.get()`), method definitions, list iterations, and YAML text as security threats. This is a pure Python user story generator with no cryptographic code, network access, or dangerous patterns. The SKILL.md code fences are documentation, not shell execution. This skill is safe to publish.
风险因素
🌐 网络访问 (1)
⚙️ 外部命令 (2)
质量评分
你能构建什么
Backlog Refinement
Break down large features into manageable user stories with clear acceptance criteria
Sprint Planning
Calculate sprint capacity and select stories that fit within team velocity
Story Estimation
Get consistent story point estimates based on complexity indicators
试试这些提示
Generate user stories for a {feature_name} feature targeting {persona} usersWrite acceptance criteria for a story about {feature_description}Plan a sprint with {capacity} story points from this backlog: {story_list}Estimate story points for: {feature_description} with these requirements: {requirements}最佳实践
- Break epics into stories with single, independent deliverables
- Use INVEST criteria to validate story quality before sprint planning
- Balance sprint capacity with 10-20 percent buffer for unexpected issues
避免
- Creating stories that depend on other stories without clear dependencies
- Writing vague stories without clear acceptance criteria
- Overcommitting to sprint capacity without accounting for technical debt
常见问题
What is the INVEST criteria?
How are story points calculated?
Can I customize persona templates?
Does this integrate with Jira?
What complexity words affect story points?
How do stretch goals work?
开发者详情
许可证
MIT
引用
main
文件结构