discovery-high-level-plan

Transform vague human intent into a governed discovery plan with validation gates.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill discovery-high-level-plan-petrsimonidesxart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery-high-level-plan
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/discovery/discovery-high-level-plan
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill discovery-high-level-plan-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates vague or broad human intent into a concrete, governed discovery action plan, ensuring alignment before artefacts are created.

Core Features & Use Cases

  • Plan discovery scope and determine artefacts needed.
  • Select and sequence necessary skills with validation gates.
  • Provide ready-to-deliver discovery plans for product and research initiatives.

Quick Start

Provide a vague idea or problem statement and let this skill generate a minimal, governed discovery plan with validation gates.

Frequently Asked Questions about discovery-high-level-plan

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

FAQPage Schema
What is a governed discovery plan in product management?

A governed discovery plan translates vague intent into a structured workflow with goals, sequenced steps, validation gates, and expected artefacts. It ensures alignment and compliance before any product delivery begins.

How do I turn a vague product idea into a concrete discovery workflow?

To turn a vague idea into a discovery workflow, input your problem statement to generate a minimal plan. This plan sequences necessary steps, defines artefact expectations, and sets validation gates for readiness.

When do I need validation gates in a discovery planning workflow?

You need validation gates in a discovery workflow when multiple planning steps are required before creating artefacts. Gates ensure governance compliance and verify readiness before proceeding to product delivery.

Can I use this approach for early-stage product research initiatives?

Yes, you can use this discovery planning approach for early-stage product research. It applies specifically to broad planning phases, scoping necessary actions and determining required artefacts before delivery.

What is the best way to scope artefacts needed for a product discovery phase?

The best way to scope required artefacts is to generate a governed discovery plan from your initial problem statement. This plan explicitly outlines artefact expectations alongside goals and validation steps.

How do I know if my discovery plan is ready for delivery?

A discovery plan is ready for delivery when it includes a ready-for-delivery indicator. This is achieved by passing all defined validation gates and meeting the outlined governance-compliant artefact expectations.