Generate structured job stories from PRDs and research findings.
npx skills add https://github.com/tylersahagun/elmer --skill job-stories-tylersahagun
Please help me install this Agent Skill. Skill: job-stories Source: https://github.com/tylersahagun/elmer/tree/main/.cursor/skills/job-stories Command: npx skills add https://github.com/tylersahagun/elmer --skill job-stories-tylersahagun
This Skill addresses the challenge of clearly communicating implementation requirements by translating product needs into a standardized job story format, ensuring that the "situation," "motivation," and "outcome" are explicitly captured for engineering and product teams.
Generate job stories for the new user authentication feature using the attached PRD and research documents.
High-intent search queries and answers about installing and using this skill.
Generate job stories from product requirements by processing PRDs and user research to produce structured outputs with situation, motivation, and outcome for clear engineering handoff. This standardizes implementation guidance for development teams.
The JTBD format structures implementation requirements by explicitly capturing the user's situation, motivation, and desired outcome. Use it during product development to translate user research into unambiguous engineering handoff guidance.
Convert user research findings into structured job stories by processing the research context alongside your PRD to define the situation, motivation, and outcome needed for implementation. This ensures research translates directly into development needs.
Yes, you can generate job stories for a new feature by attaching your PRD and research documents. It processes the provided product requirements to outline the user's context and desired outcome for engineering teams.
The best way to structure engineering handoff requirements is using the JTBD format, which preserves the situation, motivation, and outcome for each implementation need. This approach facilitates clear communication across the product development lifecycle.
Use job stories instead of traditional user stories to explicitly capture situation, motivation, and outcome in your requirements. This format provides unambiguous implementation guidance that preserves user context for engineering teams.
abhishekchoudhariConvert PRDs into Jira-ready Epic and Story hierarchies.
abhishekchoudhariCreate job stories in a When-I-want-so format with acceptance criteria.
luissimon96Automate the mcp-graph HANDOFF phase with PR creation and documentation validation.
shalevaminGenerate job stories with acceptance criteria using the When-I-want-so format.
