user-story-skill

Convert PRD artifacts into machine-consumable story maps with stable IDs.

Updated Jan 20, 2026

Search Tags:#traceability #prd #user-stories #open-questions #ambiguities #release-slices #story-map

Ready to run

npx skills add https://github.com/Galharel/my-codex-skills --skill user-story-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-story-skill
Source: https://github.com/Galharel/my-codex-skills/tree/main/user-story-skill
Command: npx skills add https://github.com/Galharel/my-codex-skills --skill user-story-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts PRD artifacts into flow-oriented user steps and a stable, machine-consumable story map with traceability, preserving IDs and surfacing ambiguities with targeted questions.

Core Features & Use Cases

Translate PRD outputs into flow-oriented user steps and a stable story map with traceability.
Preserve explicit lists and IDs verbatim to support downstream architecture skills.
Surface ambiguities with targeted questions and provide up to 3 options with pros/cons.
Enable downstream planning without dictating architecture or implementation decisions.
Output docs/story-map.json and docs/story-map.summary.md for Architecture skill.

Quick Start

Load your PRD artifacts (normalized_prd_markdown, prd_packet_json, prd_handoff_contract) to generate a complete, traceable story map with stable IDs ready for downstream architecture.

Frequently Asked Questions about user-story-skill

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

FAQPage Schema

How do I convert a PRD into traceable user stories?▼

To convert a PRD into traceable user stories, load your normalized PRD markdown, PRD packet JSON, or PRD handoff contract into the processor to generate a flow-oriented story map with stable IDs linked to FR/NFR requirements.

What is a story map with stable IDs and how does it preserve PRD traceability?▼

A story map with stable IDs is a machine-consumable representation of user flows that preserves verbatim lists and handoff data from the PRD, maintaining explicit traceability to personas, epics, and FR/NFR IDs for downstream architecture design.

How do I surface ambiguities in a PRD before architecture design?▼

To surface ambiguities in a PRD before architecture design, the transformation process identifies unclear areas and generates targeted questions accompanied by up to three options with pros and cons, ensuring downstream planning proceeds without missing requirements.

What PRD formats can I use to generate a machine-readable story map?▼

You can use normalized PRD markdown, PRD packet JSON, or PRD handoff contracts as input to generate machine-readable story map outputs, specifically producing a docs/story-map.json file and a docs/story-map.summary.md file for architecture skills.

Can I use this user story generation approach without dictating software architecture decisions?▼

Yes, you can use this user story generation approach to enable downstream planning without dictating architecture or implementation decisions, as it strictly focuses on translating PRD artifacts into deterministic, flow-oriented user steps with traceability.

Why does my user story mapping lose traceability to PRD requirements?▼

User story mapping loses traceability to PRD requirements when verbatim lists and IDs are not preserved; this processor prevents that by maintaining stable IDs and explicit links to FR/NFR requirements, personas, and epics throughout the transformation.