story

Generate story specification documents from an MVP story list.

2|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/is-ivanov/rpm-ddd --skill story-is-ivanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story
Source: https://github.com/is-ivanov/rpm-ddd/tree/main/.opencode/skills/story
Command: npx skills add https://github.com/is-ivanov/rpm-ddd --skill story-is-ivanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps transform a high-level MVP story list into concise, implementation-ready story specifications without losing important product context, historical drafts, or supporting notes.

Core Features & Use Cases

  • Story lookup and selection: Finds the target story by number, exact name, or interactive selection from the product story map.
  • Context-aware specification drafting: Reads product description, load expectations, archived drafts, existing specs, and optional story-specific interview notes before writing.
  • Two-document output: Produces a short main specification for execution and a separate notes file for warnings, suggestions, and technical detail.
  • Use case: When a product team has an MVP story map but needs standardized documentation for delivery, this Skill creates the story folder and writes both the implementation-focused spec and its supporting notes.

Quick Start

Ask the story skill to generate a specification for a chosen MVP story by name or number.

Frequently Asked Questions about story

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

FAQPage Schema
How do I generate implementation-ready story specifications from an MVP story list?

To generate story specifications from an MVP story list, select a target story by name or number, and the tool reads product context and archived drafts to produce concise implementation-focused specs and separate technical notes.

What is story mapping and how does it help create standardized product docs?

Story mapping organizes MVP features into a structured list, which this process uses to locate target stories by number or name and generate standardized product documentation folders for delivery.

How do I avoid duplicate story specifications when drafting product documentation?

To avoid duplicate story specifications, the system reviews existing specs and archived drafts within the product context before writing new implementation-focused documentation.

Can I use interview notes and product context to draft MVP requirements?

Yes, you can incorporate optional story-specific interview notes and product description documents to inform the context-aware specification drafting process for MVP requirements.

What's the best way to separate technical details from main story specs?

The best way to separate technical details is to use a two-document output: a short main specification for execution and a distinct notes file for warnings, suggestions, and technical detail.

Does this approach work for reviewing archived drafts and existing story specs?

Yes, this approach works for reviewing archived drafts by reading existing specifications and historical notes before creating a new story folder, ensuring context is preserved without duplication.