product-orchestrator

Orchestrate multi-model deliberation for product scope, architecture, and go-to-market decisions.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/MoxyWolfLLC/moxywolf-plugins --skill product-orchestrator-moxywolfllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-orchestrator
Source: https://github.com/MoxyWolfLLC/moxywolf-plugins/tree/main/plugins/product-orchestrator/skills/product-orchestrator
Command: npx skills add https://github.com/MoxyWolfLLC/moxywolf-plugins --skill product-orchestrator-moxywolfllc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you make better product decisions by forcing structured multi-model deliberation on scope, architecture, and go-to-market choices before execution starts.

Core Features & Use Cases

  • Decision classification: Routes requests into the right deliberation track (scope, architecture, GTM) or skips deliberation for execute-only asks.
  • Template-driven council framing: Loads the correct role prompts and decision structure to produce explicit recommendations and tradeoffs.
  • Actionable decision output: Extracts clear recommendation, risks, next actions, and downstream routing targets to keep momentum.
  • Decision records: Produces a product decision record to preserve institutional memory for future sessions.

Quick Start

Use the product-orchestrator skill to deliberate whether you should expand product scope for your next milestone by saying: "Deliberate on my product scope decision for v1, given these constraints: time, money, and the user feedback we have so far."

Frequently Asked Questions about product-orchestrator

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

FAQPage Schema
How do I structure product decisions for scope and architecture before execution?

Product scope decisions are evaluated by routing the request into a structured deliberation track that applies template-based role prompts to generate explicit recommendations, tradeoffs, and downstream next actions.

What is the best way to document go-to-market strategy choices for future reference?

You can document go-to-market strategy choices by generating a product decision record within the deliberation output, which preserves institutional memory and outlines downstream routing targets for future sessions.

Can I skip deliberation and route directly to execution for simple product tasks?

Yes, the decision classification mechanism evaluates your request and routes directly to execution for execute-only asks, bypassing council-style deliberation when structured evaluation is not needed.

Does product decision routing work for evaluating architecture choices and tradeoffs?

Yes, product decision routing evaluates architecture choices by loading template-driven council framing that produces explicit recommendations, risks, confidence levels, and downstream routing targets.

What context do I need to provide for a product scope deliberation session?

You need to provide a context block containing product details and stakes, which the template-based role prompts use to evaluate constraints and generate structured output with explicit tradeoffs.

When should I avoid multi-model deliberation for my product sprint planning?

You should avoid multi-model deliberation for product sprint planning when the request is an execute-only ask that does not require evaluating what to build, how to build it, or how to position it.