Convert ambiguous product requests into prioritized user stories for GitHub backlog planning.
npx skills add https://github.com/jammindev/house --skill po-jammindev
Please help me install this Agent Skill. Skill: po Source: https://github.com/jammindev/house/tree/main/.claude/skills/po Command: npx skills add https://github.com/jammindev/house --skill po-jammindev
This Skill helps transform an unclear product request into a set of small, testable, and prioritized user stories so the team can move from ambiguity to a backlog-ready plan.
Ask the po skill to break down your product request into prioritized user stories for the house project.
High-intent search queries and answers about installing and using this skill.
Turning vague product requests into ready backlog user stories requires clarifying the real user problem, scope, actors, and edge cases before decomposing the feature into atomic, testable stories formatted for issue tracking.
Breaking down a large feature for incremental delivery involves decomposing the scope into independent, prioritized lots, ensuring each story has clear acceptance criteria, constraints, and permissions suitable for the backlog.
Formatting user stories for GitHub issues requires structuring each story with testable acceptance criteria, scope boundaries, and priority levels aligned with repository conventions to ensure the backlog is immediately actionable.
Prioritizing user stories in a product backlog is best achieved by evaluating the clarified user problem, scope, and constraints, then sequencing the decomposed stories to support incremental delivery across multi-tenant workflows.
Clarifying permissions before scoping a feature for backlog planning is required because defining actors, edge cases, and access levels ensures the resulting user stories are atomic, testable, and accurately reflect the system constraints.
Story decomposition for product discovery should not be used when the initial product request lacks enough clarity to define the core users, scope, and acceptance criteria, as this prevents generating testable backlog items.
hfadhlullahGenerate Product Requirements Documents through an interview process.
shwilliamsonWrite user stories with acceptance criteria and INVEST guidelines.
githubGenerate production-grade PRDs with executive summaries, user stories, and technical specifications.
spandiosGenerate user stories with descriptions, design links, and acceptance criteria.
