Validate requirements against EARS patterns and detect forbidden phrases.
npx skills add https://github.com/beomeodev/specter --skill ms-foundation-ears
Please help me install this Agent Skill. Skill: ms-foundation-ears Source: https://github.com/beomeodev/specter/tree/main/.claude/skills/ms-foundation-ears Command: npx skills add https://github.com/beomeodev/specter --skill ms-foundation-ears
Requirements often suffer from ambiguity, vagueness, or improper language that makes them hard to implement, test, and verify. This skill ensures that requirements conform to EARS patterns and flags forbidden phrases, improving clarity and traceability. It also guides you to rewrite non-compliant statements into measurable, testable specs.
Write your requirement in natural language and run the validator to receive a compliance report.
High-intent search queries and answers about installing and using this skill.
To validate requirements against EARS patterns, run the validator on your natural language specifications to receive a structured compliance report detailing detected patterns, forbidden phrase violations, and suggested rewrites.
Forbidden phrases in requirements specification are vague or ambiguous terms that hinder testability; the validator detects them and provides concrete rewrite suggestions to ensure your requirements are measurable and clear.
You can rewrite non-compliant requirements for measurability and testability by applying the validator's suggested rewrites, which enforce clear pass/fail criteria and align your statements with the five EARS patterns.
You need EARS patterns for writing software specifications when structuring requirements consistently across Ubiquitous, Event-driven, State-driven, Optional, and Constraint categories to improve traceability and reduce implementation errors.
Yes, you can use the validator for reviewing existing requirements during a SPEC review; it assesses each statement for measurability, detects forbidden phrases, and outputs metadata detailing compliance and rewrite suggestions.
The best way to enforce clear pass/fail criteria is to validate requirements against EARS patterns, which flags ambiguous language and guides you to rewrite non-compliant statements into structured, testable specifications.
Fr-e-dAnalyze project directory structures to generate architectural summaries.
vladm3105Generate executable test suites from SDD artifacts across multiple frameworks.
maksutovicExtract acceptance criteria and test plans to verify implementations against specifications.
gnurioAdapt general memetics strategies into domain-specific playbooks with metrics and timelines.
