القائمة
Generate and validate user stories from requirements with INVEST validation and acceptance criteria
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Expert Electron application architecture skill for IPC design, main/renderer/preload boundaries, security hardening, performance optimization, packaging strategy, native integration, and cross-platform desktop development. Use when reviewing or designing Electron apps, planning migrations, auditing architecture risks, choosing IPC patterns, diagnosing startup or memory issues, or coordinating related Electron skills.
Generates DrawIO XML diagrams for Amazon Web Services architectures from text descriptions or images. Analyzes existing .drawio files to extract AWS components. Use for AWS architecture diagrams, cloud infrastructure documentation, or when converting AWS diagram images to editable DrawIO format.
Generates DrawIO XML diagrams for Google Cloud Platform architectures from text descriptions or images. Analyzes existing .drawio files to extract GCP components. Use for GCP architecture diagrams, cloud infrastructure documentation, or when converting GCP diagram images to editable DrawIO format.
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
Orchestrate a babysitter run. use this command to start babysitting a complex workflow.
Clean up .a5c/runs and .a5c/processes directories. Aggregates insights from completed/failed runs into docs/run-history-insights.md, then removes old run data and orphaned process files.
| name | user-story-writer |
| description | Generate and validate user stories from requirements with INVEST validation and acceptance criteria |
| allowed-tools | ["Read","Write","Glob","Grep","Bash"] |
| metadata | {"specialization":"business-analysis","domain":"business","id":"SK-006","category":"Agile Requirements"} |
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 |