User Story Generator

Creates well-structured agile user stories with acceptance criteria for product development

Security Scan

The skill is an instruction-only user-story generator whose instructions, requirements, and absence of installs or credentials are consistent with its stated purpose.

Purpose & Capability

The name and description (generate agile user stories with acceptance criteria, story points, and technical considerations) match the SKILL.md content. The skill declares no binaries, env vars, or installs — which is appropriate for a purely prompt/instruction-based generator.

Instruction Scope

SKILL.md limits itself to describing inputs (feature description, personas, constraints) and expected formatted outputs. It does not instruct the agent to read files, access environment variables, call external endpoints, or collect unrelated system data.

Install Mechanism

No install spec and no code files are present. As an instruction-only skill, nothing is written to disk or downloaded during install, which is the lowest-risk pattern.

Credentials

The skill requires no environment variables, credentials, or config paths. There are no requests for secrets or unrelated service keys, which is proportionate for the stated functionality.

Persistence & Privilege

Flags: always is false (not force-included), user-invocable is true, and disable-model-invocation is false (agent may invoke autonomously) — these are normal defaults for a skill of this type. The skill does not request persistent system modification or access to other skills' configs.

Assessment

This skill appears coherent and low-risk: it only documents how to convert feature descriptions into user stories and asks for no credentials or installs. Before using it, avoid pasting sensitive or proprietary data into inputs (the skill will be handled by the agent/model), and review generated acceptance criteria and technical notes for accuracy. If you plan to allow autonomous invocation, be aware the agent can call the skill automatically (this is normal) — restrict that only if you have a policy requiring human review for generated requirements.

Description

Transform feature requests and product ideas into properly structured agile user stories. Generates stories following the "As a [role], I want [action], so that [benefit]" format with detailed acceptance criteria, story points estimation, and technical considerations.

How to Use

1. Input feature description or user need
2. Specify target user personas
3. Define technical constraints (if any)
4. Receive structured user stories with acceptance criteria

Example

Input:

Feature: Add social sharing capability to mobile app
Users: App users who want to share achievements
Priority: High
Sprint capacity: 8 story points

Output:

## User Stories: Social Sharing Feature

### Epic
**Epic:** Social Engagement Enhancement

---

### User Stories

#### Story 1: Share Achievement
**As a** mobile app user
**I want to** share my achievements to social media
**So that** I can celebrate with friends and motivate myself

**Acceptance Criteria:**
- [ ] Share button appears after completing any achievement
- [ ] Generates shareable image with achievement badge
- [ ] Supports Facebook, Twitter, Instagram, and WhatsApp
- [ ] Includes app download link in shared content
- [ ] User can add personal message before sharing

**Story Points:** 5
**Priority:** High

---

#### Story 2: View Friends' Achievements
**As a** mobile app user
**I want to** see my friends' shared achievements
**So that** I can stay motivated by their progress

**Acceptance Criteria:**
- [ ] "Friends Activity" tab visible on home screen
- [ ] Chronological feed of friends' achievements
- [ ] Ability to send congratulations emoji/reaction
- [ ] Privacy setting to hide achievements from specific friends

**Story Points:** 8
**Priority:** Medium

---

### Technical Considerations
- Implement native share sheet (iOS/Android)
- Generate OG images for social media preview
- Track sharing events in analytics
- Consider deep linking for shared content

### Dependencies
- Authentication system (existing)
- Achievement/badge system (existing)
- Privacy settings framework (existing)