skills.rest
ArroganceG
ArroganceGCOMMUNITY
Explore all skills by this author →
GitHub

requirement-analyst

Clarify ambiguous user needs and extract actionable requirements from conversations.

Updated Mar 30, 2026
Search Tags:#planning#roadmap#interview#requirement-analysis#todo-management#intent-extraction
One-click install
npx skills add https://github.com/ArroganceG/trae_skills_backup --skill requirement-analyst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirement-analyst
Source: https://github.com/ArroganceG/trae_skills_backup/tree/main/requirement-analyst
Command: npx skills add https://github.com/ArroganceG/trae_skills_backup --skill requirement-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requirement ambiguity is common in early product conversations. This skill helps identify core needs, clarify intent, and convert vague descriptions into actionable requirements ready for planning and delivery.

Core Features & Use Cases

  • Structured interviewing: Guides targeted questions to elicit goals, success criteria, and acceptance standards.
  • Intent extraction: Distills non-technical language into concrete business objectives.
  • Plan alignment: Checks whether requirements align with docs/plan/roadmap.md current stage and tracks tasks in docs/plan/todo.md.

Quick Start

Provide your initial product goal and I will start structured interviews to clarify requirements.

Frequently Asked Questions about requirement-analyst

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

FAQPage Schema
How do I extract actionable requirements from stakeholder interviews?▼

Requirement extraction from stakeholder interviews is guided by structured questioning to elicit goals, success criteria, and acceptance standards. This distills non-technical language into concrete business objectives ready for delivery planning.

What is the best way to clarify ambiguous product needs during discovery?▼

Clarifying ambiguous product needs involves targeted interviews to identify core intents and convert vague descriptions into actionable requirements. This ensures early product conversations yield structured tasks aligned with overall goals.

How do I align extracted requirements with my project roadmap and todo list?▼

Plan alignment checks whether extracted requirements match the current stage in docs/plan/roadmap.md. Refined tasks are then tracked in docs/plan/todo.md to ensure structured planning and delivery continuity.

Does this requirement analysis approach work for non-technical product goals?▼

Requirement analysis works directly with non-technical product goals by applying intent extraction. It translates high-level business objectives into structured, actionable requirements without requiring initial technical specifications.

What limitations exist when converting vague descriptions into structured tasks?▼

Converting vague descriptions into structured tasks requires safety checks and frontmatter validation. Limitations arise if initial conversations lack clear goals, making intent extraction difficult without further targeted stakeholder interviewing.

Related Skills

Explore More Product & Management Skills→
kvnxiaokvnxiao

docs-generator

Audit codebases and generate CLAUDE.md with a structured docs/ directory.

Community
Advanced
kay6198835kay6198835

sprint-plan

Generate structured sprint plans from milestones, completed work, and capacity.

Community
Advanced
Aqsagull99Aqsagull99

task-intent-skill

Detect user intents from natural language and map them to Todo operations.

Community
Intermediate
hitoshisekihitoshiseki

aiox-sm

Automate scrum workflows including user story creation from product requirements documents.

Community
Advanced