requirement-mining

Analyze user feature requests to uncover root causes and produce structured requirement lists.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill requirement-mining-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirement-mining
Source: https://github.com/HACK-WU/skills/tree/main/skills/requirement-mining
Command: npx skills add https://github.com/HACK-WU/skills --skill requirement-mining-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Users often describe solutions instead of real problems, leading teams to build features that treat symptoms rather than root causes. This Skill digs beneath surface-level feature requests, challenges patch-style solutions, and translates validated needs into prioritized, testable requirement lists. ## Core Features & Use Cases - Root-Cause Analysis: Infers the user's true motivation and scenarios, identifies "solutions disguised as requirements", and critically evaluates whether a proposed feature actually solves the underlying problem. - Visual Change Comparison: Produces "current vs expected" diagrams (Mermaid flows, ASCII UI mockups) during the analysis phase so stakeholders can spot misunderstandings early. - Structured Requirement Translation: Outputs prioritized requirement lists (P0/P1/P2) with dependencies, acceptance criteria, feasibility assessment, and complexity scoring to recommend the next step (quick implementation, design, or work breakdown). - Use Case: A user says "add a progress bar to our slow export feature". The Skill reveals the real pain is uncertainty during long waits, recommends async export with completion notification as the root fix, and delivers a full requirement report with diagrams and verification metrics. ## Quick Start Ask the AI to analyze a feature request like "our export is too slow, add a progress bar" and confirm or correct its inferred requirement understanding.

Frequently Asked Questions about requirement-mining

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

FAQPage Schema
How do I turn a vague feature request into a structured requirement list?

Describe the feature request or complaint in natural language. The Skill infers the underlying motivation and scenarios, presents hypotheses for your confirmation, then translates the confirmed need into a prioritized requirement list with acceptance criteria and dependencies.

How to tell if a user request is a real need or a disguised solution?

The Skill performs root-cause analysis that traces the causal chain behind the request and evaluates whether the proposed feature addresses the symptom or the root cause. It classifies the proposal as on-target, partially effective, or superficial, and suggests more fundamental alternatives when needed.

Can requirement analysis include diagrams of workflow changes?

Yes. When a requirement changes execution flows, data flows, UI, or state transitions, the Skill generates current-versus-expected comparison diagrams using Mermaid for flows and ASCII for UI layouts, each annotated with a change-point table.

When should a requirement skip the design phase and go straight to coding?

The Skill scores complexity across six dimensions including technical difficulty, scope, dependencies, and risk. Only low-complexity requirements are recommended for direct implementation; medium and high complexity requirements are routed to design, work breakdown, or prototype verification.

What are the limitations of AI-driven requirement mining?

The analysis relies on user-provided descriptions, so inferred current-state details are marked as assumptions requiring confirmation. It produces an analysis report rather than a final approved plan, and human review remains the decision authority.