orchestrator-pm

Define product vision, MVP scope, user stories, and prioritized backlog.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/shouvik/orchestrator --skill orchestrator-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-pm
Source: https://github.com/shouvik/orchestrator/tree/main/skills/orchestrator-pm
Command: npx skills add https://github.com/shouvik/orchestrator --skill orchestrator-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of clearly defining product requirements, scoping Minimum Viable Products (MVPs), and establishing a prioritized backlog for development.

Core Features & Use Cases

  • Product Vision & MVP Scoping: Articulates the overall product direction and defines the essential features for an initial release.
  • User Stories & Backlog Prioritization: Creates detailed user stories with acceptance criteria and organizes them into a prioritized development queue.
  • Success Metrics: Establishes key performance indicators to measure the product's success post-launch.
  • Use Case: A startup needs to define the core features for their new mobile app, create user stories for the development team, and decide which features are essential for the first launch.

Quick Start

Run the orchestrator-pm skill to define the product vision, MVP scope, user stories, and prioritized backlog for a new task management application.

Frequently Asked Questions about orchestrator-pm

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

FAQPage Schema
How do I define product vision and MVP scope for a new application?

To define product vision and MVP scope, you articulate the overall product direction and identify the essential features required for an initial release. This establishes a clear foundation separating core functionalities for launch from future iterations.

How do I write user stories with acceptance criteria for a prioritized backlog?

Writing user stories with acceptance criteria involves creating detailed development tasks and organizing them into a prioritized queue. This defines specific conditions that must be met for each feature to ensure the development team understands the requirements.

What is MVP scoping and when do I need to establish success metrics?

MVP scoping is the process of defining the essential features for an initial product release. You establish success metrics during this phase to set key performance indicators that will measure the product's post-launch effectiveness.

Can I use business analysis and UX research outputs for product scoping?

Yes, you can integrate upstream business analysis and UX research outputs into product scoping. This standalone scoping process adopts a Product Manager persona to generate structured deliverables like information architecture and prioritized backlogs.

What is the best way to structure information architecture for a new product?

The best way to structure information architecture is to define it alongside product vision and MVP scope. This ensures the foundational structure aligns with the prioritized backlog and user stories before development begins.