data-requirements

To convert meeting notes into structured strategic requirements, this Skill extracts stakeholders, business problems, prioritized use cases, and data gaps from raw text. It then generates an issue tree, impact and feasibility matrix, and KPI definitions, saving the output as a requirements document.

An issue tree is a structured, prioritized breakdown of business problems used in project scoping. This Skill generates an issue tree from your context documents to systematically map root causes and prioritize use cases for actionable decision-making.

Performing a data gap analysis from kickoff notes involves comparing available data against project requirements. This Skill systematically extracts available data and missing data gaps from your text inputs, producing a data assessment table to highlight missing analytical requirements.

Yes, you can extract KPI definitions and sample size guidance from proposal preparation documents. This Skill processes your context documents to produce KPI definitions complete with MDE and sample size guidance to ensure measurable analytical outcomes.

Yes, this requirements extraction tool handles ambiguous stakeholder information through an interactive wall-bounce mode. It engages you with targeted questions to resolve ambiguities, updating the single source of truth context file while finalizing the strategic requirements.

The best way to document stakeholder analysis and risks from client meetings is to systematically extract them from raw notes into a structured format. This Skill produces a stakeholder list and a risk log, persisting the strategic outputs to a markdown requirements file.