requirements-clarity

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.

Install with Tessl CLI

npx tessl i github:softaworks/agent-toolkit --skill requirements-clarity

What are skills?

Review — 62%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 100%

Agent success when using this skill

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

100%

20%

Requirements Intake Triage

Activation detection and initial assessment

Criteria

Without context

With context

Activate on Request 1

100%

No activation on Request 2

100%

Correct non-activation reason

100%

Clarity score shown

100%

Clear aspects listed

100%

Gaps listed

100%

Score reflects low clarity

100%

Identifies functional gaps

100%

Identifies technical gaps

100%

Announces clarification intent

100%

responses.md created

100%

Without context: $0.1201 · 31s · 7 turns · 56 in / 1,581 out tokens

With context: $0.2765 · 58s · 14 turns · 62 in / 2,712 out tokens

100%

44%

Requirements Clarification Dialogue

Multi-round clarification dialogue and scoring

Criteria

Without context

With context

Initial score shown

100%

Low initial score

100%

Questions per round limited

100%

Category labels in questions

100%

Score update after round 1

100%

Summarizes new content

57%

100%

Lists remaining gaps

42%

100%

Continues if below 90

100%

Score update after round 2

100%

Declares readiness at 90+

60%

100%

Covers all four gap dimensions

100%

clarification-dialogue.md created

100%

Final Assessment section

75%

100%

Without context: $0.1649 · 56s · 6 turns · 7 in / 2,929 out tokens

With context: $0.4971 · 2m 40s · 17 turns · 65 in / 7,980 out tokens

100%

53%

Feature Requirements to PRD

PRD generation and file structure

Criteria

Without context

With context

Correct directory created

100%

Correct file path

100%

Kebab-case filename

100%

Version in filename

100%

Requirements Description section

28%

100%

Design Decisions section

42%

100%

Acceptance Criteria with checkboxes

100%

Functional acceptance items

71%

100%

Quality Standards items

50%

100%

Execution Phases present

62%

100%

Document Version in footer

100%

Clarification Rounds in footer

42%

100%

Quality Score in footer

42%

100%

Created timestamp in footer

100%

Without context: $0.2717 · 1m 43s · 7 turns · 8 in / 5,830 out tokens

With context: $0.3727 · 1m 56s · 12 turns · 13 in / 5,747 out tokens

Evaluated: about 6 hours ago
Agent: Claude Code

Table of Contents

Requirements Intake Triage Requirements Clarification Dialogue Feature Requirements to PRD

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.