Results for “user-stories”

Analyzes requirements and produces four artifact files: requirements, user stories, acceptance criteria, and business rules, with optional SRS workflow integration.

Generates a structured Product Requirements Document (PRD) for a new feature, including clarifying questions, user stories, functional requirements, and success metrics.

Generate comprehensive Product Requirements Documents (PRDs) for software systems and AI-powered features, including executive summaries, user stories, technical specifications, and risk analysis.

Guide product managers through breaking down epics into user stories using the Humanizing Work methodology with 9 splitting patterns.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Generates a structured Product Requirements Document for the MÄÄK dating app, with clarifying questions, right-sized user stories, and verifiable acceptance criteria.

Run a user story mapping workshop with adaptive questions and a structured map output, generating backbone activities, user tasks, and release slices for a workflow.

Breaks applications or features into thin vertical user-story slices with clear acceptance criteria and user-observable value, suitable for backlog planning and feature decomposition.

Analyzes requirements and produces four artifact files: requirements.md, user-stories.md, acceptance-criteria.md, and business-rules.md, with optional loading from SRS workflow artifacts.

Converts existing PRDs into the prd.json format used by the Ralph autonomous agent system, including splitting large features into right-sized stories and creating a progress file.

Turns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Extracts the problem, target users, and jobs-to-be-done, runs a quick competitive scan (web if available, logged as a gap if not), drafts the full PRD (problem, personas, user stories.

Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context.

Creates product backlog items in Why-What-Acceptance format, producing independent, valuable, testable items with strategic context.

Guide product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document.

Guides a structured interview and codebase exploration to produce a PRD, then submits it as a GitHub issue.

Writes user-focused acceptance criteria for Jira stories using Given/When/Then scenarios, and updates the ticket via the Atlassian MCP server.

Synthesize the current conversation and codebase context into a Product Requirements Document and publish it to the project's issue tracker.

Takes a high-level feature from an Epic and generates a detailed Product Requirements Document (PRD) in Markdown, covering goals, user stories, requirements, and acceptance criteria.