product-team

Generates product specs, flows, roadmaps, sprint plans, and validation tests from ideas and feedback.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill product-team-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-team
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/product-team
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill product-team-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a product idea or pile of feedback into decisions a team can actually build from is hard: assumptions go unlabeled, specs are too vague for engineering, and prioritization follows whoever is loudest. This Skill acts as a research-led product strategist that separates facts from assumptions and produces actionable specs, flows, roadmaps, and sprint plans. ## Core Features & Use Cases - Idea validation and research: Clarify the underlying problem, identify the riskiest assumptions, and design the cheapest test with pre-set success criteria instead of treating interest or sign-ups as proof of demand. - Implementation-ready artifacts: Produce specifications, complete user/system flows (including error and edge states), outcome-based roadmaps, sprint stories with acceptance criteria, decision records, and experiment definitions using built-in templates. - Prioritization with the right framework: Apply JTBD, RICE, MoSCoW, Kano, Opportunity Scoring, Working Backwards, or Cost of Delay only when the decision warrants it, with reasoning explained in prose. - Use Case: A founder says "should we build this feature?" The Skill digs into the underlying job-to-be-done, labels what is evidence versus assumption, proposes a cheap validation test that runs alongside building, and drafts a spec engineering can act on. ## Quick Start Ask the assistant to write a spec for your feature idea or to help you prioritize your backlog, and it will infer the right workflow automatically.

Frequently Asked Questions about product-team

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

FAQPage Schema
How do I write a product spec that engineering can build from?

Use the /spec command to generate a specification covering context, goals and non-goals, functional requirements, permissions, flows, error states, acceptance criteria, and rollout risks. Requirements are written to be specific and testable, avoiding vague terms like fast or user-friendly without defined behavior.

How do I validate a product idea before building it?

Use /idea or /validate to identify the riskiest assumptions behind the idea, then design the cheapest test with success and failure criteria set in advance. The Skill treats a founder's hunch as a legitimate starting point and pairs every weak signal with a test that runs alongside building.

Which prioritization framework should I use for my backlog?

The Skill selects based on your situation: RICE when you have usage data, Opportunity Scoring for early-stage products, MoSCoW for cross-team scope negotiation, and Cost of Delay when timing matters. It explains the reasoning in prose rather than presenting a score as final.

Can this Skill plan a sprint from a product spec?

Yes, the /sprint command turns approved scope into stories with outcomes, acceptance criteria, dependencies, test coverage, and definition of done. It splits oversized work into vertical slices and separates committed work from stretch work.

When should I not use a formal scoring framework like RICE?

Avoid RICE for early-stage products without usage data, since reach and impact estimates become false precision on guesses. For a simple two-option decision, reasoned prose beats a scoring exercise; the Skill names when a framework is the wrong tool.