product-owner

Automate daily standups, prioritization, and cross-project awareness for development teams.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/fyrsmithlabs/marketplace --skill product-owner-fyrsmithlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-owner
Source: https://github.com/fyrsmithlabs/marketplace/tree/main/plugins/fs-dev/skills/product-owner
Command: npx skills add https://github.com/fyrsmithlabs/marketplace --skill product-owner-fyrsmithlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to run consistent standups and keep priorities aligned across multiple repositories. The Product Owner Skill automates standups, prioritization, and cross-project awareness, reducing context switching and misalignment.

Core Features & Use Cases

  • Daily standup generation: synthesize blockers, progress, and priorities into a concise summary.
  • WSJF prioritization & DORA metrics: apply objective scoring to rank work and forecast delivery.
  • Cross-project awareness: surface dependencies and impact across repositories.

Quick Start

Use the product-owner skill during standups to summarize blockers and surface prioritized actions.

Frequently Asked Questions about product-owner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate daily standups and summarize blockers across multiple GitHub repositories?

You can automate daily standups by synthesizing GitHub state, blockers, and progress into a concise summary. This cross-project awareness reduces context switching and surfaces dependencies across multiple repositories for development teams.

What is the best way to apply WSJF prioritization to a development backlog?

Apply WSJF prioritization to rank backlog work using objective scoring. This mechanism helps product owners forecast delivery and align priorities across projects by calculating weighted shortest job first values.

Can I use DORA metrics to forecast delivery and prioritize cross-project work?

Yes, DORA metrics integrate with prioritization to forecast delivery. Combining DORA metrics with WSJF scoring applies objective ranking to development work and surfaces cross-project impact across repositories.

How do I map dependencies and coordinate cross-repo awareness for development teams?

Map dependencies by integrating GitHub state to surface cross-repo impact. Cross-project awareness coordinates multiple repositories, reducing misalignment and context switching during backlog planning and standups.

Do I need contextd memory to run cross-project prioritization and standups?

No, contextd memory is optional for running standups and prioritization. The core functionality synthesizes GitHub state, DORA metrics, and WSJF prioritization independently, utilizing contextd memory only as available.

When should I not use automated backlog prioritization for standups?

Avoid automated backlog prioritization when teams lack consistent GitHub state updates or require highly subjective, nuanced ranking. The mechanism applies objective WSJF scoring and DORA metrics, which depend on reliable repository data.