product-owner
product-owner helps teams structure raw concepts into actionable backlog items by auto-detecting project modules and injecting relevant feature context. It supports RICE scoring, MoSCoW classification, and Value/Effort prioritization to align ideas with business goals. Built for Clean Architecture and CQRS projects, it enforces validation interviews and numeric priority ordering to ensure decisions are grounded in project reality.
product-owner captures and structures product ideas with automatic domain context detection and feature mapping.
AI-generated summary based on this skill's SKILL.md
Install
duc01226/EasyPlatform/product-owner · repository language: C#
git clone https://github.com/duc01226/EasyPlatform
cp -r EasyPlatform/.agents/skills/product-owner ~/.claude/skills/product-ownernpx skillfed install duc01226/EasyPlatform/product-ownerFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does product-owner help with product backlog prioritization framework?
product-owner enables teams to apply structured prioritization frameworks including RICE scoring, MoSCoW classification, and Value/Effort matrix analysis. By auto-detecting your project's modules and injecting relevant feature context, it helps align backlog items with business goals and ensures numeric priority ordering grounds decisions in project reality.
What prioritization methods does product-owner support?
product-owner supports RICE scoring for features, MoSCoW prioritization method, and Value/Effort matrix prioritization. Each framework helps teams evaluate impact, urgency, and resource constraints differently, allowing you to choose the approach that best fits your project's needs and stakeholder alignment requirements.
Can product-owner help manage product ideas and backlog?
Yes. product-owner structures raw concepts into actionable backlog items through its idea capture and refinement process. It guides the product idea to backlog workflow, supports PBI creation and tracking with clear acceptance criteria using GIVEN WHEN THEN format, and enforces validation interviews to ensure scope is grounded in real user needs.
How does product-owner support sprint planning and capacity?
product-owner assists sprint planning and capacity management by integrating velocity-based capacity planning with stakeholder communication templates. It helps define sprint goals, order backlog items with dependency awareness, and ensure teams communicate realistic commitments based on measured team velocity.
What makes product-owner suitable for Clean Architecture projects?
product-owner is built for Clean Architecture and CQRS projects, meaning it auto-detects your project's modular structure and injects domain-specific feature context into backlog items. This ensures product decisions respect architectural boundaries and that feature mapping aligns with your codebase organization.
How does product-owner validate product assumptions?
product-owner enforces validation interviews and structured assumption testing before backlog completion. This ensures that feature scope and acceptance criteria are grounded in actual user feedback and project reality, reducing the risk of building features that don't address real needs.
SKILL.md
rendered from the published skill — quoted content, verbatim
> Codex compatibility note:
>
> - Invoke repository skills with $skill-name in Codex; this mirrored copy rewrites legacy Claude /skill-name references.
> - Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.
> - User-question prompts mean to ask the user directly in Codex.
> - Ignore Claude-specific mode-switch instructions when they appear.
> - Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.
> - Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
> - Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.
> - For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.
> -
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agents/skills/product-owner/SKILL.md