Overview

Generates a self-contained story artifact that captures the goal, scope, acceptance criteria, tasks, and context needed for implementation later. It’s triggered by phrases like 'create the next story' or 'create story [story identifier]'. The artifact supports handoffs and consistency within the CORE module led by Scrum Master Bob.

How This Skill Works

When the user requests a story, the agent consults ./instructions.md, constructs a complete story file, and saves it in the project repository. The file includes goal, scope, acceptance criteria, tasks, and references needed for later implementation. After creation, it is validated against ./checklist.md to ensure completeness.

When to Use It

• User asks to generate the next sprint story or provides 'create story [id]'
• Initiating documentation for a new feature with a unique identifier
• Onboarding a new team member who needs a self-contained story artifact
• Handoff between teams requiring a shared, self-contained story file
• Generating standardized stories for a feature family or epic

Quick Start

1. Step 1: Issue a command like 'create the next story' or 'create story [id]'.
2. Step 2: The agent reads ./instructions.md, builds a context-rich story file, and saves it to the repo.
3. Step 3: Validate the file against ./checklist.md and report the result.

Best Practices

• Capture a unique story identifier in the filename and content
• Include goal, scope, acceptance criteria, tasks, and references
• Follow instructions.md for consistent structure and formatting
• Verify the created file against checklist.md after creation
• Store the story in the designated repository path for easy access

Example Use Cases

• create story user-authentication-v2
• create story checkout-flow-01
• create story mobile-dashboard-refresh
• create story user-profile-permissions
• create story search-results-pagination

Frequently Asked Questions