create-user-stories — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited create-user-stories (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill handles project management tasks including user stories, tasks, issues, and Agile workflows.
Use this skill when the user asks to:
Always use this structure for user stories:
## 📝 User Story: [Title]
### ID
[PROJECT]-[N]
### Description
As a [role], I want to [feature] so that [benefit].
### Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
### Technical Notes
- [Technical considerations]
### Dependencies
- [Related stories/tasks]
### Priority
- [ ] Critical
- [ ] High
- [ ] Medium
- [ ] Low
### Estimation
- Story Points: [1/2/3/5/8/13]## ✅ Task: [Title]
### ID
[PROJECT]-TASK-[N]
### Description
[What needs to be done]
### Checklist
- [ ] Subtask 1
- [ ] Subtask 2
### Assigned To
[Developer/Team]
### Due Date
[Date]
### Status
- [ ] To Do
- [ ] In Progress
- [ ] Blocked
- [ ] DoneTo Do → In Progress → In Review → Done
↓
Blocked (→ To Do when unblocked)| Priority | Description | Response Time |
|---|---|---|
| Critical | Blocker, production down | Immediate |
| High | Major feature, deadline | 24h |
| Medium | Normal work | 1 week |
| Low | Nice to have | Backlog |
User: "Create a user story for user authentication"
Response:
## 📝 User Story: User Authentication
### ID
MYAPP-101
### Description
As a user, I want to log in with email and password so that I can access my secure account.
### Acceptance Criteria
- [ ] User can register with email/password
- [ ] User can log in with credentials
- [ ] User receives confirmation email
- [ ] User can reset password
- [ ] Session expires after 30 minutes of inactivity
### Technical Notes
- Use JWT tokens
- Store password hashed with bcrypt
- Implement rate limiting on login
### Dependencies
- None ( foundational story)
### Priority
- [x] Critical
### Estimation
- Story Points: 8~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.