What problem does it solve?
This Skill removes the chaos of transforming unstructured hearing sheets and meeting notes into formal, testable requirements by producing a structured requirements set, traceability artifacts, and a gap/ambiguity report.
Core Features & Use Cases
- Extract & parse hearing data: Loads hearing sheets, meeting notes, or transcripts and extracts requirement statements while preserving source context for traceability.
- Classify requirements (BR/SR/FR/NFR/CON/ASM) with MoSCoW: Organizes requirements into business, stakeholder, functional, non-functional, constraints, and assumptions, and applies Must/Should/Could/Won’t priority.
- Detect gaps, ambiguities, and conflicts: Flags vague quantifiers, open-ended lists, temporal vagueness, and passive/unclear responsibility patterns using a checklist-driven approach.
- Map requirements to WBS and generate RTM: Maps requirements to WBS items and generates a requirements traceability matrix (including Excel output support).
- Produce bilingual requirements documents (JA/EN): Supports Japanese/English workflows using configurable templates for final documentation.
Quick Start
Use the hearing-to-requirements-mapper skill to convert your attached hearing sheet into a structured requirements JSON and a requirements document using its default bilingual templates.
