wv-clarify-spec

Clarify vague task requirements using 5W+C analysis into concrete specifications.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/AGM1968/weave --skill wv-clarify-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wv-clarify-spec
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/wv-clarify-spec
Command: npx skills add https://github.com/AGM1968/weave --skill wv-clarify-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies vague requirements before implementation to prevent wasted effort and misaligned expectations.

Core Features & Use Cases

  • Identify ambiguity in task descriptions and propose concrete clarifications.
  • Apply the 5W+C framework to transform vagueness into a complete specification.
  • Transform to explicit WHAT, WHY, WHO, WHEN, WHERE, and CONSTRAINTS for implementation.

Quick Start

Use /wv-clarify-spec before claiming vague tasks to generate a concrete specification.

Frequently Asked Questions about wv-clarify-spec

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

FAQPage Schema
How do I clarify vague task requirements before starting software implementation?

To clarify vague task requirements, use the 5W+C framework to detect ambiguity and generate a concrete specification covering WHAT, WHY, WHO, WHEN, WHERE, and CONSTRAINTS before development begins.

What is the 5W+C analysis framework for software specifications?

The 5W+C framework for software specifications transforms vague task descriptions into explicit WHAT, WHY, WHO, WHEN, WHERE, and CONSTRAINTS, ensuring success criteria are clear and multiple interpretations are resolved.

When should I use ambiguity detection for task management?

Apply ambiguity detection for task management when task descriptions are vague, success criteria are unclear, or multiple interpretations exist, preventing wasted effort and misaligned expectations before implementation.

How do I turn a vague project description into a concrete specification?

Turn a vague project description into a concrete specification by guiding the team through 5W+C analysis, identifying ambiguities, and proposing explicit clarifications ready for implementation.

Do I need any specific dependencies to run 5W+C specification analysis?

No specific dependencies are required to run 5W+C specification analysis, as the tool operates independently to detect ambiguity and produce concrete specifications from vague requirements.

Why does unclear success criteria lead to wasted effort in software engineering?

Unclear success criteria lead to wasted effort because multiple interpretations cause misaligned expectations; applying 5W+C ambiguity detection beforehand produces a concrete specification to prevent this.