What problem does it solve? Collected requirements are often ambiguous, conflicting, or unprioritized, which leads to rework during specification and implementation. This Skill runs the Analysis step of the Requirements Management cycle: it evaluates requirement quality against IEEE 830 criteria, resolves stakeholder conflicts, prioritizes with MoSCoW and Kano, and decides whether to proceed to specification or return to elicitation. ## Core Features & Use Cases - Quality checklist: Evaluates each candidate requirement against completeness, consistency, unambiguity, verifiability, feasibility, and traceability criteria. - Conflict resolution: Classifies conflicts (priority, scope, technical, business) and applies structured resolution or escalation paths. - Prioritization: Applies MoSCoW with assignment criteria and optional Kano analysis, including rules to detect broken prioritization such as everything marked Must Have. - Use Case: After a requirements elicitation phase for an e-commerce platform, run this Skill to verify each requirement is testable, resolve a conflict between sales and operations stakeholders, and produce a prioritized rm-analysis.md artifact ready for specification. ## Quick Start Analyze the requirements in my rm-elicitation.md file, resolve any conflicts, prioritize them with MoSCoW, and produce the rm-analysis artifact.
