clarity

Clarify task intent and scope using the WHAT, WHY, HOW, and KNOWN UNKNOWNS framework.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ioku24/autorankr --skill clarity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarity
Source: https://github.com/ioku24/autorankr/tree/main/.claude/skills/5-system-framework/1.clarity
Command: npx skills add https://github.com/ioku24/autorankr --skill clarity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishing a shared understanding before starting work prevents misalignment, rework, and wasted effort when inputs are vague, ambiguous, or conflicting.

Core Features & Use Cases

  • Clarity Protocol: Applies WHAT, WHY, HOW, and KNOWN UNKNOWNS to define the problem, rationale, success criteria, and boundaries.
  • Context Maintenance: Updates an Active Context log to reflect evolving scope and decisions.
  • Decision Readiness: Produces a clear, actionable plan that guides execution and reduces back-and-forth.

Quick Start

Initiate the Clarity System on a new task by outlining WHAT, WHY, HOW, and KNOWN UNKNOWNS, then confirm and push context updates.

Frequently Asked Questions about clarity

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

FAQPage Schema
How do I clarify task scope and intent before starting complex work?

To clarify task scope, define the WHAT, WHY, HOW, and KNOWN UNKNOWNS to establish shared understanding and success criteria before execution. This prevents misalignment and reduces rework when inputs are vague or conflicting.

What is the best way to handle fuzzy input and conflicting requirements during project inception?

Handling fuzzy input involves applying a clarity protocol that defines the problem, rationale, and boundaries. This enforces alignment across stakeholders and produces a clear, actionable plan for execution.

How does an active context log maintain decision readiness for evolving task definitions?

An active context log maintains decision readiness by continuously recording scope updates and decisions. This reflects evolving task definitions and reduces back-and-forth communication during execution.

When do I need to establish a clarity protocol for task definition?

You need a clarity protocol at task inception or whenever inputs become ambiguous. It enforces the WHAT, WHY, HOW, and KNOWN UNKNOWNS framework to ensure alignment and reduce wasted effort.

Can I use this clarity framework to reduce rework caused by vague communication?

Yes, establishing clear intent before action directly reduces rework caused by vague communication. It enforces problem boundaries and decision readiness, ensuring stakeholders share a unified understanding.

Why does defining known unknowns help with task alignment and scope boundaries?

Defining known unknowns helps with task alignment by explicitly identifying boundaries and potential risks. This ensures stakeholders acknowledge what is unclear, preventing scope creep and guiding execution.