requirements-elicitation

PROACTIVELY use. Extract requirements from documents including PDFs, specifications, meeting transcripts, and web content. Uses pattern matching and NLP to identify requirement candidates.

PROACTIVELY use. Analyze requirements for completeness using domain checklists, NFR categories, and INVEST criteria. Identifies missing requirements and recommends elicitation techniques to fill gaps.

PROACTIVELY use when creating customer journey maps from elicited requirements. Analyzes synthesis data, interview transcripts, and stakeholder perspectives to generate comprehensive journey visualizations with emotional curves, pain points, and opportunities. Outputs Mermaid diagrams.

PROACTIVELY use when assessing requirement quality. Evaluates requirements against 6Cs criteria (Clear, Concise, Complete, Consistent, Correct, Confirmable) and INVEST principles. Returns quality scores with improvement recommendations.

PROACTIVELY use. AI-led requirements elicitation interviewer using LLMREI research-backed patterns. Conducts structured stakeholder interviews with context-adaptive questioning.

PROACTIVELY use when consolidating requirements from multiple sources. Synthesizes requirements from interviews, documents, simulations, and research into unified requirement sets. Resolves conflicts, identifies patterns, and produces pre-canonical output.

PROACTIVELY use. Unified simulated stakeholder for requirements elicitation. Supports persona types: business, compliance, end-user, operations, technical. Pass persona type as argument.

Analyze meeting transcripts to extract requirements, decisions, and action items. Specialized extraction for conversational content.

Facilitate AI-assisted brainstorming sessions for requirements discovery. Uses divergent-convergent thinking patterns to generate ideas, then filters and refines them. Supports multiple brainstorming techniques.

Business rules elicitation and analysis techniques. Covers rule types (constraints, derivations, inferences), decision tables, rule templates, and policy documentation. Use when identifying business policies, constraints, calculations, and decision logic during requirements elicitation.

Main orchestrator for full requirements elicitation workflow. Coordinates interviews, document extraction, simulation, research, and synthesis.

Extract requirements from existing documents including PDFs, Word docs, meeting transcripts, specifications, and web content. Identifies requirement candidates, categorizes them, and outputs in pre-canonical format.

MCP-powered domain research for requirements elicitation. Uses perplexity, context7, firecrawl, and other MCP servers to research domain knowledge, best practices, and industry requirements.

Hub skill for requirements elicitation. Provides technique selection, orchestration guidance, LLMREI patterns, and autonomy level configuration. Use when gathering requirements from stakeholders, conducting elicitation sessions, or preparing requirements for specification.

Export elicited requirements to specification formats. Supports canonical, EARS, Gherkin, and other formats.

Extract requirements from documents (PDF, Markdown, Word, URLs). Identifies requirement candidates and outputs in pre-canonical format.

Analyze requirements for completeness, missing areas, and gaps. Uses domain checklists, NFR categories, and INVEST criteria to identify what's missing from elicited requirements.

Analyze current requirements for completeness and identify missing areas. Uses domain checklists, NFR categories, and INVEST criteria.

AI-led stakeholder interviews using LLMREI research-backed patterns. Conducts structured interviews to elicit requirements through context-adaptive questioning, active listening, and systematic requirement extraction.

Conduct an AI-led requirements elicitation interview with a stakeholder. Uses LLMREI research-backed patterns for effective requirement capture.

Create a customer journey map from elicited requirements. Visualizes end-to-end user experience with stages, touchpoints, emotions, and pain points. Outputs Mermaid diagrams.

Jobs to Be Done (JTBD) framework by Clayton Christensen. Analyzes requirements through the lens of what 'job' customers hire products to do. Covers functional, emotional, and social jobs. Use when understanding underlying customer motivations or reframing features as outcomes.

Requirements prioritization techniques including MoSCoW, Kano Model, WSJF (SAFe), and Wiegers' Value/Cost/Risk matrix. Provides scoring frameworks, trade-off analysis, and priority visualization. Use when ranking requirements by business value, customer impact, or implementation efficiency.

Apply prioritization methods to elicited requirements. Supports MoSCoW, Kano Model, WSJF, and Wiegers' scoring. Outputs ranked requirements with justification.

Research domain knowledge using MCP servers (perplexity, context7, firecrawl). Gathers best practices, regulatory requirements, and competitive insights.

Run multi-stakeholder simulation to generate requirements from diverse perspectives. Simulates End User, Technical, Business, Compliance, and Operations stakeholders.

Multi-persona stakeholder simulation for solo requirements work. Generates diverse perspectives from simulated End User, Technical, Business, Compliance, and Operations stakeholders when real stakeholders are unavailable.

Create a user story map from elicited requirements. Visualizes user journey with backbone activities, walking skeleton, and release slices. Outputs Mermaid diagrams.

Generate stakeholder surveys for requirements gathering and analyze responses. Creates questionnaires based on domain context, collects structured feedback, and produces statistical analysis with requirement candidates.

Use Case 2.0 methodology by Ivar Jacobson. Covers use case slices, lightweight documentation, user story derivation, and value-driven prioritization. Modern approach to use case modeling for agile teams.

Jeff Patton's User Story Mapping technique for Agile discovery. Visualizes user journey as a map, identifies backbone activities, walking skeleton, and release slices. Use when organizing requirements into deliverable increments or defining MVP scope.

Facilitate structured requirements workshops (JAD-style). Guides through agenda, captures decisions, resolves conflicts, and produces consolidated requirements. Supports multiple workshop formats.