Translate business objectives into user stories with acceptance criteria.
npx skills add https://github.com/VitorAndTxr/omni-sw --skill po-vitorandtxr
Please help me install this Agent Skill. Skill: po Source: https://github.com/VitorAndTxr/omni-sw/tree/main/skills/po Command: npx skills add https://github.com/VitorAndTxr/omni-sw --skill po-vitorandtxr
Product Owner — Bridge between client and technical team. Translates business requirements into actionable user stories with acceptance criteria, prioritizes the backlog, and resolves ambiguous business rules. Use when: (1) breaking down a project brief into user stories (/po plan), (2) migrating a legacy BACKLOG.md to the JSON backlog system (/po migrate), (3) reviewing design for business accuracy (/po validate), (4) reviewing documentation for business accuracy (/po document), or (5) user says "po", "product owner", "backlog", "user stories", "acceptance criteria", "business rules", "migrate backlog".
Provide a project brief to the PO and generate a structured backlog of user stories with acceptance criteria.
High-intent search queries and answers about installing and using this skill.
To break down a project brief into user stories, provide the brief to the Product Owner workflow to generate a structured backlog of actionable items with clearly defined acceptance criteria. It translates business requirements into ready-to-implement stories.
To migrate a legacy BACKLOG.md to a JSON backlog system, run the migration command to parse existing entries and convert them into structured JSON backlog items. This process modernizes your backlog data while maintaining full traceability of user stories.
Validating design decisions against business rules requires reviewing design artifacts to ensure they accurately represent the intended business logic. The validation process checks documentation and design outputs for business accuracy, resolving any ambiguous rules before implementation.
Yes, you can prioritize a backlog for cross-functional teams by translating business objectives into actionable backlog items. It enforces a structured workflow that creates stories with IDs, transitions statuses, and renders backlog artifacts for technical teams.
Resolving ambiguous business rules when writing user stories involves bridging the gap between client requirements and the technical team. The process translates vague business objectives into actionable backlog items with explicit acceptance criteria.
Automating user story generation from project briefs is limited by the clarity of the initial business objectives provided. It requires a structured project brief to produce actionable backlog items and cannot invent missing business rules or technical requirements.
Hoang604Break high-level backlog items into ordered executable sub-items in BACKLOG.md.
belokonmCoordinate product strategy, roadmaps, and requirements across teams.
nmoralescyberSynchronize external tracker tasks into the TASKS.md backlog.
bychrisrManage product backlogs and user story lifecycles with automated validation and prioritization.
