What problem does it solve?
Feature requirements that are incomplete, ambiguous, inconsistent, or missing critical edge cases lead to costly rework, missed user needs, and delayed releases. This Skill acts as "unit tests for English" to validate the quality of requirement specifications before implementation begins, ensuring they are clear, complete, and ready for engineering teams.
Core Features & Use Cases
- Domain-Specific Checklist Generation: Create tailored checklists for UX, security, API, performance, or source document coverage to target the most relevant requirement quality dimensions for your feature.
- Dynamic Context Adaptation: Uses up to three clarifying questions derived from your feature's spec, plan, and risk indicators to customize checklist focus areas, depth, and audience without relying on pre-baked templates.
- Governance-Aligned Validation: Enforces project-specific anti-hallucination rules, traceability requirements, and forbidden pattern checks to ensure checklists are actionable, aligned with existing artifacts, and free of implementation-focused noise.
- Use Case: A product manager finalizing a new authentication feature spec can use this Skill to generate a security-focused requirements checklist to catch missing edge cases like password reset flows, inconsistent access control language, and unquantified performance targets before handing off to engineering.
Quick Start
Use the mad-checklist skill to generate a custom requirements quality checklist for your current active feature, specifying a focus domain like security or UX if desired.
