discovery-skill

Clarify ambiguous delivery requests into measurable project specifications with owner, scope, and open questions.

7|Updated Feb 19, 2026

Search Tags:#specification #validation #discovery #outcome definition #scope clarification #project intake

Ready to run

npx skills add https://github.com/MajesteitBart/delano --skill discovery-skill-majesteitbart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discovery-skill
Source: https://github.com/MajesteitBart/delano/tree/main/.agents/skills/discovery-skill
Command: npx skills add https://github.com/MajesteitBart/delano --skill discovery-skill-majesteitbart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps turn an unclear delivery request into a measurable, approvable project spec before planning begins. It is meant for situations where the outcome, owner, or constraints are still fuzzy and the work needs definition first.

Core Features & Use Cases

Outcome definition: Shapes a clear outcome hypothesis and success criteria for a new project.
Scope clarification: Separates in-scope work from explicit non-goals and open questions.
Operational setup: Creates or updates the project scaffold and validates the resulting spec against the runtime rules.
Use case: A maintainer receives an ambiguous request and uses this Skill to produce a precise spec, assumptions list, and clarification questions before execution starts.

Quick Start

Use this skill to define the project outcome, owner, constraints, and open questions for a new delivery request.

Frequently Asked Questions about discovery-skill

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

FAQPage Schema

How do I turn an ambiguous project request into a measurable specification?▼

To turn an ambiguous project request into a measurable specification, define the outcome hypothesis, assign an explicit owner, and establish clear success criteria. This ensures the delivery request is approvable before planning begins.

What is the best way to define project scope and non-goals during intake?▼

Defining project scope and non-goals during intake requires separating in-scope work from explicit non-goals. You must also document assumptions and open questions to clarify responsibility before execution starts.

Do I need a validated project scaffold before planning delivery work?▼

Yes, you need a validated project scaffold before planning delivery work. Creating or updating the scaffold and validating the resulting spec against runtime rules ensures the contract is actionable for execution.

When should I use outcome definition for early-stage project intake?▼

Use outcome definition for early-stage project intake when scope, success criteria, or responsibility are not yet defined. It shapes a clear outcome hypothesis when the work needs approval before planning can proceed.

How does scope clarification handle open questions and assumptions?▼

Scope clarification handles open questions and assumptions by explicitly separating in-scope work from non-goals. It produces an assumptions list and clarification questions to resolve fuzzy constraints before execution.

Can I validate a project specification against delivery runtime rules?▼

Yes, you can validate a project specification against delivery runtime rules. Operational setup validates the authored spec to ensure the resulting contract is actionable before the project moves into execution.