dev-step--clarify-requirements

Name: dev-step--clarify-requirements
Availability: InStock
Author: tetetratra

Clarify task requirements and produce a formatted requirements document.

Updated Sep 27, 2020

Search Tags:#template #requirements #structured-output #questioning #stakeholders #clarify #task-definition

Ready to run

npx skills add https://github.com/tetetratra/dotfiles --skill dev-step-clarify-requirements

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-step--clarify-requirements
Source: https://github.com/tetetratra/dotfiles/tree/main/claude/skills/dev-step--clarify-requirements
Command: npx skills add https://github.com/tetetratra/dotfiles --skill dev-step-clarify-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams transform vague task requests into precise, testable requirements by eliciting essential details and documenting them in a standardized format.

Core Features & Use Cases

Clarification dialogue: Proactively asks questions to resolve ambiguity and identify missing information.
Structured output: Produces a formal requirements definition that uses the required template, including a keywords section and a formal output section.
Use Case: For a product feature request, it gathers acceptance criteria and non-functional requirements, then outputs a complete requirements document ready for review.

Quick Start

Ask for a task description and known constraints, then generate a formal requirements definition in the required format.

Frequently Asked Questions about dev-step--clarify-requirements

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

FAQPage Schema

How do I clarify task requirements to reduce ambiguity and scope creep?▼

To clarify task requirements and reduce ambiguity, you need to elicit missing details from stakeholders and document them in a standardized template. This structured output approach formalizes vague task requests into precise, testable requirements.

What is the best way to formalize a vague product feature request into testable requirements?▼

The best way to formalize a vague product feature request is to run a clarification dialogue that gathers acceptance criteria and non-functional requirements. This produces a complete formal requirements document ready for stakeholder review.

How do I generate a structured requirements document from a basic task description?▼

You can generate a structured requirements document by providing a task description and known constraints. The Skill processes these inputs to produce a formal requirements block listing each requirement and its description alongside a keywords section.

Can I use structured questioning to define requirements for software and research tasks?▼

Yes, you can use structured questioning to define requirements for software and research tasks. The clarification process applies across product, software, and research domains by proactively asking questions to resolve ambiguity and identify missing information.

Does clarifying requirements before development actually prevent scope creep?▼

Yes, clarifying requirements before development prevents scope creep by transforming vague task requests into precise, testable definitions. Eliciting essential details upfront establishes strict boundaries and formalizes stakeholder expectations.

What format does the structured task definition output use for stakeholders?▼

The structured task definition output uses a standardized template featuring a keywords section and a formal requirements block. This formatted requirements document lists each requirement alongside its description for stakeholder review.