requirements-critic

Critique requirements for hidden decisions, CRUD-disguised behavior, and absolute quantifiers.

Updated Nov 19, 2020
One-click install
npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill requirements-critic-kwojtasinski-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-critic
Source: https://github.com/kwojtasinski-repo/ECommerceApp/tree/main/.github/skills/requirements-critic
Command: npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill requirements-critic-kwojtasinski-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Requirements often hide unstated decisions, disguise simple status changes as domain behavior, or lock in implementations too early. This Skill reviews requirement text, tickets, or specs on explicit request and exposes those problems before implementation begins. ## Core Features & Use Cases - Problem vs Solution Check: Flags technical choices that obscure the real business need while ignoring settled constraints. - CRUD Detection: Identifies commands whose only effect is a database status change and probes for observable behavior like counters, quotas, and reversibility. - Hidden Decision Signal Map: Scans domain clusters such as money, retention, roles, integrations, status transitions, dates, and search to surface targeted questions. - Rigid Quantifier Probe: Tests words like always, never, only, and must against boundary scenarios. - Use Case: Paste a ticket like "users can always cancel orders" and receive quoted issues, discriminating questions, and a concrete rewrite into observable behavior. ## Quick Start Ask the assistant to critique the pasted requirement text or ticket and report hidden decisions with a suggested rewrite.

Frequently Asked Questions about requirements-critic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a requirement for hidden assumptions?

Paste the requirement text and explicitly ask for a critique. The Skill scans for hidden domain decisions across clusters like money, retention, roles, and integrations, then asks targeted questions and suggests a concrete rewrite.

How to detect CRUD operations disguised as business logic?

Check whether the command's only effect is a database status change. Probe what changes for other users, whether counters or quotas shift, whether the operation is reversible, and what breaks if the status field is removed.

When should I not use requirements critique?

Do not use it when the user is simply describing a feature, wants a solution rather than a critique, or the input is not a requirement or ticket. It activates only on explicit review requests.

Why do absolute words like always and never cause requirement problems?

Absolute quantifiers such as always, never, only, and must often hide untested boundary cases. The Skill tests each absolute rule against two to three boundary scenarios to check whether any exceptions should be allowed.

What output does a requirements critique produce?

Each finding includes the exact quoted phrase that triggered it, the check that flagged it, specific questions to resolve before implementation, and a suggested rewrite into observable behavior. If no issues exist, it says so explicitly.