unknowns-first

Diagnose ambiguous tasks by identifying four unknown categories and success standards.

16|1|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/bahayonghang/my-ai-cli-toolkit --skill unknowns-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unknowns-first
Source: https://github.com/bahayonghang/my-ai-cli-toolkit/tree/main/skills/development-workflows/unknowns-first
Command: npx skills add https://github.com/bahayonghang/my-ai-cli-toolkit --skill unknowns-first

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents wasted effort and rework by forcing a structured diagnosis of ambiguous or high-stakes tasks before execution begins.

Core Features & Use Cases

  • Task Diagnosis: Identifies knowns, unknowns, and hidden assumptions to clarify project requirements.
  • Expert Alignment: Matches the task level to the appropriate expert perspective to ensure success standards are realistic.
  • Use Case: When a user provides a vague request like "make this landing page feel more premium," the skill surfaces the need for visual prototypes and examples rather than guessing the user's intent.

Quick Start

Invoke the unknowns-first skill to diagnose your current project requirements and identify critical missing information before you start coding.

Frequently Asked Questions about unknowns-first

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

FAQPage Schema
How do I clarify ambiguous project requirements before starting development?

To clarify ambiguous project requirements, diagnose the task by identifying knowns, unknowns, and hidden assumptions to establish clear success standards before execution begins.

What is the best way to prevent wasted effort on vague software tasks?

Preventing wasted effort on vague software tasks requires a structured diagnosis that surfaces hidden assumptions and matches task complexity to the appropriate expert perspective for realistic planning.

How do I diagnose unknowns and manage risks in complex project planning?

Diagnosing unknowns in complex project planning involves categorizing missing information into distinct groups and applying a formal diagnostic contract to mitigate risks before work starts.

Can I use structured task diagnosis for high-stakes creative work?

Yes, structured task diagnosis applies to high-stakes creative work by surfacing critical missing information—like needing visual prototypes for a premium redesign—rather than guessing user intent.

When should I use a formal diagnostic contract for task clarification?

Use a formal diagnostic contract for task clarification when facing high-stakes decisions or vague requests, ensuring expert alignment and structured risk mitigation prior to execution.

Does task diagnosis work without specific platform dependencies?

Task diagnosis works without specific platform dependencies because it focuses on identifying unknowns and establishing success standards through a formal reasoning process rather than relying on external libraries.