maister:requirements-critic

What problem does it solve?

Poorly written, ambiguous, or incomplete requirements lead to wasted development effort, misaligned deliverables, and code that fails to meet actual business needs. This skill eliminates that risk by systematically identifying flaws in requirements before implementation begins.

Core Features & Use Cases

• 4-Structured Validation Checks: Applies problem-vs-solution framing analysis, CRUD-disguised-as-domain-logic detection, hidden domain decision signal mapping, and rigid quantifier probing to catch common requirement flaws.
• Interactive Reformulation: Turns vague status-change-only requirements into clear, testable requirements with explicit observable behavior, concurrency rules, and reversibility logic.
• Use Case: A product manager can use this skill to review a ticket that says "User clicks Reserve to set status to Reserved" and get a reformulated requirement that specifies the reservation blocks availability for other users, handles concurrent requests, and supports cancellation.

Quick Start

Share your requirements, ticket, or spec with the skill and request a critique to receive identified issues, clarifying questions, and suggested rewrites for each requirement.