skills.rest
taptap
taptapOFFICIAL
Explore all skills by this author →
Website𝕏@taptapGitHub

requirement-clarification

Extract scope, constraints, and success criteria through structured questions.

Updated Aug 27, 2026
Search Tags:#workflow#documentation#requirements#qa#clarification#downstream
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill requirement-clarification-taptap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirement-clarification
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/test/skills/requirement-clarification
Command: npx skills add https://github.com/taptap/agents-plugins --skill requirement-clarification-taptap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams align on vague or evolving requirements by driving a structured clarification process and capturing decisions.

Core Features & Use Cases

  • Structured multi-pass Q&A to surface hidden requirements and uncertainties.
  • Produces standardized artifacts (clarification_log.md, clarified_requirements.json, requirement_points.json, implementation_brief.json) for downstream skills.
  • Supports multiple input modes (document, design, exploratory) and provides cross-checks against acceptance criteria.

Quick Start

Provide input data (link, document, or text) and the skill will initiate a structured clarification workflow to generate four artifacts.

Frequently Asked Questions about requirement-clarification

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

FAQPage Schema
How do I clarify vague project requirements before starting development?▼

Structured requirement clarification uses multi-pass Q&A to surface hidden uncertainties and constraints from documents or text, producing a log and JSON artifacts to align teams on vague inputs.

What is the best way to extract scope and success criteria from a design document?▼

Design mode clarification processes design documents by cross-checking inputs against acceptance criteria, yielding structured requirement points and an implementation brief for downstream workflows.

How do I generate structured documentation from free text conversation fragments?▼

Exploratory mode clarification ingests free text conversation fragments to identify scope and constraints, outputting standardized artifacts like clarification_log.md and clarified_requirements.json for downstream use.

Can I use conversation fragments as input for requirement clarification workflows?▼

Yes, conversation fragments are supported as valid inputs for requirement clarification workflows alongside links, documents, and free text, enabling the extraction of scope and constraints to generate structured artifacts.

What artifacts are generated when clarifying requirements through structured questioning?▼

The requirement clarification workflow generates four downstream artifacts: clarification_log.md, clarified_requirements.json, requirement_points.json, and implementation_brief.json.

Does requirement clarification work for exploratory inputs without formal documentation?▼

Yes, exploratory mode processes informal free text and conversation fragments without formal documentation, extracting constraints and success criteria to output structured requirement points and an implementation brief.

Related Skills

Explore More Product & Management Skills→
accionlabsaccionlabs
2

analyze-functional

Analyze requirements against the Breeze functional graph to identify gaps and conflicts.

Official
Advanced
Nikhil-Chopra-7Nikhil-Chopra-7
1

figma-mapper

Map task breakdowns to Figma frames and extract design properties.

Community
Advanced
joe-watkinsjoe-watkins
1

a11y-validator

Re-run accessibility tests and verify acceptance criteria against magentaa11y-mcp.

Community
Intermediate
aqwsde321aqwsde321

resume-to-json

Convert unstructured resume text into a standardized resume.json file.

Community
Intermediate