project-discovery

Guide project managers through structured discovery interviews to create a Project Definition Document.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/magnum6actual/dev-sop --skill project-discovery-magnum6actual
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-discovery
Source: https://github.com/magnum6actual/dev-sop/tree/main/planning/skills/project-discovery
Command: npx skills add https://github.com/magnum6actual/dev-sop --skill project-discovery-magnum6actual

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides a PM through structured discovery interviews to transform a white paper or concept into a buildable project definition.

Core Features & Use Cases

  • Four phases of conversation to uncover vision, risks, scope, and architecture.
  • Guidance on forming sponsor-PM alignment and producing a complete Project Definition Document.
  • Reusable templates and references to templates.md to standardize outputs.

Quick Start

Initiate a project discovery session with a sponsor using a white paper as the starting artifact.

Frequently Asked Questions about project-discovery

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

FAQPage Schema
How do I turn a white paper into a buildable project definition?

To turn a white paper into a buildable project definition, use structured discovery interviews to uncover vision, risks, scope, and architecture, producing a complete Project Definition Document for sponsor alignment.

What is the best way to structure project discovery interviews for sponsor alignment?

The best way to structure project discovery interviews is through a four-phase PM-led conversation that enforces explicit scope boundaries and risk capture, ensuring sponsor alignment before transitioning from ideation to execution.

How do I transition a project from ideation to execution when starting with only a white paper?

Transition from ideation to execution by applying a structured four-phase interview process to the white paper, capturing explicit scope boundaries and risks to generate a standardized Project Definition Document template.

What should be included in a Project Definition Document after sponsor discovery interviews?

A Project Definition Document should include the uncovered vision, explicit scope boundaries, captured risks, and architectural details gathered during the four-phase PM-led discovery interviews, standardized via a template reference.

When do I need to use a structured project discovery process?

You need a structured project discovery process when starting a new project with a white paper but no roadmap, when sponsor alignment is needed, or when transitioning a concept from ideation to execution.

Does this project discovery process enforce scope boundaries and risk capture?

Yes, the project discovery process enforces explicit scope boundaries and risk capture throughout its four-phase interview structure to ensure the resulting project definition is buildable and aligned with sponsors.