القائمة
Guidelines for writing effective user stories with clear acceptance criteria. Use when creating issues from discovery findings.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/shwilliamson/automatasaurus --skill user-storiesيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | user-stories |
| description | Guidelines for writing effective user stories with clear acceptance criteria. Use when creating issues from discovery findings. |
This skill provides guidance for writing well-formed user stories with clear acceptance criteria.
As a [type of user],
I want [goal/desire],
So that [benefit/value].
Good:
As a registered user,
I want to reset my password via email,
So that I can regain access to my account if I forget my password.
Bad:
Add password reset feature.
The good example captures WHO needs it, WHAT they need, and WHY.
Good user stories are:
| Criteria | Description |
|---|---|
| Independent | Can be developed separately from other stories |
| Negotiable | Details can be discussed and refined |
| Valuable | Delivers clear value to the user |
| Estimable | Can be sized (fits in a single PR) |
| Small | Implementable in one PR, not weeks of work |
| Testable | Has clear acceptance criteria to verify |
Acceptance criteria define WHEN a story is complete. They should be:
Use checkbox format for easy verification:
## Acceptance Criteria
- [ ] User can request password reset with their email
- [ ] Reset link is sent to registered email only
- [ ] Reset link expires after 1 hour
- [ ] User sees error message for unregistered email
- [ ] User can set new password via reset link
- [ ] Old password no longer works after reset
Good criteria:
Bad criteria:
Large features should be broken into stories sized for a single PR.
By User Flow Step
By Data Entity
By User Type
By Complexity Layer
Break into:
| Issue | Story | Dependencies |
|---|---|---|
| #1 | Database schema for users | None |
| #2 | User registration endpoint | #1 |
| #3 | User login endpoint | #1 |
| #4 | Session management | #3 |
| #5 | Password reset flow | #2, #3 |
Each issue is one PR's worth of work.
## User Story
As a [type of user],
I want [goal/desire],
So that [benefit/value].
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
## Technical Notes
[Architecture decisions, approach, or constraints]
## UI/UX Requirements
[Design specs, wireframes, or "None - backend only"]
## Dependencies
[List as "Depends on #X" or "None - can be worked independently"]
## Out of Scope
[Explicitly list what is NOT included to avoid scope creep]
Bad: "As a user, I want a complete authentication system" Better: Split into registration, login, password reset, etc.
Bad: "Refactor the database layer" Better: "As a developer, I want a normalized user schema so that queries are faster"
Bad: "Login should work well" Better: "User is redirected to dashboard after successful login"
Bad: Only happy path criteria Better: Include error states, empty states, boundary conditions
Bad: No mention of required prior work Better: "Depends on #1 (User model must exist first)"
Before finalizing a story, verify: