tad-elicit

Automate structured requirement elicitation with 3-5 rounds of questioning and evidence recording.

3|Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Sheldon-92/TAD --skill tad-elicit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tad-elicit
Source: https://github.com/Sheldon-92/TAD/tree/main/.agents/skills/tad-elicit
Command: npx skills add https://github.com/Sheldon-92/TAD --skill tad-elicit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured requirement elicitation by enforcing 3-5 rounds of questioning and recording evidence to ensure clear scope.

Core Features & Use Cases

  • Enforces a minimum of three elicitation rounds with a deterministic flow.
  • Collects and stores round-by-round evidence for audit and traceability.
  • Provides a quick-start template to begin elicitation in new engagements.

Quick Start

Initiate the requirement elicitation process with 3-5 mandatory rounds, enforce the rounds, and record evidence for each round.

Frequently Asked Questions about tad-elicit

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

FAQPage Schema
How do I automate structured requirement elicitation with stakeholders?

Requirement elicitation is a structured process of gathering stakeholder input through 3-5 mandatory rounds of questioning to define project scope, constraints, and priorities. It enforces deterministic flows and uses 0-9 options instead of yes/no questions to ensure precise data collection.

How do I ensure requirement elicitation rounds are properly recorded for audit?

Structured requirement elicitation differs from ad-hoc stakeholder interviews by enforcing a deterministic 3-5 round questioning flow and automatically recording round-by-round evidence for audit traceability. It uses 0-9 options instead of yes/no questions to capture precise priorities and constraints.

Does requirement elicitation work without yes/no questions?

Yes, this requirement elicitation approach enforces the use of 0-9 options instead of yes/no questions to capture nuanced stakeholder priorities. You can use it for new engagements by loading the quick-start template to define scope, constraints, and priorities across 3-5 mandatory rounds.

What are the limitations of enforcing 3-5 rounds for stakeholder requirement gathering?

Enforcing 3-5 rounds of requirement elicitation ensures thorough scope definition but may add overhead for simple engagements. The mandatory minimum of three rounds and deterministic flow might be excessive if stakeholder input is already well-defined and constraints are clear.

How do I start requirement elicitation for a new project engagement?

You can start requirement elicitation for new engagements by using a quick-start template that initiates a structured 3-5 round questioning flow. The process loads the elicitation task from a markdown file and immediately begins recording stakeholder evidence.