pm-story-write

Generate INVEST-compliant user stories with acceptance criteria from product concepts.

25|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/parhumm/jaan-to --skill pm-story-write
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-story-write
Source: https://github.com/parhumm/jaan-to/tree/main/adapters/codex/skillpack/skills/pm-story-write
Command: npx skills add https://github.com/parhumm/jaan-to --skill pm-story-write

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates well-structured, INVEST-compliant user stories from product concepts, eliminating manual drafting and ensuring consistent acceptance criteria across teams.

Core Features & Use Cases

  • Parse input formats: feature-persona-goal, narrative descriptions, Jira context, or design references.
  • Produce 3-7 acceptance criteria organized as Gherkin-style scenarios following INVEST guidelines.
  • Plan story structure with clear scope, dependencies, and metadata (epic, priority, labels).
  • Output ready-to-run story artifacts in the JAAN_OUTPUTS_DIR, including a YAML frontmatter and a Markdown body; embeds design references when provided.

Quick Start

Provide input to /jaan-to:pm-story-write using any supported format to generate a draft story ready for review.

Frequently Asked Questions about pm-story-write

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

FAQPage Schema
How do I generate user stories with INVEST compliance from a feature description?

Generate INVEST-compliant user stories by parsing feature-persona-goal inputs, narrative descriptions, or Jira context to produce structured markdown with clear scope, dependencies, and 3-7 Gherkin-style acceptance criteria.

What is the best way to write testable acceptance criteria for product concepts?

Write testable acceptance criteria by mapping edge cases and planning 3-7 Gherkin-style scenarios that enforce INVEST guidelines, ensuring your product concepts translate into ready-to-run story artifacts.

Can I use Jira context to draft user stories and acceptance criteria automatically?

Yes, you can use Jira context to draft user stories automatically; the parser ingests Jira inputs to generate story metadata, including epic, priority, and labels, alongside a markdown body.

Does user story generation support embedding design references for full storytelling?

Yes, user story generation supports embedding design references; when provided, they are integrated into the output to deliver full storytelling context within the YAML frontmatter and markdown body.

How do I output ready-to-run story artifacts with YAML frontmatter and a markdown body?

Output ready-to-run story artifacts by directing the generated INVEST-compliant stories to the designated outputs directory, producing a complete file containing YAML frontmatter and a markdown story body.

What limitations exist when parsing narrative descriptions for user story generation?

The main limitation is that narrative descriptions must align with supported formats like feature-persona-goal or Jira context to successfully map edge cases and enforce INVEST compliance during story generation.