What is the 150% Clarity Rule?

It is a principle ensuring 100% understanding of the core goal and expected result, plus an additional 50% focus on surfacing hidden constraints, unstated requirements, and edge cases.

Can Goal Clarity 150 be used with other Claude Code skills?

Yes, it is designed to be the first step in a workflow: use Goal-Clarity for understanding, Deep-Think for strategy, and Max-Quality for execution.

When should I trigger the Goal Clarity skill?

Invoke it when starting new tasks, when requirements seem vague, when multiple interpretations are possible, or anytime you realize mid-work that expectations are unclear.

How does this skill help prevent scope creep?

By explicitly defining what is included and excluded in the 'Scope' dimension and establishing clear success criteria at the start, it creates a documented boundary for the task.

Goal Clarity 150

Name: Goal Clarity 150
Author: MykhailoDmytriakha

byMykhailoDmytriakha

Productivity & Workflow

Ensures absolute alignment on project goals, success criteria, and hidden constraints before executing tasks to eliminate wasted effort.

About

Goal Clarity 150 is a specialized protocol designed to neutralize ambiguity in software development. By implementing a systematic '150% Clarity' framework, it probes beyond surface-level instructions to identify the core purpose, success metrics, and hidden constraints of any task. This skill is essential for developers and project leads who want to prevent scope drift and ensure that the final output matches the stakeholder's vision, making it the ideal first step for any new feature, bug fix, or project phase.

Key Features

Built-in recovery protocols for addressing scope drift or mid-task ambiguity
Proactive identification of risks and unstated stakeholder expectations
Systematic 150% Clarity framework covering core goals and hidden constraints
Structured success criteria mapping including 'done' definitions and ideal outcomes
Standardized output format for documenting agreed-upon project requirements
0 GitHub stars

Use Cases

Translating vague feedback or high-level goals into actionable technical tasks
Auditing ongoing work to ensure alignment when project expectations shift
Starting complex new features where initial requirements are loosely defined

About

Key Features

Built-in recovery protocols for addressing scope drift or mid-task ambiguity
Proactive identification of risks and unstated stakeholder expectations
Systematic 150% Clarity framework covering core goals and hidden constraints
Structured success criteria mapping including 'done' definitions and ideal outcomes
Standardized output format for documenting agreed-upon project requirements
0 GitHub stars

Use Cases

Translating vague feedback or high-level goals into actionable technical tasks
Auditing ongoing work to ensure alignment when project expectations shift
Starting complex new features where initial requirements are loosely defined