wz:clarifier

Transform briefing inputs into validated, auditable project plans with gated checkpoints.

3|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-clarifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wz:clarifier
Source: https://github.com/MohamedAbdallah-14/Wazir/tree/main/skills/clarifier
Command: npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-clarifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifier helps teams transform vague briefs into explicit scope, actionable plans, and auditable checkpoints, reducing misalignment and rework.

Core Features & Use Cases

  • Performs research, clarifies scope, brainstorms design, and generates task specifications and an execution plan with gating checkpoints.
  • Produces structured artifacts and enforces approvals between phases to minimize drift.
  • Supports interactive, guided, and auto interaction modes to suit different collaboration styles.

Quick Start

Review your briefing and run the clarifier to generate a fully scoped plan and execution handover.

Frequently Asked Questions about wz:clarifier

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

FAQPage Schema
How do I clarify project scope from a vague brief?

To clarify project scope, you transform briefing inputs into a validated plan using phase-gates. This enforces approvals between research, scope definition, design, and execution phases to minimize drift and rework.

What is the best way to lock project scope before execution handover?

Locking project scope requires generating structured artifacts and applying gated checkpoints. This separates clarify, spec, design, and plan phases, producing an auditable execution handover in the .wazir/runs/latest/clarified directory.

Can I run scope clarification automatically for multi-phase pipelines?

Yes, you can run scope clarification automatically. The process supports auto, guided, and interactive interaction modes to accommodate different collaboration styles across multi-phase AI-driven project pipelines.

How does phase-gating prevent scope creep in project planning?

Phase-gating prevents scope creep by enforcing explicit approvals between the clarify, spec, design, and plan phases. This structured approach transforms vague briefs into auditable checkpoints, preventing misalignment before execution handover.

Do I need specific documentation formats to define task specifications?

You do not need specific external documentation formats; the system generates task specifications and execution plans internally. It produces structured artifacts automatically within the .wazir/runs/latest/clarified output directory.