discovering

Clarify vague project ideas into goals, scope, and a discovery brief.

14|1|Updated Feb 1, 2026

Search Tags:#requirements #alignment #scope #project-planning #stakeholders #discover #discovery-brief

Ready to run

npx skills add https://github.com/azat-io/ai-config --skill discovering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discovering
Source: https://github.com/azat-io/ai-config/tree/main/skills/discovering
Command: npx skills add https://github.com/azat-io/ai-config --skill discovering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams and stakeholders quickly crystallize goals, scope, and success criteria when ideas are vague.

Core Features & Use Cases

Context-first discovery: gather background from code, docs, and stakeholders to establish a shared understanding.
Guided decision flow: ask a single focused question at a time and propose 2-3 high-level directions with trade-offs.
Discovery brief & sign-off: deliver a concise brief with goal, constraints, recommended direction, and open questions for stakeholder alignment.

Quick Start

Use the Discovering skill to align on project goals and scope before design or implementation begins.

Frequently Asked Questions about discovering

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

FAQPage Schema

How do I clarify vague project ideas and align stakeholders before technical work begins?▼

Clarifying vague project ideas requires gathering context first, then defining goals and scope. You can establish shared understanding by asking focused questions, proposing high-level approaches with trade-offs, and delivering a discovery brief for stakeholder sign-off before implementation.

What is a discovery brief and when do I need one for project planning?▼

A discovery brief is a concise document outlining project goals, constraints, recommended directions, and open questions. You need one when project scope is unclear, multiple interpretations exist among stakeholders, or alignment is required before technical work begins.

How do I define project scope when the requirements are unclear?▼

Defining project scope with unclear requirements involves gathering background context from stakeholders, docs, and code. By presenting 2-3 high-level directions with trade-offs and asking single focused questions, you can crystallize success criteria and finalize scope.

Can I use a guided decision flow to resolve multiple stakeholder interpretations?▼

A guided decision flow resolves multiple stakeholder interpretations by asking one focused question at a time and proposing high-level directions with trade-offs. This context-first discovery approach establishes shared understanding and aligns goals before technical implementation.

What is the best way to gather context for project discovery?▼

The best way to gather context for project discovery involves collecting background from code, docs, and stakeholders. This context-first approach establishes a shared understanding, allowing you to define success criteria, propose directions, and deliver a concise brief for sign-off.

Why does my project discovery process need stakeholder sign-off?▼

Project discovery needs stakeholder sign-off to ensure alignment on goals, constraints, and recommended directions before technical work begins. Delivering a discovery brief formalizes this agreement, preventing scope creep and conflicting interpretations during implementation.