user-story-writer — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited user-story-writer (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.
The User Story Writer skill provides specialized capabilities for creating, validating, and managing user stories from business requirements. This skill enables conversion of traditional requirements into agile user stories with proper structure, validation against INVEST criteria, and comprehensive acceptance criteria.
Convert these requirements to user stories:
[BRD requirements list]
Include persona identification and acceptance criteria for each story.Validate these user stories against INVEST criteria:
[User story list]
Provide scores and improvement recommendations.Split this epic into smaller user stories:
[Epic description]
Maintain value delivery and generate acceptance criteria for each.Create a story map for this product:
[Product description and user activities]
Organize by user journey and define release slices.This skill integrates with the following business analysis processes:
As a [type of user],
I want [some goal],
So that [some reason/benefit].When [situation],
I want to [motivation],
So I can [expected outcome].| Criterion | Description | Validation Question |
|---|---|---|
| Independent | Can be developed in any order | Does this story depend on other stories? |
| Negotiable | Details can be refined | Is there room for discussion? |
| Valuable | Delivers user/business value | What value does this provide? |
| Estimable | Can be sized | Can we estimate the effort? |
| Small | Fits in a sprint | Can it be completed in one sprint? |
| Testable | Has clear acceptance criteria | How will we know it's done? |
Given [precondition/context]
When [action/trigger]
Then [expected outcome]
And [additional outcome]| Points | Description |
|---|---|
| 1 | Trivial, well-understood |
| 2 | Small, minor complexity |
| 3 | Medium, some unknowns |
| 5 | Medium-large, notable complexity |
| 8 | Large, significant unknowns |
| 13 | Very large, should consider splitting |
| 21+ | Epic, must be split |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.