story

Generate detailed story specifications from MVP stories and scan against a hazard catalogue.

45|13|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/rakovi4/continue-framework --skill story-rakovi4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/story
Command: npx skills add https://github.com/rakovi4/continue-framework --skill story-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of detailed story specifications from MVP stories, streamlining documentation creation and ensuring consistent formatting.

Core Features & Use Cases

  • Story Specification Generation: Automatically create story specifications based on MVP stories list and product context.
  • Interactive Selection: Choose stories by name, number, or via interactive selection.
  • Hazard Catalogue Scan: Scans generated specifications against a hazard catalogue to ensure compliance and quality.

Quick Start

Generate a story specification for "Login/Logout" by running the command: /story "Login/Logout".

Frequently Asked Questions about story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate story specification generation from MVP stories?

Automating story specification generation from MVP stories involves processing a provided list to identify the target story and outputting detailed specifications. This streamlines documentation creation and ensures consistent formatting for software development.

What is a hazard catalog scan for story specifications?

A hazard catalog scan checks generated story specifications against a predefined catalog to ensure compliance with product guidelines. It verifies that the detailed documentation meets quality standards before development begins.

How do I generate a story specification for a specific MVP feature like Login?

To generate a story specification for a specific MVP feature, run the command with the story name in quotes, such as `/story "Login/Logout"`. The automation processes the input and creates the detailed specification.

Can I select MVP stories by name or number during specification generation?

Yes, you can select MVP stories by name, number, or through an interactive selection process. This flexibility allows you to target specific stories from your product backlog for detailed specification generation.

Does story specification automation require any external dependencies?

No external dependencies are required to automate story specification generation from MVP stories. The Skill operates independently using its internal scripts and references to process your product context and output documentation.

What are the limitations of automating MVP story specifications?

Automating MVP story specifications relies on the provided product context and a predefined hazard catalog for compliance. Specifications may not cover edge cases outside the predefined guidelines, requiring manual review for complex software development scenarios.