skills.rest
chieflatif
chieflatifCOMMUNITY
Explore all skills by this author →
GitHub

discover

Turn rough product ideas into validated product documents and governance artifacts.

2|1|Updated Mar 9, 2026
Search Tags:#planning#architecture#requirements#discovery#governance#product#stakeholders
One-click install
npx skills add https://github.com/chieflatif/vibeos-plugin --skill discover-chieflatif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/chieflatif/vibeos-plugin/tree/main/plugins/vibeos/skills/discover
Command: npx skills add https://github.com/chieflatif/vibeos-plugin --skill discover-chieflatif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run product discovery to turn a rough idea into validated product, anchor, and governance documents. Use when a user describes what they want to build, shares a product idea, says "I want to build/create/make...", mentions a "new project/app/product", or needs help defining scope, requirements, architecture, and technical approach. Also use for existing codebases when the user wants to analyze what they have.

Core Features & Use Cases

  • Turn a rough idea into a validated product vision, anchor documents, and governance artifacts.
  • Guide discovery with a structured flow: onboarding, intent capture, product shaping, and adaptive follow-ups.
  • Produce concrete artifacts: product brief, PRD, architecture outline, technical spec, anchor docs, and governance artifacts to proceed with development.

Quick Start

Describe your product idea in plain English and I will start the discovery flow.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I turn a rough product idea into validated product plans and governance artifacts?▼

To turn a rough product idea into validated product plans, run a structured discovery flow that captures intent and shapes the product through adaptive follow-ups to output architecture outlines and governance artifacts.

What is the best way to define scope, architecture, and technical approach for a new project?▼

Defining scope, architecture, and technical approach for a new project is best handled by running product discovery to produce concrete artifacts like a product brief, PRD, and technical spec.

Can I analyze an existing codebase to extract requirements and architecture outlines?▼

Yes, you can analyze an existing codebase to extract requirements and architecture outlines by running the discovery flow, which captures current state intent and generates structured product documents.

What documents do I need to generate during product discovery to guide development?▼

During product discovery, you need to generate anchor documents, a product brief, a PRD, a technical spec, and governance artifacts to provide a validated vision and phased plan for development.

How does stakeholder governance work when shaping product requirements from a rough idea?▼

Stakeholder governance works by applying structured discovery to rough ideas, capturing intent through onboarding and adaptive follow-ups to produce governance artifacts that anchor product requirements.

Related Skills

Explore More Product & Management Skills→
jdonohoojdonohoo
15

new-idea

Create a standardized discovery folder structure with input and output directories.

Community
Basic
LISSConsultingLISSConsulting
1

speckit-plan

Generate technical implementation plans from feature specifications.

Official
Advanced
truongnattruongnat

business-analysis

Clarify business requirements through a forced four-step workflow with spec quality review.

Community
Advanced
viktorbezdekviktorbezdek
10

creative-problem-solving

Generate innovative solutions for complex problems using structured frameworks and game theory.

Community
Intermediate