user-story-writing
Write effective user stories and acceptance criteria that communicate intent, value, and testable outcomes to delivery teams. Use when breaking work into backlog items, refining stories, or improving collaboration between product, design, and engineering.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- user-story-writing
- description
- Write effective user stories and acceptance criteria that communicate intent, value, and testable outcomes to delivery teams. Use when breaking work into backlog items, refining stories, or improving collaboration between product, design, and engineering.
03 SKILL.md 正文
User Story Writing
Overview
User stories are a lightweight way to express desired outcomes from a user’s perspective. They work best when paired with clear acceptance criteria and conversation.
When to Use
- Building and refining a product backlog
- Sprint or iteration planning inputs
- Aligning on what “done” means for a piece of value
Format Guidance
Story
As a [type of user], I want [goal] so that [benefit].
Acceptance Criteria
- Prefer Given / When / Then or clear checklist-style criteria
- Cover happy path and important edge cases
- Make criteria testable and unambiguous
Principles
- Focus on user value, not implementation detail
- Keep stories small enough to complete in a reasonable cycle
- Acceptance criteria define “done,” not the design solution
- Stories are prompts for conversation, not legal contracts
- Include non-functional needs when they matter (performance, accessibility, security)
Verification
- [ ] The story describes value for a real user
- [ ] Acceptance criteria are testable
- [ ] Scope is small enough to discuss and deliver incrementally
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.