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
Decision gist · record as of 2026-06-18
product-owner captures and structures product ideas with automatic domain context detection and feature mapping. 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.
Use it when
- product-owner supports RICE scoring for features, MoSCoW prioritization method, and Value/Effort matrix prioritization.
- Yes.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
duc01226/EasyPlatform/product-owner · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
File tree — 1 file
.agents/skills/product-owner/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Capture and structure product ideas with domain context and feature mapping”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Business Analyst guides you through refining requirements into structured user stories using the As-a/I-want/So-that format while ensuring INVEST compliance. It extracts and references existing business rules from your project docs, investigates domain entities, and generates acceptance criteria in BDD (GIVEN/WHEN/THEN) format to close gaps and improve testability.
Refine transforms raw ideas into production-ready product backlog items through structured problem validation, requirements elicitation, and BDD-formatted acceptance criteria. The skill enforces hypothesis gates, mandatory user interviews, and dual estimation cycles to ensure teams have complete, testable scope before development begins.
problem-solving guides you through five systematic techniques—Simplification Cascades, Collision-Zone Thinking, Meta-Pattern Recognition, Inversion Exercise, and Scale Game—each designed to address specific types of stuck-ness. Match your symptom to the right technique, load its detailed reference, and apply the process step-by-step; combine multiple techniques when a problem requires it.
Sequential Thinking guides you through complex problem-solving using manageable thought sequences that adjust dynamically as understanding evolves. Build solutions step-by-step, explicitly mark revisions when insights change earlier reasoning, and branch to explore alternatives before converging on a verified approach.
idea guides you through structured idea capture with mandatory discovery and validation gates, ensuring problem statements stay technology-neutral and ready for downstream refinement. It auto-detects your project module, conducts focused user interviews, and outputs validated artifacts ready for conversion into backlog items.
Brainstorm runs your team through a scenario-aware ideation workflow—problem-solving, new product, or feature enhancement—using diverge-and-converge phases to move from raw ideas to a ranked shortlist of 3–5 candidates. Each finalist carries a problem statement, value hypothesis, riskiest assumption, and cheapest validation test, ensuring you commit to the right problem before building.
More skills issue-manage (MIT) · Super Product Owner (unlicensed) · Util Manage Todo (unlicensed) · marketing-strategy-pmm (MIT) · quality-gate-review (MIT) · product-owner (MIT)