aiox-pm

Name: aiox-pm
Availability: InStock
Author: hyagoviana

Generate PRDs, epics, and prioritization artifacts from product manager workflows.

1|Updated May 15, 2026

Search Tags:#roadmap #prioritization #product strategy #prd #epic planning #success metrics #business case

Ready to run

npx skills add https://github.com/hyagoviana/Sistema_Hyago_Viana_Adabtech --skill aiox-pm-hyagoviana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aiox-pm
Source: https://github.com/hyagoviana/Sistema_Hyago_Viana_Adabtech/tree/main/meu-projeto/.claude/skills/AIOX/agents/pm
Command: npx skills add https://github.com/hyagoviana/Sistema_Hyago_Viana_Adabtech --skill aiox-pm-hyagoviana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps product teams turn ideas and stakeholder input into clear, actionable product documentation and prioritization decisions instead of leaving them as scattered notes.

Core Features & Use Cases

PRD creation for greenfield and brownfield: Draft complete product requirements using appropriate templates and structured outputs that teams can execute.
Epic and story planning: Define epic scope for brownfield, then delegate story creation to the story-making specialist while keeping strategy coherent.
Strategic prioritization and roadmap planning: Produce prioritization (MoSCoW/RICE), business case framing, success metrics, and go/no-go readiness for stakeholder alignment.
Quick Start: Use purpose-built commands to go from planning to documentation and execution artifacts efficiently.

Quick Start

Tell the assistant: create-prd for my new product, including goals, target users, key requirements, success metrics, and a prioritized MVP plan.

Frequently Asked Questions about aiox-pm

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

FAQPage Schema

How do I create a PRD for a new product with clear success metrics and an MVP plan?▼

To create a PRD for a new product, use purpose-built commands to generate structured documentation including goals, target users, key requirements, success metrics, and a prioritized MVP plan. This applies structured templates to turn scattered ideas into actionable product requirements.

What is the best way to plan epics and define scope for brownfield product features?▼

Planning epics for brownfield features involves defining the epic scope strategically and delegating detailed story creation to a specialist. This ensures the epic planning maintains strategy coherence while breaking down requirements into executable stories.

How does strategic prioritization work for roadmap scoping and go/no-go decisions?▼

Strategic prioritization for roadmap scoping uses MoSCoW or RICE frameworks to produce business case framing and success metrics. This approach generates stakeholder-ready go/no-go readiness decisions based on structured prioritization artifacts.

Can I use this for both greenfield and brownfield product planning?▼

Yes, you can use this for both greenfield and brownfield product planning. It applies appropriate templates and structured outputs to draft complete product requirements, adapting its workflow to handle new product creation and existing feature expansion.

Do I need stakeholder input to develop a business case for product strategy?▼

You need stakeholder input to develop a business case for product strategy because the process turns stakeholder input and scattered ideas into clear, actionable product documentation and prioritization decisions for stakeholder alignment.