discovery-high-level-plan

Transform vague human intent into a structured discovery action plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill tackles situations where the user's intent is vague, broad, or requires multiple steps to clarify before any concrete action can be taken. It prevents wasted effort by ensuring a clear, governed plan is established first.

Core Features & Use Cases

  • Intent Clarification: Transforms unclear goals into actionable discovery steps.
  • Action Planning: Outlines a sequence of skills needed to achieve a high-level objective.
  • Use Case: When a user says "I have an idea for a new feature," this skill will help define what needs to be discovered first, like market research, user needs analysis, and technical feasibility, before any development work begins.

Quick Start

Use discovery-high-level-plan to create a plan for understanding user drop-off during onboarding.

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 discovery action plan and when do I need one?

A discovery action plan outlines a logical sequence of skills and validation gates to clarify vague objectives. You need one when your project intent is broad and requires multiple discovery steps before concrete development can safely begin.

How do I turn a vague feature idea into an actionable strategy?

To turn a vague idea into an actionable strategy, you must clarify the intent, identify required artefacts, and select necessary skills in logical order. This establishes a governed plan with validation gates to prevent wasted effort on unclear objectives.

What's the best way to plan discovery steps for a broad project goal?

The best way to plan discovery steps for a broad goal is to insert validation gates where objectives remain unclear. This approach selects necessary skills in a logical sequence, ensuring that market research, user needs, and technical feasibility are validated before execution.

Can I create a discovery plan if I only have an idea and no context artefacts?

Yes, you can create a discovery plan with only human intent. While optional context artefacts or memory can enrich the process, the core function relies on transforming the stated intent into a structured sequence of necessary skills and validation gates.

Why does my discovery plan include validation gates?

Discovery plans include validation gates to manage broad or unclear objectives. They act as checkpoints to ensure the strategy remains aligned with the original intent, preventing wasted effort by pausing for clarification before proceeding to the next selected skill.