skills.rest
Ruzenie
RuzenieCOMMUNITY
Explore all skills by this author →
GitHub

requirements-elicitation-engine

Clarify ambiguous project requirements and generate a draft PRD, questions, and style profile.

2|Updated Feb 15, 2026
Search Tags:#style guide#clarification#requirements gathering#questionnaire#project scoping#prd generation
One-click install
npx skills add https://github.com/Ruzenie/RUI-agentskills --skill requirements-elicitation-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-elicitation-engine
Source: https://github.com/Ruzenie/RUI-agentskills/tree/main/RUI-agentskills/RUI-codex-cn/skills/requirements-elicitation-engine
Command: npx skills add https://github.com/Ruzenie/RUI-agentskills --skill requirements-elicitation-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms vague or incomplete user requirements into actionable project specifications, ensuring clarity and alignment before development begins.

Core Features & Use Cases

  • Structured Questioning: Proactively identifies missing information through targeted questions across eight key dimensions (basic info, tech stack, design, etc.).
  • Artifact Generation: Automatically produces a draft Product Requirements Document (PRD), a list of follow-up questions, and a style profile.
  • Use Case: When a user provides a brief like "Build a SaaS data dashboard," this Skill will ask clarifying questions about the target users, desired features, and technical preferences to generate a comprehensive PRD.

Quick Start

Use the requirements-elicitation-engine skill to clarify the requirement "Build a SaaS data dashboard".

Frequently Asked Questions about requirements-elicitation-engine

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

FAQPage Schema
How do I convert vague project requirements into a draft PRD?▼

To convert vague project requirements into a draft PRD, use structured requirements gathering. A multi-dimensional questioning mechanism clarifies project basics, tech stack, and design preferences to generate actionable specifications.

What questions should I ask for project scoping and requirements gathering?▼

For project scoping and requirements gathering, ask targeted questions across eight dimensions: project basics, tech stack, design preferences, functionality, quality constraints, responsiveness, content management, and deployment considerations.

Can I generate a style profile and PRD from a brief like build a SaaS data dashboard?▼

Yes, you can generate a style profile and PRD from a brief like build a SaaS data dashboard. The system asks clarifying questions about target users and features to produce comprehensive draft specifications.

What is the best way to clarify ambiguous software requirements before development?▼

The best way to clarify ambiguous software requirements before development is employing a structured elicitation questionnaire. It proactively identifies missing information and outputs a list of outstanding follow-up questions.

Do I need any specific dependencies to automate PRD generation?▼

No, you do not need any specific dependencies to automate PRD generation. The requirements elicitation operates independently without external tool dependencies to transform incomplete inputs into structured specifications.

Related Skills

Explore More Product & Management Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
githubgithub
37.6k

prd

Generate production-grade PRDs with executive summaries, user stories, and technical specifications.

Official
Basic
JohannesKoningsJohannesKonings

to-prd

Synthesize conversation and codebase context into a product requirements document and publish it to the issue tracker.

Community
Intermediate
fred-drakefred-drake
27

interview

Conducts an interactive interview to generate a detailed specification document.

Community
Advanced