Convert PRD artifacts into machine-consumable story maps with stable IDs.
npx skills add https://github.com/Galharel/my-codex-skills --skill user-story-skill
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
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.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
GalharelConverts a messy PRD into a normalized Markdown document and JSON packet.
GalharelMap PRD and story-map artifacts to a traceable system architecture package.
ImaginerLabsExtract FRs and NFRs from PRD documents into epics and stories.
EONMUNConvert feature ideas into technology-agnostic specifications with user stories and acceptance criteria.
